--- a/spec/latest/json-ld-syntax/index.html Fri Jun 22 22:55:53 2012 -0400
+++ b/spec/latest/json-ld-syntax/index.html Fri Jun 22 23:05:38 2012 -0400
@@ -807,8 +807,9 @@
<p>A <tref>JSON object</tref> used to define property values is called a
<tref>subject definition</tref>. <tref title="subject definition">Subject definitions</tref>
- do not require a <code>@id</code>, in which case they are considered to be an
- <tref>unlabeled node</tref>.</p>
+ do not require an <code>@id</code>.
+ <tref title="subject definition">Subject definitions</tref> that do not
+ contain an <code>@id</code> are known as an <tref>unlabeled node</tref>.</p>
</section>
</section>
@@ -816,7 +817,7 @@
<section>
<h2>IRIs</h2>
-<p>Expressing <tref>IRI</tref>s are fundamental to <tref>Linked Data</tref>
+<p><tref>IRI</tref>s are fundamental to <tref>Linked Data</tref>
as that is how most <tref>subject</tref>s, all
<tref title="property">properties</tref> and many <tref>object</tref>s are
identified. <tref>IRI</tref>s can be expressed in a variety of different ways
@@ -836,7 +837,7 @@
<p>An <tdef>absolute IRI</tdef> is defined in [[!RFC3987]] containing a <em>scheme</em> along with
<em>path</em> and optional <em>query</em> and <em>fragment</em> segments. A <tdef>relative IRI</tdef> is an IRI
- that is relative some other <tref>absolute IRI</tref>. In JSON-LD all <tref>relative IRI</tref>s are resolved relative to the
+ that is relative to some other <tref>absolute IRI</tref>. In JSON-LD all <tref>relative IRI</tref>s are resolved relative to the
<tdef>base IRI</tdef> associated with the document (typically, the directory that contains the document or the document itself).</p>
<p>IRIs can be expressed directly in the key position like so:</p>
@@ -2311,8 +2312,8 @@
<ol>
<li>A JSON-LD document is composed of a single <tref>JSON object</tref> or an <tref>array</tref> of <tref title="JSON object">JSON objects</tref>.</li>
<li>The value of <code>@id</code> MUST be <code>null</code>, a <tref>term</tref>, a <tref>compact IRI</tref>, or an <tref>IRI</tref>.</li>
-<li>A <code>@id</code> keyword and a <code>@language</code> keyword MUST NOT exist in the same <tref>JSON object</tref>.</li>
-<li>A <code>@id</code> keyword and a <code>@container</code> keyword MUST NOT exist in the same <tref>JSON object</tref>.</li>
+<li>An <code>@id</code> keyword and a <code>@language</code> keyword MUST NOT exist in the same <tref>JSON object</tref>.</li>
+<li>An <code>@id</code> keyword and a <code>@container</code> keyword MUST NOT exist in the same <tref>JSON object</tref>.</li>
<li>A <tref>JSON object</tref> MAY contain a <code>@context</code> property.</li>
<li>A <code>@context</code> value MUST NOT contain an embedded <code>@context</code> definition.</li>
<li>The value associated with the <code>@context</code> keyword MUST be an <tref>IRI</tref>, a <tref>JSON object</tref>, null, or an <tref>array</tref> containing a combination of the allowed values.</li>