Update formatting

website/docs/api/lexeme.jade

@@ -4,7 +4,7 @@ include ../../_includes/_mixins
 
 p
     |  An entry in the vocabulary. A #[code Lexeme] has no string context – it's
-    |  a word-type, as opposed to a word token. It therefore has no
+    |  a word type, as opposed to a word token. It therefore has no
     |  part-of-speech tag, dependency parse, or lemma (if lemmatization depends
     |  on the part-of-speech tag).
 

website/docs/api/vocab.jade

@@ -3,7 +3,7 @@
 include ../../_includes/_mixins
 
 p
-    |  A look-up table that allows you to access #[code Lexeme] objects. The
+    |  A lookup table that allows you to access #[code Lexeme] objects. The
     |  #[code Vocab] instance also provides access to the #[code StringStore],
     |  and owns underlying C-data that is shared between #[code Doc] objects.
 

website/docs/usage/adding-languages.jade

@@ -384,8 +384,6 @@ p
         "ababábites": "ababábite"
     }
 
-+aside("Where can I find lemmatizer data?")
-
 p
     |  To add a lookup lemmatizer to your language, import the #[code LOOKUP]
     |  table and #[code Lemmatizer], and create a new classmethod:

website/docs/usage/rule-based-matching.jade

@@ -283,7 +283,6 @@ p
     # set manual=True to make displaCy render straight from a dictionary
     displacy.serve(matched_sents, style='ent', manual=True)
 
-
 +h(3, "quantifiers-example2") Quantifiers example: Phone numbers
 
 p