--- a/spec/latest/json-ld-syntax/index.html	Mon Jan 21 18:44:49 2013 +0100
+++ b/spec/latest/json-ld-syntax/index.html	Mon Jan 21 18:58:44 2013 +0100
@@ -498,12 +498,12 @@
     -->
     </pre>
 
-    <p>As <tref>context</tref> above shows, the value of a <tdef>term definition</tdef> can
-      either be 1)&nbsp;a simple string mapping the <tref>term</tref> to an <tref>IRI</tref>,
-      or 2)&nbsp;an <tref>expanded term definition</tref> in the form of a <tref>JSON object</tref>
-      to allow additional information to be associated with the term.</p>
-
-    <p><tref title="expanded term definition">Expanded term definitions</tref> may
+    <p>As the <tref>context</tref> above shows, the value of a <tdef>term definition</tdef> can
+      either be a simple string, mapping the <tref>term</tref> to an <tref>IRI</tref>,
+      or a <tref>JSON object</tref> which allows additional information to be associated
+      with the term (making it an <tref>expanded term definition</tref>).</p>
+
+    <p><tdef title="expanded term definition">Expanded term definitions</tdef> may
       be used to associate <a href="#type-coercion">type</a> or
       <a href="#string-internationalization">language information</a> (as in the
       example above which specifies that the  values of <code>image</code> and
@@ -1420,7 +1420,7 @@
 <tref title="term">terms</tref>. Using type coercion, value representation is preserved without requiring
 the data type to be specified with each piece of data.</p>
 
-<p>Type coercion is specified within an <a href="#expanded-term-definition"></a>
+<p>Type coercion is specified within an <tref>expanded term definition</tref>
   using the <code>@type</code> key. The value of this key expands to an <tref>IRI</tref>.
   Alternatively, the <tref>keyword</tref> <code>@id</code> may be used as value to indicate
   that within the body of a JSON-LD document, a string value of a <tref>term</tref> coerced to
@@ -2836,7 +2836,7 @@
 <p><tref>Term</tref> values MUST be either a
   <tref>string</tref>, <tref>null</tref>, or an <tref>expanded term definition</tref>.</p>
 
-<p>An <tdef>expanded term definition</tdef> is used to describe the mapping
+<p>An <tref>expanded term definition</tref> is used to describe the mapping
   between a <tref>term</tref> and its expanded identifier, as well as other
   properties of the value associated with the <tref>term</tref> when it is
   used as key in a <tref>node object</tref>.</p>
@@ -2869,8 +2869,7 @@
 
 <p><tref title="term">Terms</tref> MUST NOT be used in a circular manner. That is, the definition of a term cannot depend on the definition of another term if that other term also depends on the first term.</p>
 
-<p>See <a href="#the-context"></a> and <a href="#expanded-term-definition"></a>
-  for further discussion on contexts.</p>
+<p>See <a href="#the-context"></a> for further discussion on contexts.</p>
 </section>
 
 </section>