--- a/spec/latest/json-ld-syntax/index.html	Tue Apr 24 11:47:10 2012 -0700
+++ b/spec/latest/json-ld-syntax/index.html	Tue Apr 24 12:17:00 2012 -0700
@@ -1946,11 +1946,9 @@
 
 <section>
   <h2>Named Graphs</h2>
-  <p class="issue">This section is provisional, as the group has not yet decided to include
-    support for named graphs. However, the use of the <code>@graph</code> keyword does have
-    meaning for a top-level object definition.</p>
-  <p>The <code>@graph</code> is used to identify a set of JSON-LD object definitions that may not be directly
-    related through a property, or where <tref>embedding</tref> is not appropriate. For example:</p>
+  <p>The <code>@graph</code> keyword is used to identify a set of JSON-LD object
+    definitions that may not be directly related through a property, or where 
+    <tref>embedding</tref> is not appropriate. For example:</p>
 
   <pre class="example" data-transform="updateExample">
   <!--
@@ -2002,12 +2000,15 @@
   -->
   </pre>
 
-  <p>The <code>@graph</code> keyword takes on additional meaning when it is used along with
-    other properties, or is used within an embedded JSON-LD object. In this case, the set
-    of JSON-LD objects contained within a <code>@graph</code> is given a <em>name</em>, based
-    on the label of the JSON-LD object containing a <code>@graph</code> property, either an
-    <tref>IRI</tref>, or an <tref>unlabeled node</tref>. This allows statements to be
-    made about an entire <tref>linked data graph</tref>, rather than just a single JSON-LD object.</p>
+  <p>The <code>@graph</code> keyword takes on additional meaning when it
+    is used along with other properties, or is used within an embedded JSON-LD 
+    object. In this case, the set of <tref title="subject definition">subject definitions</tref>,
+    or <tref title="subject reference">subject references</tref> 
+    contained within a <code>@graph</code> is given a <em>name</em>, based on 
+    the label of the JSON-LD object containing a <code>@graph</code> property, 
+    either an <tref>IRI</tref>, or an <tref>unlabeled node</tref>. This allows 
+    statements to be made about an entire <tref>linked data graph</tref>, 
+    rather than just a single JSON-LD object.</p>
 
   <pre class="example" data-transform="updateExample">
   <!--
@@ -2028,16 +2029,20 @@
         "@type": "foaf:Person",
         "name": "Gregg Kellogg",
         "knows" "http://manu.sporny.org/i/public"
-      }
+      },
+      "http://www.markus-lanthaler.com/"
     ]
   }
   -->
   </pre>
 
   <p>This example says that there is a <tref>linked data graph</tref> identified by
-    <code>http://example.org/linked-data-graph</code> which is composed of the statements
-    about Manu and Gregg. Additionally, there is information about the graph itself, which
-    indicates a time at which this information as asserted to be true.</p>
+    <code>http://example.org/linked-data-graph</code> which is composed of the 
+    statements about Manu and Gregg and a reference to another IRI, which could 
+    make statements about Markus. Additionally, there is information about the 
+    graph itself, which indicates a time at which this information as asserted 
+    to be true.</p>
+
 </section>
 
 <section>