--- a/spec/latest/json-ld-syntax/index.html	Mon Jan 21 19:05:09 2013 +0100
+++ b/spec/latest/json-ld-syntax/index.html	Mon Jan 21 20:04:20 2013 +0100
@@ -62,12 +62,12 @@
       authors:  [
           { name: "Manu Sporny", url: "http://digitalbazaar.com/",
             company: "Digital Bazaar", companyURL: "http://digitalbazaar.com/" },
+          { name: "Dave Longley", url: "http://digitalbazaar.com/",
+            company: "Digital Bazaar", companyURL: "http://digitalbazaar.com/"},
           { name: "Gregg Kellogg", url: "http://greggkellogg.net/",
             company: "Kellogg Associates", companyURL: "http://kellogg-assoc.com/" },
           { name: "Markus Lanthaler", url: "http://www.markus-lanthaler.com/",
             company: "Graz University of Technology", companyURL: "http://www.tugraz.at/" },
-          { name: "Dave Longley", url: "http://digitalbazaar.com/",
-            company: "Digital Bazaar", companyURL: "http://digitalbazaar.com/"},
           { name: "Niklas Lindström", url: "http://neverspace.net/" }
       ],
 
@@ -206,7 +206,7 @@
 
     <ul>
       <li>Software developers that want to encode Linked Data in a variety of
-      programing languages that can use JSON.</li>
+      programming languages that can use JSON.</li>
       <li>Software developers that want to understand the design decisions and
       language syntax for JSON-LD.</li>
       <li>Software developers that want to implement processors and APIs for
@@ -374,7 +374,7 @@
   <h1>Conformance</h1>
 
   <p>This specification describes the conformance criteria for JSON-LD documents.
-    This criteria is relevant to authors and authoring tool implementors.</p>
+    This criteria is relevant to authors and authoring tool implementers.</p>
 
   <p>A <tref>JSON-LD document</tref> complies with this specification if it follows
     the normative statements in section <a href="#json-ld-grammar"></a>. JSON documents
@@ -554,7 +554,7 @@
       the values of the <code>homepage</code> and <code>image</code> property
       can be interpreted as an <tref>IRI</tref> (<code>"@type": "@id"</code>,
       see section <a href="#iris"></a> for more details). This information gives the
-      data global context and allows developers to re-use each others data
+      data global context and allows developers to re-use each other's data
       without having to agree to how their data will interoperate on a
       site-by-site basis. External JSON-LD context documents may contain extra
       information located outside of the <code>@context</code> key, such as
@@ -591,7 +591,7 @@
 
     <p>Contexts may be used at any time a <tref>JSON object</tref> is defined
       (except inside a context definition). In particular, a
-      <tref>JSON-LD document</tref> may may use more than one context:</p>
+      <tref>JSON-LD document</tref> may use more than one context:</p>
 
     <pre class="example" data-transform="updateExample"
          title="Using multiple contexts">
@@ -708,7 +708,7 @@
         ordinary JSON document:</p>
 
       <pre class="example" data-transform="updateExample"
-           title="Referening a JSON-LD context from a JSON document via an HTTP Link Header">
+           title="Referencing a JSON-LD context from a JSON document via an HTTP Link Header">
       <!--
       GET /ordinary-json-document.json HTTP/1.1
       Host: example.com
@@ -935,7 +935,7 @@
 
   <p>To be able to externally reference nodes in a graph, it is important that each <tref>node</tref> has
     an unambiguous identifier. <tref title="IRI">IRIs</tref> are a fundamental concept of
-    <tref>Linked Data</tref>, and nodes should have a de-referencable
+    <tref>Linked Data</tref>, and nodes should have a de-referenceable
     identifier used to name and locate them. For nodes to be truly linked,
     de-referencing the identifier should result in a representation of that node.
     Associating an IRI with a node tells an application that the returned
@@ -1338,7 +1338,7 @@
 </pre>
 
 <p>The <em>modified</em> key's value above is automatically type coerced to a
-datetime value because of the information specified in the
+dateTime value because of the information specified in the
 <code>@context</code>.</p>
 
 <p>The second example uses the expanded form of setting the type information
@@ -1466,7 +1466,7 @@
 </pre>
 
 <p>The markup shown above would generate the following data. The data has no inherent order
-  except for the values the <code>http://xmlns.com/foaf/0.1/homepage</code> property
+  except for the values of the <code>http://xmlns.com/foaf/0.1/homepage</code> property
   which represent an ordered list.</p>
 
 <table class="example">
@@ -2360,7 +2360,7 @@
 
 <section>
 <h3>Expanded Document Form</h3>
-<p>The JSON-LD API [[JSON-LD-API]] defines an method for <em>expanding</em> a
+<p>The JSON-LD API [[JSON-LD-API]] defines a method for <em>expanding</em> a
   JSON-LD document.
   Expansion is the process of taking a JSON-LD document and applying a
   <code>@context</code> such that all IRIs, types, and values