Clarify use of thread_get_nice() and thread_set_nice().

[pintos-anon] / doc / 44bsd.texi

diff --git a/doc/44bsd.texi b/doc/44bsd.texi
index 612aa1c74c51921168a319c2866e2a6b622b5466..3bbce0d572c2a6b3cc051920fa7caa7906b439ae 100644 (file)
--- a/doc/44bsd.texi
+++ b/doc/44bsd.texi
@@ -55,8 +55,8 @@ they run in ``round robin'' order.
 Multiple facets of the scheduler require data to be updated after a
 certain number of timer ticks.  In every case, these updates should
 occur before any ordinary kernel thread has a chance to run, so that
-there is no chance that a kernel thread could see @func{timer_ticks}
-increased but these old values for these data.
+there is no chance that a kernel thread could see a newly increased
+@func{timer_ticks} value but old scheduler data values.
 
 @menu
 * Thread Niceness::             
@@ -81,9 +81,9 @@ 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
-thread.  You
-must implement these functions, for which we have provided skeleton
-definitions in @file{threads/thread.c}.
+thread.  You must implement the functions described below, which are for
+use by test programs.  We have provided skeleton definitions for them in
+@file{threads/thread.c}.  by test programs
 
 @deftypefun int thread_get_nice (void)
 Returns the current thread's @var{nice} value.