X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fthreads.texi;h=a28d7a41d1c14842c8ee65a8ca3bf26c177c4ff8;hb=34ff639aaa7fd691d2e588d46acd41669c0b5754;hp=d83b52f4525770b2a89d7768713426e1ad1821b0;hpb=c7ceee91c04fa72da655c00cb82302537ff6c9eb;p=pintos-anon

diff --git a/doc/threads.texi b/doc/threads.texi
index d83b52f..a28d7a4 100644
--- a/doc/threads.texi
+++ b/doc/threads.texi
@@ -675,7 +675,7 @@ list.
 
 @item If the highest-priority thread yields, does it continue running?
 
-Yes.  As long as there is a single highest-priority thread, it continues
+Yes.  If there is a single highest-priority thread, it continues
 running until it blocks or finishes, even if it calls
 @func{thread_yield}.
 If multiple threads have the same highest priority,
@@ -730,9 +730,6 @@ scheduler at the same time.
 
 @item Can I use one queue instead of 64 queues?
 
-Yes, that's fine.  It's easiest to describe the algorithm in terms of 64
-separate queues, but that doesn't mean you have to implement it that
-way.
-
-If you use a single queue, it should probably be sorted.
+Yes.  In general, your implementation may differ from the description,
+as long as its behavior is the same.
 @end table