diff --git a/docs/internals/contributing/writing-documentation.txt b/docs/internals/contributing/writing-documentation.txt
index 1258d4686f..2654cce06e 100644
--- a/docs/internals/contributing/writing-documentation.txt
+++ b/docs/internals/contributing/writing-documentation.txt
@@ -191,7 +191,7 @@ If you encounter false-positives (error output that actually is correct), do
 one of the following:
 
 * Surround inline code or brand/technology names with double grave accents
-  (``).
+  (\`\`)
 * Find synonyms that the spell checker recognizes.
 * If, and only if, you are sure the word you are using is correct - add it
   to ``docs/spelling_wordlist`` (please keep the list in alphabetical order).
diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt
index dbfa2c8c1e..9cb1ddda23 100644
--- a/docs/topics/cache.txt
+++ b/docs/topics/cache.txt
@@ -10,8 +10,8 @@ processing-overhead perspective, than your standard
 read-a-file-off-the-filesystem server arrangement.
 
 For most web applications, this overhead isn't a big deal. Most web
-applications aren't ``washingtonpost.com`` or ``slashdot.org``; they're small-
-to medium-sized sites with so-so traffic. But for medium- to high-traffic
+applications aren't ``washingtonpost.com`` or ``slashdot.org``; they're
+small-to medium-sized sites with so-so traffic. But for medium- to high-traffic
 sites, it's essential to cut as much overhead as possible.
 
 That's where caching comes in.