--- a/spec/latest/json-ld-api/index.html	Sun Jun 10 22:32:24 2012 -0400
+++ b/spec/latest/json-ld-api/index.html	Sun Jun 10 22:34:11 2012 -0400
@@ -1186,7 +1186,7 @@
     of an array) using a <tdef>term mapping</tdef>. It is also used to maintain
     <tdef>coercion mapping</tdef>s from terms to datatypes, <tdef>language mapping</tdef>s from terms to language codes,
     and <tdef>list mapping</tdef>s and <tdef>set mapping</tdef>s for terms. Processors MUST use the
-    lexical form of the property when creating a mapping, as lookup is performed on lexical representations, not
+    lexical form of the property when creating a mapping, as lookup is performed on lexical forms, not
     expanded IRI representations.</p>
   <p>A <tref>local context</tref> is identified within a <tref>JSON object</tref> having a <code>@context</code>
     property with a <tref>string</tref>, <tref>array</tref> or a <tref>JSON object</tref> value.
@@ -1806,7 +1806,7 @@
     <tref title="IRI">IRIs</tref> for describing
     externally named entities, <tref>blank node</tref>, resources for which an external name does not
     exist, or is not known, and <tref>Literal</tref>, which describe terminal entities such as strings,
-    dates and other representations having a lexical representation possibly including
+    dates and other representations having a lexical form possibly including
     an explicit language or datatype.
   </p>
   <p>Data described with JSON-LD may be considered to be the representation of a graph made
@@ -2086,13 +2086,13 @@
 
 <p>When coercing numbers to <strong>xsd:integer</strong> or <strong>xsd:double</strong>
   as it, e.g., happens during <a href="#rdf-conversion">RDF Conversion</a>, implementers MUST
-  ensure that the result is a canonical lexical representation in the form of a
-  <tref>string</tref>. A <tdef>canonical lexical representation</tdef> is a set of literals
+  ensure that the result is a canonical lexical form in the form of a
+  <tref>string</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 canonical lexical representation and a value in the value space as defined in
+  between the canonical lexical form and a value in the value space as defined in
   [[!XMLSCHEMA11-2]]]. In other words, every value MUST be converted to a deterministic string
   representation.</p>
-<p>The canonical lexical representation of an <em>integer</em>, i.e., a number without fractions
+<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
   digits (<code>0-9</code>) with an optional leading minus sign; leading zeroes are prohibited.
   To convert the number in JavaScript, implementers can use the following snippet of code:</p>
@@ -2101,7 +2101,7 @@
 (value).toFixed(0).toString()
 -->
 </pre>
-<p>The canonical lexical representation of a <em>double</em>, i.e., a number with fractions
+<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
   character "E", followed by an exponent. The mantissa MUST be a decimal number. The exponent
   MUST be an integer. Leading zeroes and a preceding plus sign (<code>+</code>) are prohibited
@@ -2123,7 +2123,7 @@
 <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
-set the canonical lexical representation directly.</p>
+set the canonical lexical form directly.</p>
 
 <p class="note">When JSON-native datatypes, like <tref>number</tref>s, are type coerced, lossless
 data round-tripping can not be guaranted. Consider the following code example:</p>