--- a/spec/latest/json-ld-syntax/index.html	Sun Nov 06 18:54:07 2011 -0800
+++ b/spec/latest/json-ld-syntax/index.html	Mon Nov 07 11:50:52 2011 +0800
@@ -501,7 +501,7 @@
  it is not always possible without adding great complexity to the language.
  </dd>
  <dt>One-pass Processing</dt>
- <dd>JSON-LD supports one-pass processing, which results in a very small memory 
+ <dd>JSON-LD supports one-pass processing, which results in a very small memory
  footprint when processing documents. For example, to convert a JSON-LD document
  into an RDF document of any kind, only one pass is required over the data.</dd>
 </dl>
@@ -604,8 +604,8 @@
 -->
 </pre>
 
-<p>This context document can then be used in an JSON-LD document by adding a 
-single line. The JSON markup as shown in the previous section could be changed 
+<p>This context document can then be used in an JSON-LD document by adding a
+single line. The JSON markup as shown in the previous section could be changed
 as follows to link to the context document:</p>
 
 <pre class="example" data-transform="updateExample">
@@ -727,8 +727,8 @@
 <section>
   <h2>External Contexts</h2>
 
-  <p>Authors may choose to declare JSON-LD <tref>context</tref>s in external 
-documents to promote re-use of contexts as well as reduce the size of JSON-LD 
+  <p>Authors may choose to declare JSON-LD <tref>context</tref>s in external
+documents to promote re-use of contexts as well as reduce the size of JSON-LD
 documents.
 In order to use an external context, an author MAY specify an <tref>IRI</tref> to a valid
 JSON-LD document. The referenced document MUST have a top-level <tref>JSON Object</tref>.
@@ -748,7 +748,7 @@
 -->
 </pre>
 
-<p>Authors may also import multiple contexts or a combination of external and local contexts by specifying a list of 
+<p>Authors may also import multiple contexts or a combination of external and local contexts by specifying a list of
 contexts:</p>
 
 <pre class="example" data-transform="updateExample">
@@ -776,7 +776,7 @@
 <p>External JSON-LD context documents MAY contain extra information located
 outside of the <code>@context</code> key, such as
 documentation about the <tref>prefix</tref>es declared in the document. It is
-also RECOMMENDED that a human-readable document encoded in HTML+RDFa 
+also RECOMMENDED that a human-readable document encoded in HTML+RDFa
 [[HTML-RDFA]] or other Linked Data compatible format is served as well to
 explain the correct usage of the JSON-LD context document.
 </p>
@@ -1259,7 +1259,7 @@
     This results in three triples being generated, each relating the subject to an individual
     object, with no inherent order.</p>
   <p>
-    As the notion of ordered collections is rather important in data modeling, it is useful to 
+    As the notion of ordered collections is rather important in data modeling, it is useful to
     have specific language support. In JSON-LD, a list may be represented using the
     <code>@list</code> keyword as follows:
   </p>
@@ -1312,7 +1312,7 @@
 
 
 <section>
-<h3>Base URI</h3>
+<h3>Base IRI</h3>
 <p>JSON-LD allows <tref>IRI</tref>s to be specified in a relative form. For <tref>subject</tref> and <tref>object</tref>
   IRIs, relative IRIs are resolved against the document base using
   <cite><a href="http://www.ietf.org/rfc/rfc2396.txt">section 5.1 Establishing a
@@ -1320,7 +1320,7 @@
   set with a <tref>context</tref> using the <code>@base</code> keyword.</p>
 
 <p>For example, if a JSON-LD document was retrieved from <code>http://manu.sporny.org/</code>,
-  relative IRIs would resolve against that URI:</p>
+  relative IRIs would resolve against that IRI:</p>
 
 <pre class="example" data-transform="updateExample">
 <!--
@@ -1353,7 +1353,7 @@
 <section>
 <h3>Default Vocabulary</h3>
 <p>It is often common that all types and properties come from the same vocabulary. JSON-LD provides
-  a way to set a base URI to be used for all properties and types that aren't based on terms,
+  a way to set a base IRI to be used for all properties and types that aren't based on terms,
   prefixes or absolute IRIs. Much like the <code>@base</code> keyword, the <code>@vocab</code> keyword
   can be used to set a base <tref>IRI</tref> to use for all types and properties that don't otherwise resolve to
   an absolute <tref>IRI</tref>.
@@ -1757,9 +1757,9 @@
 
 <section>
   <h3>Turtle</h3>
-  
+
   <p>The following are examples of representing <tref>RDF</tref> as expressed in [[TURTLE]] into JSON-LD.</p>
-  
+
 <section>
 <h4>Prefix and Base definitions</h4>
 <p>The JSON-LD context has direct equivalents for Turtle <code>@base</code> and <code>@prefix</code> expressions:</p>