--- a/requirements/latest/index.html	Tue Aug 09 09:19:33 2011 -0700
+++ b/requirements/latest/index.html	Tue Aug 09 12:41:10 2011 -0700
@@ -290,7 +290,7 @@
     </p>
     <ol>
       <li><tdef>Linked Data</tdef> is a set of documents, each containing a representation of a linked data graph.</li>
-      <li>A <tdef>linked data graph</tdef> is a labeled directed graph, where nodes are <tref>subject</tref>s or <tref>object</tref>s, and edges are properties.</li>
+      <li>A <tdef>linked data graph</tdef> is an unordered labeled directed graph, where nodes are <tref>subject</tref>s or <tref>object</tref>s, and edges are properties.</li>
       <li>A <tdef>subject</tdef> is any node in a <tref>linked data graph</tref> with at least one outgoing edge.</li>
       <li>A <tref>subject</tref> SHOULD be labeled with an IRI.</li>
       <li>A <tdef>property</tdef> is an edge of the <tref>linked data graph</tref>.</li>
@@ -319,30 +319,22 @@
       <li>A JSON-LD document MUST be able to express a <tref>linked data graph</tref>.</li>
       <li>A JSON-LD document MUST be a valid JSON document.</li>
       <li>
-        All JSON constructs MUST have semantic meaning in a JSON-LD document: associative arrays, arrays, numbers,
-        strings and other literal names to express semantic information.
+        All JSON constructs MUST have semantic meaning in a
+        JSON-LD document: <tref>JSON object</tref>s, arrays, numbers, strings and the literal
+        names false, and true.
       </li>
       <li>A <tref>subject</tref> is defined using a designated name/value pair of a <tref>JSON object</tref>.</li>
       <li>There MUST be a way label a <tref>JSON object</tref> with an IRI.</li>
       <li>There MAY be a way to reference an un-labeled JSON object that does not have a direct child relationship.</li>
-      <li>JSON name/value SHOULD be used to describe <tref>property</tref>-<tref>object</tref> relationships.</li>
+      <li><tref>JSON object</tref> name/value SHOULD be used to describe <tref>property</tref>-<tref>object</tref> relationships.</li>
       <li>A <tref>property</tref> SHOULD resolve to an absolute IRI.</li>
-      <li>
-        An <tref>object</tref> is represented using
-        <trefs>JSON object</trefs>s, arrays, numbers, strings and literal names resolve to nodes in
-        a <tref>linked data graph</tref>.
-      </li>
-      <li>Un-coerced JSON strings represent literal <tref>object</tref>s.</li>
-      <li>Coerced JSON strings MAY represent IRIs.</li>
+      <li>Un-coerced strings represent literal <tref>object</tref>s.</li>
+      <li>Coerced strings MAY represent IRIs.</li>
       <li>There SHOULD be a way to associate a datatype IRI with a literal JSON value.</li>
-      <li>JSON booleans, numbers and other literal values MUST represent specific datatyped literals.
-        <span class="issue">
-          What does null map to? There may be value in specifically saying that
-          the meaning is undefined.
-        </span>
-      </li>
+      <li>JSON boolean and numbers values represent specific datatyped literals.</li>
+      <li>The literal value of JSON null is undefined.</li>
       <li>A JSON array MAY be used to associate multiple <tref>object</tref>s with a <tref>subject</tref> through a common <tref>property</tref>.</li>
-      <li>A JSON array MUST NOT be used to imply an order to the component entities.</li>
+      <li>Without explicit syntactic support, JSON arrays MUST NOT be interpreted as defining an object ordering.</li>
       <li>A JSON-LD document SHOULD be able to express and ordered list objects.</li>
     </ol>
   </section>