Invert the priority scheme, so that PRI_MIN is now the lowest priority

[pintos-anon] / doc / tour.texi

diff --git a/doc/tour.texi b/doc/tour.texi
index c1371cfde5760df3df4129a4f5eec6b0c4d3e66e..2e15b38ff525b1b15c8e2246a64d8eaa98f27850 100644 (file)
--- a/doc/tour.texi
+++ b/doc/tour.texi
@@ -327,8 +327,8 @@ the page.  @xref{Interrupt Handling}, for more information.
 
 @deftypecv {Member} {@struct{thread}} {int} priority
 A thread priority, ranging from @code{PRI_MIN} (0) to @code{PRI_MAX}
-(63).  Lower numbers correspond to @emph{higher} priorities, so that
-priority 0 is the highest priority and priority 63 is the lowest.
+(63).  Lower numbers correspond to lower priorities, so that
+priority 0 is the lowest priority and priority 63 is the highest.
 Pintos as provided ignores thread priorities, but you will implement
 priority scheduling in project 1 (@pxref{Priority Scheduling}).
 @end deftypecv