--- a/spec/latest/json-ld-syntax/index.html	Thu Dec 27 14:11:52 2012 +0100
+++ b/spec/latest/json-ld-syntax/index.html	Thu Dec 27 14:22:24 2012 +0100
@@ -2498,40 +2498,38 @@
 </section>
 
 <section>
-<h2>Explicitly Ignoring Data</h2>
-
-<p>At times, it becomes necessary to explicitly ignore data expressed in JSON
-documents because it has no semantic meaning. For example, when the
-<code>@vocab</code> keyword is used, every key in a JSON-LD object is
-appended to the vocabulary <tref>IRI</tref>. The author may not want that
-behavior to apply to every key, and it may be easier to specify just the keys
-that they want the JSON-LD processor to ignore. For this purpose, an author
-may associate the <tref>null</tref> keyword with a <tref>term</tref> in the
-JSON-LD Context.</p>
-
-<pre class="example" data-transform="updateExample"
-     title="Using the null keyword to ignore data">
-<!--
-{
-  "@context":
+  <h2>Explicitly Ignoring Data</h2>
+
+  <p>At times, it becomes necessary to explicitly ignore data expressed in JSON
+    documents because it has no semantic meaning. For example, when the
+    <code>@vocab</code> keyword is used, every key in a JSON-LD object is
+    appended to the vocabulary <tref>IRI</tref>. The author may not want that
+    behavior to apply to every key, and it may be easier to specify just the keys
+    that they want the JSON-LD processor to ignore. For this purpose, an author
+    may associate the <tref>null</tref> keyword with a <tref>term</tref> in the
+    JSON-LD Context.</p>
+
+  <pre class="example" data-transform="updateExample"
+       title="Using the null keyword to ignore data">
+  <!--
   {
-     "@vocab": "http://schema.org/",
-     ****"databaseId": null****
-  },
-  "name": "Manu Sporny",
-  "description": "That guy",
-  "gender": "Male",
-  ****"databaseId": "23987520"****
-}
--->
-</pre>
-
-<p>In the example above, the author has used <code>@vocab</code> as the base
-IRI for all terms in the document, but has expressed that the
-<code>databaseId</code> value should not be processed by the JSON-LD processor
-by associating it with the <tref>null</tref> keyword in the JSON-LD Context.
-</p>
-
+    "@context":
+    {
+       "@vocab": "http://schema.org/",
+       ****"databaseId": null****
+    },
+    "name": "Manu Sporny",
+    "description": "That guy",
+    "gender": "Male",
+    ****"databaseId": "23987520"****
+  }
+  -->
+  </pre>
+
+  <p>In the example above, the author has used <code>@vocab</code> to expand all
+    properties to <tref title="IRI">IRIs</tref> but has expressed that the
+    <code>databaseId</code> value should not be processed by the JSON-LD processor
+    by associating it with the <tref>null</tref> keyword in the JSON-LD Context.</p>
 </section>
 
 <section>