commit 051ed9a1727c83a489a2e50fd8a8ef10b117d2db Author: Robert Ransom rransom.8774@gmail.com Date: Mon May 9 19:32:55 2011 -0700
Fix minor issues --- control-spec.txt | 2 +- dir-spec.txt | 2 +- path-spec.txt | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/control-spec.txt b/control-spec.txt index c0a0a0e..38c327b 100644 --- a/control-spec.txt +++ b/control-spec.txt @@ -25,7 +25,7 @@ TC is a bidirectional message-based protocol. It assumes an underlying stream for communication between a controlling process (the "client" or "controller") and a Tor process (or "server"). The stream may be - implemented via TCP, TLS-over-TCP, a Unix-doma2in socket, or so on, + implemented via TCP, TLS-over-TCP, a Unix-domain socket, or so on, but it must provide reliable in-order delivery. For security, the stream should not be accessible by untrusted parties.
diff --git a/dir-spec.txt b/dir-spec.txt index 0e17e6e..a4dd14f 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -1448,7 +1448,7 @@ Two strategies exist on the current network for deciding on values for the Named flag. In the original version, relay operators were asked to send nickname-identity pairs to a - mailing list of Naming directory authorities operators. The + mailing list of Naming directory authorities' operators. The operators were then supposed to add the pairs to their mapping files; in practice, they didn't get to this often.
diff --git a/path-spec.txt b/path-spec.txt index 90e3160..480772e 100644 --- a/path-spec.txt +++ b/path-spec.txt @@ -147,7 +147,7 @@ of their choices. 2.1.3. Relays build circuits for testing reachability and bandwidth
Tor relays test reachability of their ORPort once they have - successfully built a circuit (on start and whenever their IP address + successfully built a circuit (on startup and whenever their IP address changes). They build an ordinary fast internal circuit with themselves as the last hop. As soon as any testing circuit succeeds, the Tor relay decides it's reachable and is willing to publish a descriptor.
tor-commits@lists.torproject.org