Fix typos.

Author: davidlehn

common/terms.html

@@ -126,7 +126,7 @@
     A <a>list</a> is an ordered sequence of <a>IRIs</a>, <a>blank nodes</a>, and <a>literals</a>.</dd>
   <dt><dfn data-cite="RDF11-CONCEPTS#dfn-literal" data-lt="RDF literal" class="preserve">literal</dfn></dt><dd>
     An <a>object</a> expressed as a value such as a <a>string</a> or <a>number</a>.
-    Implicitlly or explicitly includes a <a>datatype IRI</a> and, if the datatype is `rdf:langString`, an optional <a>language tag</a>.</dd>
+    Implicitly or explicitly includes a <a>datatype IRI</a> and, if the datatype is `rdf:langString`, an optional <a>language tag</a>.</dd>
   <dt><dfn data-cite="RDF11-CONCEPTS#dfn-named-graph" class="preserve">named graph</dfn></dt><dd>
     A <a>named graph</a>
     is a <a>linked data graph</a> that is identified by an <a>IRI</a> or <a>blank node</a>.</dd>
@@ -179,7 +179,7 @@
     as the <code>@context</code> <a>entry</a> of one of the following:
     a <a>node object</a>, a <a>value object</a>, a <a>graph object</a>, a <a>list object</a>,
     a <a>set object</a>, the value of a <a>nested properties</a>,
-    or the value of an <a>expanded term definition</a></span>.
+    or the value of an <a>expanded term definition</a>.
     Its value may be a <a>map</a> for a <a data-cite="JSON-LD11#dfn-context-definition">context definition</a>,
     as an <a>IRI</a>, or as an <a>array</a> combining either of the above.
   </dd>

index.html

@@ -615,7 +615,7 @@ <h2>Syntax Tokens and Keywords</h2>
         Setting this to `false` causes term definitions created within that context
         to be removed when entering a new <a>node object</a>.</dd>
       <dt class="changed">`@protected`</dt><dd class="changed">
-        Used to prevent <a>term definitions</a> of a context to be overriden by other contexts.
+        Used to prevent <a>term definitions</a> of a context to be overridden by other contexts.
         This keyword is described in <a class="sectionRef" href="#protected-term-definitions"></a>.
       <dt class="changed">`@import`</dt><dd class="changed">
         Used in a <a>context definition</a> to load an external context
@@ -1347,7 +1347,7 @@ <h2>Uses of JSON Objects</h2>
     <li><a>Numbers</a>, which describe literal numeric values,</li>
     <li><a>Strings</a>, which may describe literal string values, or be used as the keys in a <a>JSON object</a>.</li>
     <li><a>Boolean</a> <code>true</code> and <code>false</code>, which describe literal boolean values,</li>
-    <li><code>null</code>, which describes the absense of a value,</li>
+    <li><code>null</code>, which describes the absence of a value,</li>
     <li><a>Arrays</a>, which describe an ordered set of values of any type, and</li>
     <li><a>JSON objects</a>, which provide a set of <a>map entries</a>, relating keys with values.</li>
   </ul>
@@ -3546,7 +3546,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
     and then that term is later redefined,
     the association of the context defined in the earlier
     <a>expanded term definition</a> is lost
-    within the scope of that redefnition. This is consistent with
+    within the scope of that redefinition. This is consistent with
     <a>term definitions</a> of a term overriding previous term definitions from
     earlier less deeply nested definitions, as discussed in
     <a href="#advanced-context-usage" class="sectionRef"></a>.</p>
@@ -4045,7 +4045,7 @@ <h3>Using the Document Base for the Default Vocabulary</h3>
       @prefix schema: <http://schema.org/>.
 
       <https://digitalbazaar.com/> a o:Organization ;
-        o:membet <http://manu.sporny.org/about#manu>.
+        o:member <http://manu.sporny.org/about#manu>.
 
       <http://manu.sporny.org/about#manu> a schema:Person ;
         schema:name "Manu Sporny".
@@ -9672,7 +9672,7 @@ <h3>Graph Containers</h3>
     <li>Certain well-known contexts may be statically cached within a <a>documentLoader</a> implementation.
       This might be particularly useful in embedded applications,
       where it is not feasible, or even possible, to access remote documents.</li>
-    <li>For security purposes, the act of remotely retriving a document may provide a signal of application behavior.
+    <li>For security purposes, the act of remotely retrieving a document may provide a signal of application behavior.
       The judicious use of a <a>documentLoader</a> can isolate the application and reduce its online fingerprint.</li>
   </ul>
 </section>
@@ -10205,7 +10205,7 @@ <h3>Graph Containers</h3>
     <p>Properties with multiple values are typically represented using
       an unordered <a>array</a>. This means that an application working
       on an internalized representation of that JSON would need to
-      iterrate through the values of the array to find a value matching
+      iterate through the values of the array to find a value matching
       a particular pattern, such as a <a>language-tagged string</a>
       using the language <code>en</code>.</p>
 
@@ -10756,7 +10756,7 @@ <h3>Graph Containers</h3>
 
   <p>The JSON-LD 1.1 Processing Algorithms and API specification [[JSON-LD11-API]]
     provides for an <a data-cite="JSON-LD11-API#dom-jsonldoptions-expandcontext">expandContext</a> option for specifying
-    a <a>context</a> to use when expanding JSON documents programatically.</p>
+    a <a>context</a> to use when expanding JSON documents programmatically.</p>
 
   <p>The following example demonstrates the use of an external context with an
     ordinary JSON document over HTTP:</p>
@@ -10845,7 +10845,7 @@ <h3>Graph Containers</h3>
   -->
   </pre>
 
-  <p>A processor seeing a non-JSON result will note the presense of the link header
+  <p>A processor seeing a non-JSON result will note the presence of the link header
     and load that document instead.</p>
 </section>
 </section>
@@ -12008,7 +12008,7 @@ <h2>Context Definitions</h2>
     <code class="changed">@propagate</code>,
     <code class="changed">@protected</code>,
     <code class="changed">@type</code>,
-    <code class="changed">@version</code>.
+    <code class="changed">@version</code>,
     or <code>@vocab</code>.
   </p>
 
@@ -12612,7 +12612,7 @@ <h3>Security Considerations</h3>
   <h3>Privacy Considerations</h3>
   <p>The retrieval of external contexts can expose the operation of a JSON-LD processor,
     allow intermediate nodes to fingerprint the client application through introspection of retrieved resources
-    (see [[?fingerprinting-guidance]]), and
+    (see [[?fingerprinting-guidance]]),
     and provide an opportunity for a man-in-the-middle attack.
     To protect against this, publishers should consider caching remote contexts for future use,
     or use the <a>documentLoader</a>
@@ -12649,7 +12649,7 @@ <h3>Internationalization Considerations</h3>
 
 <section class="appendix informative"><h2>Image Descriptions</h2>
   <section id="fig-linked-data-graph-descr" class="informative"><h3>Linked Data Dataset</h3>
-      <p>This secrion describes the <a href="#fig-linked-data-graph">Linked Data Dataset figure</a> in <a href="#data-model" class="sectionRef"></a>.</p>
+      <p>This section describes the <a href="#fig-linked-data-graph">Linked Data Dataset figure</a> in <a href="#data-model" class="sectionRef"></a>.</p>
       <p>The image consists of three dashed boxes, each describing a different
         <a>linked data graph</a>. Each box consists of shapes linked with arrows describing
         the linked data relationships.</p>
@@ -13040,7 +13040,7 @@ <h3>application/ld+json</h3>
           <p>All other URIs starting with <code>http://www.w3.org/ns/json-ld</code>
             are reserved for future use by JSON-LD specifications.</p>
           <p class="note">Other specifications may publish additional profile parameter
-            URIs with their own defined sematics.</p>
+            URIs with their own defined semantics.</p>
           <p>
             When used as a <a data-cite="RFC4288#section-4.3">media type parameter</a> [[RFC4288]]
             in an <a data-cite="rfc7231#section-5.3.2">HTTP Accept header</a> [[RFC7231]],
@@ -13232,7 +13232,7 @@ <h2>Changes since 1.0 Recommendation of 16 January 2014</h2>
   <h2>Changes since JSON-LD Community Group Final Report</h2>
   <ul>
     <li><a>Lists</a> may now have items which are themselves <a>lists</a>.</li>
-    <li>Values of <code>@type</code>, or an alais of <code>@type</code>, may now have their <code>@container</code> set to <code>@set</code>
+    <li>Values of <code>@type</code>, or an alias of <code>@type</code>, may now have their <code>@container</code> set to <code>@set</code>
       to ensure that <code>@type</code> <a>entries</a> are always represented as an array. This
       also allows a term to be defined for <code>@type</code>, where the value MUST be a <a>map</a>
       with <code>@container</code> set to <code>@set</code>.</li>