[or-cvs] [tor/master 5/5] tor-spec.txt tweaks from arma

[nickm@xxxxxxxxxxxxxx]

Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date: Wed, 15 Sep 2010 13:08:44 -0400
Subject: tor-spec.txt tweaks from arma
Commit: 69508d04a2db530c0bbb4c1cc421e6b258b822be

---
 doc/spec/tor-spec.txt |   13 ++++++-------
 1 files changed, 6 insertions(+), 7 deletions(-)

diff --git a/doc/spec/tor-spec.txt b/doc/spec/tor-spec.txt
index 314169f..a08005c 100644
--- a/doc/spec/tor-spec.txt
+++ b/doc/spec/tor-spec.txt
@@ -598,13 +598,12 @@ see tor-design.pdf.
    RELAY_TRUNCATED cell.
 
    [Note: If an OR receives a TRUNCATE cell and it has any RELAY cells
-   still queued on the circuit for the next node that it had not yet sent,
-   it will drop them without sending them.  This is not considered
-   conformant behavior, but it probably won't get fixed till a later
-   version of Tor.  Thus, clients SHOULD NOT send a TRUNCATE cell to a
-   node running any current version of Tor if they have sent relay cells
-   through that node, and they aren't sure whether those cells have been
-   sent on.]
+   still queued on the circuit for the next node it will drop them
+   without sending them.  This is not considered conformant behavior,
+   but it probably won't get fixed until a later version of Tor.  Thus,
+   clients SHOULD NOT send a TRUNCATE cell to a node running any current
+   version of Tor if a) they have sent relay cells through that node,
+   and b) they aren't sure whether those cells have been sent on yes.]
 
    When an unrecoverable error occurs along one connection in a
    circuit, the nodes on either side of the connection should, if they
-- 
1.7.1