minor doc patches

svn:r212

3 files changed, 3 insertions, 3 deletions

diff --git a/doc/FAQ b/doc/FAQ
index d4d7a46a2..bd3a96306 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -12,7 +12,7 @@ service. Users build a layered block of asymmetric encryptions
 (an "onion") which describes a source-routed path through a set of
 nodes. Those nodes build a "virtual circuit" through the network, in which
 each node knows its predecessor and successor, but no others. Traffic
-flowing down the circuit is unwrapped by a symmetric key at each node
+flowing down the circuit is unwrapped by a symmetric key at each node,
 which reveals the downstream node.
 
 Basically tor provides a distributed network of servers ("onion
diff --git a/doc/TODO b/doc/TODO
index 74f38ca93..f7b5c0110 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -25,7 +25,7 @@ NICK            . Handle half-open connections
 NICK            - Look at what ssl does to keep from mutating data streams
 NICK    . On the fly compression of each stream
         o Clean up the event loop (optimize and sanitize)
-ARMA    - Remove that awful concept of 'roles'
+ARMA    o Remove that awful concept of 'roles'
 ARMA    - Exit policies
                 - Spec how to write the exit policies
                 - Path selection algorithms
diff --git a/doc/tor-spec.txt b/doc/tor-spec.txt
index 9d35949aa..ab729346d 100644
--- a/doc/tor-spec.txt
+++ b/doc/tor-spec.txt
@@ -357,7 +357,7 @@ which reveals the downstream node.
           begin queueing CREATE cells for this circuit.
 
           Otherwise, we have a half-open circuit.  If the total payload
-          length of the CREATE cells for this circuit is at exactly equal
+          length of the CREATE cells for this circuit is exactly equal
           to the onion length specified in the first cell (minus 4), then
           process the onion. If it is more, then tear down the circuit.