Apply suggestions from code review

Co-Authored-By: David I. Lehn <[email protected]>

Author: gkellogg

index.html

@@ -3673,7 +3673,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     The rationale is that the new definition does not violate the protection,
     as it does not change the semantics of the protected term.
     This is useful for widespread term definitions,
-    such as e.g. aliasing <code>@type</code> to <code>type</code>,
+    such as aliasing <code>@type</code> to <code>type</code>,
     which may occur (including in a protected form) in several contexts.
   </p>
 
@@ -3704,7 +3704,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
           {
             ****"id": "@id",
             "type": "@type",****
-            ####­– Those "redefinition" do not raise an error.
+            ####­– Those "redefinitions" do not raise an error.
             ­– Note however that the terms are still protected ####
             "Person": "http://schema.org/Person",
             "name": "http://schema.org/name"
@@ -12832,7 +12832,7 @@ <h2>Changes since JSON-LD Community Group Final Report</h2>
       using type <code>application/ld+json;profile=http://www.w3.org/ns/json-ld#frame</code>.</li>
     <li>Term definitions can now be <a href="#protected-term-definitions">protected</a>,
       to limit the ability of other contexts to override them.</li>
-    </ul>
+  </ul>
 </section>
 
 <section id="ack"