aboutsummaryrefslogtreecommitdiff
path: root/spec/path-spec/attaching-streams-to-circuits.md
diff options
context:
space:
mode:
Diffstat (limited to 'spec/path-spec/attaching-streams-to-circuits.md')
-rw-r--r--spec/path-spec/attaching-streams-to-circuits.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/spec/path-spec/attaching-streams-to-circuits.md b/spec/path-spec/attaching-streams-to-circuits.md
index e03414e..585885b 100644
--- a/spec/path-spec/attaching-streams-to-circuits.md
+++ b/spec/path-spec/attaching-streams-to-circuits.md
@@ -6,7 +6,7 @@ When a circuit that might support a request is built, Tor tries to attach
the request's stream to the circuit and sends a BEGIN, BEGIN_DIR,
or RESOLVE relay
cell as appropriate. If the request completes unsuccessfully, Tor
-considers the reason given in the CLOSE relay cell. [XXX yes, and?]
+considers the reason given in the CLOSE relay cell. \[XXX yes, and?\]
After a request has remained unattached for SocksTimeout (2 minutes
by default), Tor abandons the attempt and signals an error to the
@@ -14,6 +14,6 @@ client as appropriate (e.g., by closing the SOCKS connection).
XXX Timeouts and when Tor auto-retries.
-* What stream-end-reasons are appropriate for retrying.
+- What stream-end-reasons are appropriate for retrying.
If no reply to BEGIN/RESOLVE, then the stream will timeout and fail.