aboutsummaryrefslogtreecommitdiff
path: root/spec/tor-spec/closing-streams.md
diff options
context:
space:
mode:
Diffstat (limited to 'spec/tor-spec/closing-streams.md')
-rw-r--r--spec/tor-spec/closing-streams.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/spec/tor-spec/closing-streams.md b/spec/tor-spec/closing-streams.md
index 9ef1b98..5fa84a8 100644
--- a/spec/tor-spec/closing-streams.md
+++ b/spec/tor-spec/closing-streams.md
@@ -42,7 +42,7 @@ versions of Tor may provide more fine-grained reasons.
For most reasons, the format of RELAY_END is:
-Reason [1 byte]
+Reason \[1 byte\]
For REASON_EXITPOLICY, the format of RELAY_END is:
@@ -72,7 +72,7 @@ how many cells of which types (CONNECTED, SENDME, DATA) that it would have
accepted on that stream, and SHOULD kill the circuit if it receives more
than permitted.
---- [The rest of this section describes unimplemented functionality.]
+--- \[The rest of this section describes unimplemented functionality.\]
Because TCP connections can be half-open, we follow an equivalent
to TCP's FIN/FIN-ACK/ACK protocol to close streams.