[or-cvs] [tor/master 3/5] Make tor-spec wording easier to understand

[nickm at torproject.org]

Author: Sebastian Hahn <sebastian at torproject.org>
Date: Tue, 3 Aug 2010 17:28:19 +0200
Subject: Make tor-spec wording easier to understand
Commit: 4e3373f7fe24c281b88c9a139854afa1c213d163

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

diff --git a/doc/spec/tor-spec.txt b/doc/spec/tor-spec.txt
index d0c60c0..314169f 100644
--- a/doc/spec/tor-spec.txt
+++ b/doc/spec/tor-spec.txt
@@ -597,13 +597,14 @@ see tor-design.pdf.
    cell to the next node in the circuit, and replies to the OP with a
    RELAY_TRUNCATED cell.
 
-   [Note: If an OR receives a TRUNCATE cell and it any RELAY cells queued on
-   the circuit for the next node in 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 versions 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.]
+   [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.]
 
    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