aboutsummaryrefslogtreecommitdiff
path: root/spec/dir-spec
diff options
context:
space:
mode:
Diffstat (limited to 'spec/dir-spec')
-rw-r--r--spec/dir-spec/exchanging-votes.md2
-rw-r--r--spec/dir-spec/extra-info-document-format.md6
-rw-r--r--spec/dir-spec/limited-ed-diff-format.md2
-rw-r--r--spec/dir-spec/outline.md2
-rw-r--r--spec/dir-spec/serving-bandwidth-list-files.md4
5 files changed, 8 insertions, 8 deletions
diff --git a/spec/dir-spec/exchanging-votes.md b/spec/dir-spec/exchanging-votes.md
index aac1d4b..066f825 100644
--- a/spec/dir-spec/exchanging-votes.md
+++ b/spec/dir-spec/exchanging-votes.md
@@ -38,7 +38,7 @@ at
`http://<hostname>/tor/status-vote/next/<fp>.z`
-where <fp> is the fingerprint of the other authority's identity key.
+where `<fp>` is the fingerprint of the other authority's identity key.
And at
`http://<hostname>/tor/status-vote/next/d/<d>.z`
diff --git a/spec/dir-spec/extra-info-document-format.md b/spec/dir-spec/extra-info-document-format.md
index a821ecc..7307885 100644
--- a/spec/dir-spec/extra-info-document-format.md
+++ b/spec/dir-spec/extra-info-document-format.md
@@ -128,13 +128,13 @@ per protocol family.
List of mappings from pluggable transport names to the number
of unique IP addresses that have connected using that
pluggable transport. Unobfuscated connections are counted
-using the reserved pluggable transport name "<OR>" (without
+using the reserved pluggable transport name "`<OR>`" (without
quotes). If we received a connection from a transport proxy
but we couldn't figure out the name of the pluggable
transport, we use the reserved pluggable transport name
-"<??>".
+"`<??>`".
-("<OR>" and "<??>" are reserved because normal pluggable
+("`<OR>`" and "`<??>`" are reserved because normal pluggable
transport names MUST match the following regular expression:
"[a-zA-Z_][a-zA-Z0-9_]*" )
diff --git a/spec/dir-spec/limited-ed-diff-format.md b/spec/dir-spec/limited-ed-diff-format.md
index 53fa334..f6a2d61 100644
--- a/spec/dir-spec/limited-ed-diff-format.md
+++ b/spec/dir-spec/limited-ed-diff-format.md
@@ -27,7 +27,7 @@ lines are only ever referred to by their position in the original
file.
If there are any directory signatures on the original document, the
-first command MUST be a "<n1>,$d" form to remove all of the directory
+first command MUST be a "`<n1>,$d`" form to remove all of the directory
signatures. Using this format ensures that the client will
successfully apply the diff even if they have an unusual encoding for
the signatures.
diff --git a/spec/dir-spec/outline.md b/spec/dir-spec/outline.md
index 55deb49..faa848a 100644
--- a/spec/dir-spec/outline.md
+++ b/spec/dir-spec/outline.md
@@ -170,7 +170,7 @@ The Initial Item must be the first item in the document.
The Signature Item has the following format:
-<signature item keyword> [arguments] NL SIGNATURE NL
+`<signature item keyword> [arguments] NL SIGNATURE NL`
The "SIGNATURE" Object contains a signature (using the signing key) of
the PKCS#1 1.5 padded digest of the entire document, taken from the
diff --git a/spec/dir-spec/serving-bandwidth-list-files.md b/spec/dir-spec/serving-bandwidth-list-files.md
index 1263e43..253f2d6 100644
--- a/spec/dir-spec/serving-bandwidth-list-files.md
+++ b/spec/dir-spec/serving-bandwidth-list-files.md
@@ -347,9 +347,9 @@ This sorting algorithm is used for consensus-method 22 and later.
Deciding which descriptors to include.
-A tuple belongs to an <id-RSA, id-Ed> identity if it is a new tuple that
+A tuple belongs to an `<id-RSA, id-Ed>` identity if it is a new tuple that
matches both ID parts, or if it is an old tuple (one with no Ed opinion)
-that matches the RSA part. A tuple belongs to an <id-RSA> identity if its
+that matches the RSA part. A tuple belongs to an `<id-RSA>` identity if its
RSA identity matches.
A tuple matches another tuple if all the fields that are present in both