1 files changed, 4 insertions, 4 deletions

diff --git a/spec/dir-spec/client-operation.md b/spec/dir-spec/client-operation.md
index 3f19a61..42a5906 100644
--- a/spec/dir-spec/client-operation.md
+++ b/spec/dir-spec/client-operation.md
@@ -55,7 +55,7 @@ as indicated above. When bootstrap completes, Tor will be ready to handle
 an application requesting an internal circuit to hidden services at
 ".onion" addresses.
 
-If a future consensus contains Exits, exit circuits may become available.]
+If a future consensus contains Exits, exit circuits may become available.\]
 
 (Note: clients can and should pick caches based on the network-status
 information they have: once they have first fetched network-status info
@@ -95,7 +95,7 @@ most recent consensus it has if that consensus is "reasonably live". A
 Clients try to have the best descriptor for each router.  A descriptor is
 "best" if:
 
-* It is listed in the consensus network-status document.
+- It is listed in the consensus network-status document.
 
 Periodically (currently every 10 seconds) clients check whether there are
 any "downloadable" descriptors.  A descriptor is downloadable if:
@@ -182,7 +182,7 @@ We follow the same splitting and back-off rules as in section 5.2.
 
 ## Using directory information
 
-[XXX This subsection really belongs in path-spec.txt, not here. -KL]
+\[XXX This subsection really belongs in path-spec.txt, not here. -KL\]
 
 Everyone besides directory authorities uses the approaches in this section
 to decide which relays to use and what their keys are likely to be.
@@ -194,7 +194,7 @@ above.)
 ### Choosing routers for circuits
 
 Circuits SHOULD NOT be built until the client has enough directory
-information: a live consensus network status [XXXX fallback?]  and
+information: a live consensus network status \[XXXX fallback?\]  and
 descriptors for at least 1/4 of the relays believed to be running.
 
 A relay is "listed" if it is included by the consensus network-status