X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Ftour.texi;h=845a1c8b6f68904eb3289ed532e93b065832d853;hb=841338bbc961acad4ca01edb7b140578b477e1cf;hp=ed1f92be1bad527cdc7574371dc917a16f7b603b;hpb=5d3c07d8b0aad51ade536e35f63267f5826524c5;p=pintos-anon

diff --git a/doc/tour.texi b/doc/tour.texi
index ed1f92b..845a1c8 100644
--- a/doc/tour.texi
+++ b/doc/tour.texi
@@ -553,8 +553,10 @@ A semaphore initialized to 0 can be useful for waiting for an event
 that will happen exactly once.  For example, suppose thread @var{A}
 starts another thread @var{B} and wants to wait for @var{B} to signal
 that some activity is complete.  @var{A} can create a semaphore
-initialized to 0, pass it to @var{B}, and then ``down'' the semaphore.
-When @var{B} finishes its activity, it ``ups'' the semaphore.
+initialized to 0, pass it to @var{B} as it starts it, and then
+``down'' the semaphore.  When @var{B} finishes its activity, it
+``ups'' the semaphore.  This works regardless of whether @var{A}
+``downs'' the semaphore or @var{B} ``ups'' it first.
 
 Pintos declared its semaphore type and operations on them in
 @file{threads/synch.h}.