Minor corrections from @pchampin.

Author: gkellogg

index.html

@@ -10867,7 +10867,7 @@ <h3>Graph Containers</h3>
   <p class="changed">In other cases, a resource may be returned using a representation that cannot easily be interpreted
     as JSON-LD. Normally, <a href="https://en.wikipedia.org/wiki/Content_negotiation">HTTP content negotiation</a>
     would be used to allow a client to specify a preference for JSON-LD over another representation,
-    but in certain situations, it is not possible for a server to respond appropriately to such requests.
+    but in certain situations, it is not possible or practical for a server to respond appropriately to such requests.
     For this, an <a>HTTP Link Header</a> can be used to provide an alternate location for a document
     to be used in place of the originally requested resource,
     as described in <a href="#alternate-document-location" class="sectionRef"></a>.</p>
@@ -10951,7 +10951,7 @@ <h3>Graph Containers</h3>
 <section class="normative changed"><h3>Alternate Document Location</h3>
 
   <p>Documents which can't be directly interpreted as JSON-LD can provide an alternate location containing JSON-LD.
-    One way to provide this is by using referencing a JSON-LD document in an <a>HTTP Link Header</a>.
+    One way to provide this is by referencing a JSON-LD document in an <a>HTTP Link Header</a>.
     This might be useful, for example, when the URL associated with a namespace naturally
     contains an HTML document, but the JSON-LD context associated with that URL is located elsewhere.</p>