Apply "cell" and "message" consistently

Done by grepping for "cell" and making sure it was accurate in every
place where it occurs.  In tor-spec, I also searched for "message".

Part of #253.

1 files changed, 7 insertions, 7 deletions

diff --git a/spec/control-spec/replies.md b/spec/control-spec/replies.md
index 4046d6d..6fce9b1 100644
--- a/spec/control-spec/replies.md
+++ b/spec/control-spec/replies.md
@@ -292,8 +292,8 @@ The syntax is:
                            has become redundant, since some other circuit
                            opened in parallel with it has succeeded.)
 
-   The "REMOTE_REASON" field is provided only when we receive a DESTROY or
-   TRUNCATE cell, and only if extended events are enabled.  It contains the
+   The "REMOTE_REASON" field is provided only when we receive a DESTROY cell or
+   RELAY_TRUNCATE message, and only if extended events are enabled.  It contains the
    actual reason given by the remote OR for closing the circuit. Clients MUST
    accept reasons not listed above.  Reasons are as listed in tor-spec.txt.
    [Added in Tor 0.4.3.1-alpha.]
@@ -319,8 +319,8 @@ The syntax is:
                "NEW"          / ; New request to connect
                "NEWRESOLVE"   / ; New request to resolve an address
                "REMAP"        / ; Address re-mapped to another
-               "SENTCONNECT"  / ; Sent a connect cell along a circuit
-               "SENTRESOLVE"  / ; Sent a resolve cell along a circuit
+               "SENTCONNECT"  / ; Sent a connect message along a circuit
+               "SENTRESOLVE"  / ; Sent a resolve message along a circuit
                "SUCCEEDED"    / ; Received a reply; stream established
                "FAILED"       / ; Stream failed and not retriable
                "CLOSED"       / ; Stream closed
@@ -383,14 +383,14 @@ to talk to itself.
    accept reasons not listed above.  Reasons are as given in tor-spec.txt,
    except for:
 
-      END          (We received a RELAY_END cell from the other side of this
+      END          (We received a RELAY_END message from the other side of this
                     stream.)
       PRIVATE_ADDR (The client tried to connect to a private address like
                     127.0.0.1 or 10.0.0.1 over Tor.)
       [XXXX document more. -NM]
 
    The "REMOTE_REASON" field is provided only when we receive a RELAY_END
-   cell, and only if extended events are enabled.  It contains the actual
+   message, and only if extended events are enabled.  It contains the actual
    reason given by the remote OR for closing the stream. Clients MUST accept
    reasons not listed above.  Reasons are as listed in tor-spec.txt.
 
@@ -1524,7 +1524,7 @@ The syntax is:
 ID is the locally unique circuit identifier that is only included if the
 circuit originates at this node.
 
-Inbound and outbound refer to the direction of cell flow through the
+Inbound and outbound refer to the direction of relay cell flow through the
 circuit which is either to origin (inbound) or from origin (outbound).
 
 InboundQueue and OutboundQueue are identifiers of the inbound and