Clarify when enable_mlfqs gets set.

Thanks to "Yi Lang Mok" <yilangmok@stanford.edu> and others for
pointing this out.

diff --git a/doc/threads.texi b/doc/threads.texi
index ced5ae87aa5ff3e64c4b281851df71920ad6ecbd..77afeda0e17a49a0062062b16d6c9ba328c705b5 100644 (file)
--- a/doc/threads.texi
+++ b/doc/threads.texi
@@ -511,8 +511,8 @@ must be active, but we must be able to choose the 4.4@acronym{BSD}
 scheduler
 with the @option{-mlfqs} kernel option.  Passing this
 option sets @code{enable_mlfqs}, declared in @file{threads/init.h}, to
-true, when the options are parsed by @func{parse_options}, which happens
-through midway through @func{main}.
+true when the options are parsed by @func{parse_options}, which happens
+midway through @func{main}.
 
 When the 4.4@acronym{BSD} scheduler is enabled, threads no longer
 directly control their own priorities.  The @var{priority} argument to