X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?p=pintos-anon;a=blobdiff_plain;f=doc%2F44bsd.texi;h=ba67ddaa876e6504f2c2b95993b7810415dd0c6c;hp=d49f23490281312499a91d2d00ef9e7bd9f6c91d;hb=17102846d22591590c37548f8514067e2be6c5f6;hpb=04b1db625129936325474664d7f400b9993e9611

diff --git a/doc/44bsd.texi b/doc/44bsd.texi
index d49f234..ba67dda 100644
--- a/doc/44bsd.texi
+++ b/doc/44bsd.texi
@@ -76,11 +76,10 @@ Thread priority is dynamically determined by the scheduler using a
 formula given below.  However, each thread also has an integer
 @dfn{nice} value that determines how ``nice'' the thread should be to
 other threads.  A @var{nice} of zero does not affect thread priority.  A
-positive @var{nice}, to the maximum of 20, increases the numeric
-priority of a thread, decreasing its effective priority, and causes it
-to give up some CPU time it would otherwise receive.  On the other hand,
-a negative @var{nice}, to the minimum of -20, tends to take away CPU
-time from other threads.
+positive @var{nice}, to the maximum of 20, decreases the priority of a 
+thread and causes it to give up some CPU time it would otherwise receive.
+On the other hand, a negative @var{nice}, to the minimum of -20, tends
+to take away CPU time from other threads.
 
 The initial thread starts with a @var{nice} value of zero.  Other
 threads start with a @var{nice} value inherited from their parent