--- a/spec/latest/json-ld-syntax/index.html	Mon Jan 21 20:04:20 2013 +0100
+++ b/spec/latest/json-ld-syntax/index.html	Mon Jan 21 20:41:17 2013 -0500
@@ -362,7 +362,7 @@
       This keyword is described in <a href="#named-graphs"></a>.</dd>
     <dt><code>:</code></dt>
     <dd>The separator for JSON keys and values that use
-      <tref title="compact IRI">compact IRIs</tref>.</dd>
+      <tref title="compact_iri">compact IRIs</tref>.</dd>
     </dl>
 
     <p>For the avoidance of doubt, all keys, <tref title="keyword">keywords</tref>,
@@ -512,10 +512,10 @@
       and to specify whether <tref title="array">array</tref> values are to be
       interpreted as <a href="#sets-and-lists">sets or lists</a>.
       <tref title="expanded term definition">Expanded term definitions</tref> may
-      be defined using <tref title="absolute IRI">absolute</tref> or
-      <tref title="compact IRI">compact IRIs</tref> as keys. This mechanism is
+      be defined using <tref title="absolute_iri">absolute</tref> or
+      <tref title="compact_iri">compact IRIs</tref> as keys. This mechanism is
       mainly used to associate type or language information with an
-      <tref title="absolute IRI">absolute</tref> or <tref>compact IRI</tref>.</p>
+      <tref title="absolute_iri">absolute</tref> or <tref>compact IRI</tref>.</p>
 
     <p class="note">While it is possible to define a <tref>compact IRI</tref>, or
       an <tref>absolute IRI</tref> to expand to some other unrelated <tref>IRI</tref>
@@ -754,7 +754,7 @@
     relative to the <tdef>base IRI</tdef> associated with the document, which
     is typically the directory path containing the document.</p>
 
-  <p><tref title="absolute IRI">IRIs</tref> can be expressed directly in the key
+  <p><tref title="absolute_iri">IRIs</tref> can be expressed directly in the key
     position like so:</p>
 
   <pre class="example" data-transform="updateExample"
@@ -1229,7 +1229,7 @@
     <code>http://xmlns.com/foaf/0.1/name</code>. Instead of having to remember and
     type out the entire IRI, the developer can instead use the prefix in their JSON-LD markup.
   </p>
-  <p>Terms are interpreted as <tref title="compact IRI">compact IRIs</tref> if they contain at least one
+  <p>Terms are interpreted as <tref title="compact_iri">compact IRIs</tref> if they contain at least one
     colon and the first colon is not followed by two slashes (<code>//</code>, as in
     <code>http://example.com</code>). To generate the full <tref>IRI</tref>,
     the value is first split into a <em>prefix</em> and <em>suffix</em> at the first
@@ -1425,7 +1425,7 @@
   that within the body of a JSON-LD document, a string value of a <tref>term</tref> coerced to
   <code>@id</code> is to be interpreted as an <tref>IRI</tref>.</p>
 
-<p><tref title="term">Terms</tref> or <tref title="compact IRI">compact IRIs</tref> used as the value of a
+<p><tref title="term">Terms</tref> or <tref title="compact_iri">compact IRIs</tref> used as the value of a
   <code>@type</code> key may be defined within the same context. This means that one may specify a
   <tref>term</tref> like <code>xsd</code> and then use <code>xsd:integer</code> within the same
   context definition.</p>
@@ -1502,7 +1502,7 @@
 </tbody>
 </table>
 
-<p>Terms may also be defined using <tref title="absolute iri">absolute IRIs</tref> or <tref title="compact IRI">compact IRIs</tref>.
+<p>Terms may also be defined using <tref title="absolute_iri">absolute IRIs</tref> or <tref title="compact_iri">compact IRIs</tref>.
   This allows coercion rules to be applied to keys which are not represented as a simple <tref>term</tref>.
   For example:</p>
 
@@ -1693,7 +1693,7 @@
 -->
 </pre>
 
-<p><tref title="compact IRI">Compact IRIs</tref>
+<p><tref title="compact_iri">Compact IRIs</tref>
   and <tref title="IRI">IRIs</tref> may be used on the left-hand side of a
   <tref>term</tref> definition.</p>
 
@@ -1734,7 +1734,7 @@
 </p>
 
 <p>
-<tref title="absolute IRI">Absolute IRIs</tref> may also be used in the key position in a <tref>context</tref>:
+<tref title="absolute_iri">Absolute IRIs</tref> may also be used in the key position in a <tref>context</tref>:
 </p>
 
 <pre class="example" data-transform="updateExample"
@@ -2606,7 +2606,7 @@
 
 <p>A <tref>node object</tref> MUST be a <tref>JSON object</tref>. All keys
   which are not <tref title="IRI">IRIs</tref>,
-  <tref title="compact IRI">compact IRIs</tref>, <tref title="term">terms</tref>
+  <tref title="compact_iri">compact IRIs</tref>, <tref title="term">terms</tref>
   valid in the <tref>active context</tref>, or one of the following
   <tref title="keyword">keywords</tref> MUST be ignored when processed:</p>