[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[or-cvs] r10415: clean up a few confusions brian levine pointed out (tor/trunk/doc/spec)



Author: arma
Date: 2007-05-30 23:47:41 -0400 (Wed, 30 May 2007)
New Revision: 10415

Modified:
   tor/trunk/doc/spec/path-spec.txt
Log:
clean up a few confusions brian levine pointed out


Modified: tor/trunk/doc/spec/path-spec.txt
===================================================================
--- tor/trunk/doc/spec/path-spec.txt	2007-05-30 09:21:12 UTC (rev 10414)
+++ tor/trunk/doc/spec/path-spec.txt	2007-05-31 03:47:41 UTC (rev 10415)
@@ -316,9 +316,10 @@
   probability (N-C)/N of choosing a good entry and not being profiled.
 
   When guard nodes are enabled, Tor maintains an ordered list of entry nodes
-  as our chosen guards, and store this list persistently to disk.  If a Guard
+  as our chosen guards, and stores this list persistently to disk.  If a Guard
   node becomes unusable, rather than replacing it, Tor adds new guards to the
-  end of the list.  When it comes time to choose an entry, Tor chooses at
+  end of the list.  When choosing the first hop of a circuit, Tor
+  chooses at
   random from among the first NumEntryGuards (default 3) usable guards on the
   list.  If there are not at least 2 usable guards on the list, Tor adds
   routers until there are, or until there are no more usable routers to add.