Fix spelling and markup.

davidlehn · davidlehn · commit 7d148ae8d871 · 2018-05-15T13:51:01.000-04:00
diff --git a/spec/latest/json-ld-api-best-practices/index.html b/spec/latest/json-ld-api-best-practices/index.html
@@ -32,7 +32,7 @@
   <body>
     <section id='abstract'>
       <p>
-        Developers share a common problem: they want a simple, but extensible way to create an API for a web service that gets the job done, doesn't design them into a corner, and allows developers to easily interact with their service without reinventing the wheel. JSON-LD [[JSON-LD]] has become an important solution, as it bridges the gap between formally data and more coloquial JSON interfaces used in APIs from numerous providers. This guide attempts to define certain best practices for publishing data using JSON-LD, and interacting with such services.
+        Developers share a common problem: they want a simple, but extensible way to create an API for a web service that gets the job done, doesn't design them into a corner, and allows developers to easily interact with their service without reinventing the wheel. JSON-LD [[JSON-LD]] has become an important solution, as it bridges the gap between formally data and more colloquial JSON interfaces used in APIs from numerous providers. This guide attempts to define certain best practices for publishing data using JSON-LD, and interacting with such services.
       </p>
     </section>
 
@@ -126,7 +126,7 @@ <h2>Resource Representation</h2>
               }
             ]
           </pre>
-          <p>Expanded form is not useful as is, but is necessary for performing further algorithmic transformaions of JSON-LD data and is useful when validating that JSON-LD entity descriptions say what the publisher means.</p>
+          <p>Expanded form is not useful as is, but is necessary for performing further algorithmic transformations of JSON-LD data and is useful when validating that JSON-LD entity descriptions say what the publisher means.</p>
         </div>
       </div>
 
@@ -137,7 +137,7 @@ <h2>Resource Representation</h2>
 
       <div class="practice">
         <p><span id="top-level-object" class="practicelab">Use a top-level object</span></p>
-        <p class="practicedesc">JSON documents may be in the form of a object, or an array of objects. For most purposes, develpers need a single entrypoint, so the JSON SHOULD be in the form of a single top-level object</p>
+        <p class="practicedesc">JSON documents may be in the form of a object, or an array of objects. For most purposes, developers need a single entry point, so the JSON SHOULD be in the form of a single top-level object</p>
       </div>
 
       <div class="practice">
@@ -153,7 +153,7 @@ <h2>Resource Representation</h2>
       <div class="practice">
         <p><span id="typed-objects" class="practicelab">Provide one or more types for JSON objects</span></p>
         <p class="practicedesc">Principles of <a>Linked Data</a> dictate that messages SHOULD be self describing, which includes adding a <code>type</code> to such messages.</p>
-        <p>Many APIs use JSON messages where the type of information being conveyed is inferred from the retreaval endpoint. For example, when retrieving information about a Github Commit, you might see the following response:</p>
+        <p>Many APIs use JSON messages where the type of information being conveyed is inferred from the retrieval endpoint. For example, when retrieving information about a Github Commit, you might see the following response:</p>
         <pre class="example" title="Github Commit message">
           {
             "sha": "7638417db6d59f3c431d3e1f261cc637155684cd",
@@ -292,7 +292,7 @@ <h2>Resource Representation</h2>
         <pre class="example" title="Example enumerated value">
           {
             "@context": ["http://schema.org", <strong>{
-              <strong>"gender": {"@id": "schema:gender", "@type": "@vocab"}</strong>
+              "gender": {"@id": "schema:gender", "@type": "@vocab"}
             }</strong>],
             "id": "https://www.wikidata.org/wiki/Q76",
             "type": "Person",
