aboutsummaryrefslogtreecommitdiff
path: root/spec/address-spec.md
diff options
context:
space:
mode:
Diffstat (limited to 'spec/address-spec.md')
-rw-r--r--spec/address-spec.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/spec/address-spec.md b/spec/address-spec.md
index 0254e24..c3c779c 100644
--- a/spec/address-spec.md
+++ b/spec/address-spec.md
@@ -15,7 +15,7 @@ Table of Contents
# Overview
Most of the time, Tor treats user-specified hostnames as opaque: When
-the user connects to <www.torproject.org>, Tor picks an exit node and uses
+the user connects to \<www.torproject.org>, Tor picks an exit node and uses
that node to connect to "www.torproject.org". Some hostnames, however,
can be used to override Tor's default behavior and circuit-building
rules.
@@ -35,7 +35,7 @@ option or the MAPADDRESS control command.
[name-or-digest].exit
```
-Hostname is a valid hostname; [name-or-digest] is either the nickname of a
+Hostname is a valid hostname; \[name-or-digest\] is either the nickname of a
Tor node or the hex-encoded digest of that node's public key.
When Tor sees an address in this format, it uses the specified hostname as
@@ -99,7 +99,7 @@ is supported in Tor 0.2.4.10-alpha and later.
# .noconnect
-SYNTAX: [string].noconnect
+SYNTAX: \[string\].noconnect
When Tor sees an address in this format, it immediately closes the
connection without attaching it to any circuit. This is useful for