Fix inconstiency in recent_cpu update description.

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

diff --git a/doc/44bsd.texi b/doc/44bsd.texi
index d27343f655d979540f74b1243fcffb4000e6bbe8..e8ae11347bb9adf62ee2e7435831da58392c1937 100644 (file)
--- a/doc/44bsd.texi
+++ b/doc/44bsd.texi
@@ -182,7 +182,7 @@ current value of @var{recent_cpu} decays to a weight of .1 in
 received ``recently,'' with the rate of decay inversely proportional to
 the number of threads competing for the CPU.
 
-Assumptions made by some of the tests require that updates to
+Assumptions made by some of the tests require that these recalculations of
 @var{recent_cpu} be made exactly when the system tick counter reaches a
 multiple of a second, that is, when @code{timer_ticks () % TIMER_FREQ ==
 0}, and not at any other time.