Several more warnings from markdownlint.

4 files changed, 10 insertions, 12 deletions

diff --git a/spec/dir-spec/directory-cache-operation.md b/spec/dir-spec/directory-cache-operation.md
index 1aa3f4b..8b3bfce 100644
--- a/spec/dir-spec/directory-cache-operation.md
+++ b/spec/dir-spec/directory-cache-operation.md
@@ -151,7 +151,7 @@ send that diff instead of the specified consensus.
 
 Caches also serve diffs from the URIs:
 
-```
+```text
 /tor/status-vote/current/consensus/diff/<HASH>/<FPRLIST>.z
 /tor/status-vote/current/consensus-<FLAVOR>/diff/<HASH>/<FPRLIST>.z
 ```
diff --git a/spec/dir-spec/extra-info-document-format.md b/spec/dir-spec/extra-info-document-format.md
index 7307885..1c7dffe 100644
--- a/spec/dir-spec/extra-info-document-format.md
+++ b/spec/dir-spec/extra-info-document-format.md
@@ -136,7 +136,7 @@ transport, we use the reserved pluggable transport name
 
 ("`<OR>`" and "`<??>`" are reserved because normal pluggable
 transport names MUST match the following regular expression:
-"[a-zA-Z_][a-zA-Z0-9_]*" )
+"`[a-zA-Z_][a-zA-Z0-9_]*`" )
 
 The pluggable transport name list is sorted into lexically
 ascending order.
diff --git a/spec/dir-spec/scope-preliminaries.md b/spec/dir-spec/scope-preliminaries.md
index 61d2ff7..1025c04 100644
--- a/spec/dir-spec/scope-preliminaries.md
+++ b/spec/dir-spec/scope-preliminaries.md
@@ -9,9 +9,9 @@ used by the 0.1.1.x and 0.1.2.x series.
 
 This document merges and supersedes the following proposals:
 
-101  Voting on the Tor Directory System
-103  Splitting identity key from regularly used signing key
-104  Long and Short Router Descriptors
+- 101  Voting on the Tor Directory System
+- 103  Splitting identity key from regularly used signing key
+- 104  Long and Short Router Descriptors
 
 XXX timeline
 XXX fill in XXXXs
@@ -29,8 +29,7 @@ The earliest versions of Onion Routing shipped with a list of known
 routers and their keys.  When the set of routers changed, users needed to
 fetch a new list.
 
-The Version 1 Directory protocol
---------------------------------
+### The Version 1 Directory protocol
 
 Early versions of Tor (0.0.2) introduced "Directory authorities": servers
 that served signed "directory" documents containing a list of signed
@@ -50,8 +49,7 @@ routers on the network, rather than a complete list of all the
 descriptors.  Clients and caches would fetch these documents far more
 frequently than they would fetch full directories.
 
-The Version 2 Directory Protocol
---------------------------------
+### The Version 2 Directory Protocol
 
 During the Tor 0.1.1.x series, Tor revised its handling of directory
 documents in order to address two major problems:
@@ -89,7 +87,7 @@ contents were substantially changed.
 
 <a id="dir-spec.txt-0.2"></a>
 
-## Goals of the version 3 protocol
+### Goals of the version 3 protocol
 
 Version 3 of the Tor directory protocol tries to solve the following
 issues:
diff --git a/spec/dir-spec/serving-bandwidth-list-files.md b/spec/dir-spec/serving-bandwidth-list-files.md
index 253f2d6..2dd5ff4 100644
--- a/spec/dir-spec/serving-bandwidth-list-files.md
+++ b/spec/dir-spec/serving-bandwidth-list-files.md
@@ -316,7 +316,7 @@ earlier item.
 
 <a id="dir-spec.txt-3.8.0.1"></a>
 
-#### Deciding which Ids to include
+### Deciding which Ids to include
 
 This sorting algorithm is used for consensus-method 22 and later.
 
@@ -876,7 +876,7 @@ once the voting period ends, regardless of the number of signatures.
 The authorities serve another consensus of each flavor "F" from the
 locations
 
-```
+```text
 /tor/status-vote/(current|next)/consensus-F.z. and
 /tor/status-vote/(current|next)/consensus-F/<FP1>+....z.
 ```