--- a/spec/latest/json-ld-api/index.html	Wed Mar 27 13:19:41 2013 +0100
+++ b/spec/latest/json-ld-api/index.html	Wed Mar 27 13:24:07 2013 +0100
@@ -3470,7 +3470,7 @@
 
     <p>When <a href="#rdf-conversion">converting JSON-LD to RDF</a> JSON-native types such as
       <em>numbers</em> and <em>booleans</em> are automatically coerced to
-      <strong>xsd:integer</strong>, <strong>xsd:double</strong>, or <strong>xsd:boolean</strong>.
+      <code>xsd:integer</code>, <code>xsd:double</code>, or <code>xsd:boolean</code>.
       Implementers MUST ensure that the result is in <tref>canonical lexical form</tref>. A
       <tdef>canonical lexical form</tdef> is a set of literals from among the valid set of literals for
       a datatype such that there is a one-to-one mapping between the <tref>canonical lexical form</tref>
@@ -3478,7 +3478,7 @@
       value MUST be converted to a deterministic <tref>string</tref> representation.</p>
 
     <p>The canonical lexical form of an <em>integer</em>, i.e., a number without fractions
-      or a number coerced to <strong>xsd:integer</strong>, is a finite-length sequence of decimal
+      or a number coerced to <code>xsd:integer</code>, is a finite-length sequence of decimal
       digits (<code>0-9</code>) with an optional leading minus sign; leading zeros are prohibited.
       To convert the number in JavaScript, implementers can use the following snippet of code:</p>
 
@@ -3490,7 +3490,7 @@
     </pre>
 
     <p>The canonical lexical form of a <em>double</em>, i.e., a number with fractions
-      or a number coerced to <strong>xsd:double</strong>, consists of a mantissa followed by the
+      or a number coerced to <code>xsd:double</code>, consists of a mantissa followed by the
       character "E", followed by an exponent. The mantissa MUST be a decimal number. The exponent
       MUST be an integer. Leading zeros and a preceding plus sign (<code>+</code>) are prohibited
       in the exponent. If the exponent is zero, it must be indicated by <code>E0</code>.
@@ -3499,7 +3499,7 @@
       representations must be normalized such that there is a single digit which is non-zero to the
       left of the decimal point and at least a single digit to the right of the decimal point unless
       the value being represented is zero. The canonical representation for zero is <code>0.0E0</code>.
-      <strong>xsd:double</strong>'s value space is defined by the IEEE double-precision 64-bit
+      <code>xsd:double</code>'s value space is defined by the IEEE double-precision 64-bit
       floating point type [[!IEEE-754-1985]]; in JSON-LD the mantissa is rounded to 15 digits after the
       decimal point.</p>
 
@@ -3514,15 +3514,15 @@
 
     <p class="note">When data such as decimals need to be normalized, JSON-LD authors should
       not use values that are going to undergo automatic conversion. This is due to the lossy nature
-      of <strong>xsd:double</strong> values. Authors should instead use the expanded object form to
+      of <code>xsd:double</code> values. Authors should instead use the expanded object form to
       set the canonical lexical form directly.</p>
 
-    <p>The canonical lexical form of the <em>boolean</em> values <code>true</code> and <code>false</code>
-      are the strings <strong>true</strong> and <strong>false</strong>.</p>
+    <p>The canonical lexical form of the <em>boolean</em> values <tref>true</tref> and <tref>false</tref>
+      are the strings <code>true</code> and <code>false</code>.</p>
 
     <p>When JSON-native <tref>number</tref>s, are type coerced, lossless data round-tripping can not
       be guaranteed as rounding errors might occur. Additionally, only literals typed as
-      <strong>xsd:integer</strong>, <strong>xsd:double</strong>, and  <strong>xsd:boolean</strong> are
+      <code>xsd:integer</code>, <code>xsd:double</code>, and  <code>xsd:boolean</code> are
       automatically converted back to their JSON-native counterparts in when
       <a href="#rdf-conversion">converting from RDF</a>.</p>