X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Ftour.texi;h=81eb5bd8786941cedf22ecd66b43e6915a70d922;hb=399d2a1d044a1c8789ee6c1bea54c57cffa710f9;hp=d1147dde6b0e91d891d5192cbf6bcc841781b920;hpb=ecd12507c871ad36c8f26d705d73ca367b5373ac;p=pintos-anon

diff --git a/doc/tour.texi b/doc/tour.texi
index d1147dd..81eb5bd 100644
--- a/doc/tour.texi
+++ b/doc/tour.texi
@@ -261,10 +261,10 @@ other registers that must be saved are saved on the stack.
 A thread priority, ranging from the lowest possible priority
 @code{PRI_MIN} (0) to the highest possible priority @code{PRI_MAX}
 (59).  Pintos as provided ignores thread priorities, but you will
-implement priority scheduling in problem 1-3 (@pxref{Problem 1-3
+implement priority scheduling in problem 1-2 (@pxref{Problem 1-2
 Priority Scheduling}).
 
-@item list_elem elem;
+@item struct list_elem elem;
 A ``list element'' used to put the thread into doubly linked lists,
 either the list of threads ready to run or a list of threads waiting
 on a semaphore.  Take a look at @file{lib/kernel/list.h} for