--- a/spec/latest/json-ld-syntax/index.html	Wed Nov 21 17:25:04 2012 +0100
+++ b/spec/latest/json-ld-syntax/index.html	Wed Nov 21 18:00:40 2012 +0100
@@ -1698,35 +1698,37 @@
   For example:</p>
 
 <pre class="example" data-transform="updateExample"
-     title="Term definition with absolute IRI">
+     title="Term definitions using compact and absolute IRIs">
 <!--
 {
   "@context":
   {
-    ****"foaf": "http://xmlns.com/foaf/0.1/"****,
+    "foaf": "http://xmlns.com/foaf/0.1/",
     "****foaf:age****":
     {
+      ****"@id": "http://xmlns.com/foaf/0.1/age"****,
       "@type": "xsd:integer"
     },
-    "****foaf:homepage****":
-    ****{
+    "****http://xmlns.com/foaf/0.1/homepage****":
+    {
       "@type": "@id"
-    }****
+    }
   },
   "foaf:name": "John Smith",
-  "foaf:age": ****"41"****,
-  "foaf:homepage":
-  ****[
+  "****foaf:age****": "41",
+  "****http://xmlns.com/foaf/0.1/homepage****":
+  [
     "http://personal.example.org/",
     "http://work.example.com/jsmith/"
-  ]****
+  ]
 }
 -->
 </pre>
 
-<p>In this case the <code>@id</code> definition is optional, but if it does exist, the <tref>compact IRI</tref>
+<p>In this case the <code>@id</code> definition in the term definition is optional, but if it does exist, the <tref>compact IRI</tref>
   or <tref>IRI</tref> is treated as a <tref>term</tref> (not a <code>prefix:suffix</code> construct)
-  so that the actual definition of a <tref>prefix</tref> becomes unnecessary.</p>
+  so that the actual definition of a <tref>prefix</tref> becomes unnecessary. Type coercion is performed using
+  the unexpanded value of the key, which has to match exactly an entry in the <tref>active context</tref>.</p>
 
 <p class="note">Keys in the context are treated as <tref title="term">terms</tref> for the purpose of
   expansion and value coercion. At times, this may result in multiple representations for the same expanded IRI.
@@ -1737,8 +1739,6 @@
   <code>http://example.org/river</code>, but this usage is discouraged because it would lead to a
   great deal of confusion among developers attempting to understand the JSON-LD document.</p>
 
-<p>Type coercion is performed using the unexpanded value of the key, which has to match exactly
-  an entry in the <tref>active context</tref>.</p>
 
 </section>