--- a/spec/PR/json-ld/20131105/diff-20130910.html	Wed Oct 30 15:25:09 2013 +0100
+++ b/spec/PR/json-ld/20131105/diff-20130910.html	Thu Oct 31 15:17:25 2013 +0100
@@ -817,20 +817,22 @@
 Changes
 since
 the
-<a href="http://www.w3.org/TR/2013/WD-json-ld-20130411/">
 <del class="diff-old">11&nbsp;April&nbsp;2013
-</del>
-<ins class="diff-chg">11&#160;April&#160;2013
-</ins>
 Last
 Call
 Working
 Draft
+</del>
+<a href="http://www.w3.org/TR/2013/CR-json-ld-20130910/">
+<ins class="diff-chg">10&#160;September&#160;2013
+Candidate
+Recommendation
+</ins>
 </a>:
 </p>
 <ul>
 <li>
-Allow
+<del class="diff-old">Allow
 keyword
 aliases
 to
@@ -840,8 +842,6 @@
 expanded
 term
 definitions
-</li>
-<li>
 Mention
 profile
 URIs
@@ -854,23 +854,16 @@
 various
 document
 forms
-</li>
-<li>
 Support
 relative
 IRIs
 in
-<code>
 @base
-</code>
-</li>
-<li>
+</del>
 Clarify
-how
-the
-<code>
+<del class="diff-old">how
+the
 profile
-</code>
 media
 type
 parameter
@@ -881,8 +874,6 @@
 content
 negotiation
 process
-</li>
-<li>
 Update
 grammar
 to
@@ -892,8 +883,6 @@
 as
 data
 types
-</li>
-<li>
 Update
 grammar
 to
@@ -904,11 +893,7 @@
 as
 value
 of
-<code>
 @vocab
-</code>
-</li>
-<li>
 Align
 the
 JSON-LD
@@ -919,31 +904,31 @@
 RDF
 Data
 Model
-</li>
-<li>
 Support
 processing
-of
-documents
-with
-a
-<code>
-+json
-</code>
-media
+</del>
+<ins class="diff-chg">context-sensitivity
+</ins>
+of
+<del class="diff-old">documents
+with
+a
+</del>
+<code>
+<del class="diff-old">+json
+</del>
+<ins class="diff-chg">@type
+</ins>
+</code>
+<del class="diff-old">media
 type
 as
 defined
 in
 [
-<cite>
-<a href="#bib-RFC6839" class="bibref">
-RFC6839
-</a>
-</cite>
+</del>
+<del class="diff-old">RFC6839
 ]
-</li>
-<li>
 Added
 a
 brief
@@ -955,8 +940,6 @@
 to
 the
 introduction.
-</li>
-<li>
 Fixed
 a
 number
@@ -977,24 +960,8 @@
 the
 last
 several
-<del class="diff-old">moths.
-</del>
-<ins class="diff-chg">months
-</ins></li></ul><p><ins class="diff-chg">
-Changes
-since
-the
-</ins><a href="http://www.w3.org/TR/2013/CR-json-ld-20130910/"><ins class="diff-chg">
-10&#160;September&#160;2013
-Candidate
-Recommendation
-</ins></a>:</p><ul><li><ins class="diff-chg">
-Clarify
-context-sensitivity
-of
-</ins><code><ins class="diff-chg">
-@type
-</ins></code>
+moths.
+</del>
 </li>
 </ul>
 <p>
@@ -8261,10 +8228,12 @@
 </p>
 </div>
 <p>
-Generally
+<del class="diff-old">Generally
 speaking,
 a
-<dfn id="dfn-node-type" title="node-type">
+</del>
+<ins class="diff-chg">A
+</ins><dfn id="dfn-node-type" title="node-type">
 node
 type
 </dfn>

--- a/spec/PR/json-ld/20131105/index.html	Wed Oct 30 15:25:09 2013 +0100
+++ b/spec/PR/json-ld/20131105/index.html	Thu Oct 31 15:17:25 2013 +0100
@@ -306,25 +306,6 @@
     next two months.</p>
 
   <p>Changes since the
-    <a href="http://www.w3.org/TR/2013/WD-json-ld-20130411/">11&nbsp;April&nbsp;2013 Last Call Working Draft</a>:</p>
-
-  <ul>
-    <li>Allow keyword aliases to be defined using expanded term definitions</li>
-    <li>Mention profile URIs also in the sections describing the various document forms</li>
-    <li>Support relative IRIs in <code>@base</code></li>
-    <li>Clarify how the <code>profile</code> media type parameter is used in the content
-      negotiation process</li>
-    <li>Update grammar to disallow blank nodes as data types</li>
-    <li>Update grammar to allow blank node identifiers as value of <code>@vocab</code></li>
-    <li>Align the JSON-LD Data Model with the RDF Data Model</li>
-    <li>Support processing of documents with a <code>+json</code> media type as defined in
-      [<cite><a href="#bib-RFC6839" class="bibref">RFC6839</a></cite>]</li>
-    <li>Added a brief description of the data model to the introduction.</li>
-    <li>Fixed a number of document readability and flow issues related to all
-      of the updates made over the last several months</li>
-  </ul>
-
-  <p>Changes since the
     <a href="http://www.w3.org/TR/2013/CR-json-ld-20130910/">10&nbsp;September&nbsp;2013 Candidate Recommendation</a>:</p>
 
   <ul>
@@ -1281,7 +1262,7 @@
   with a <a href="#dfn-node" title="node" class="tref internalDFN">node</a>. The concept of a <a href="#dfn-node-type" title="node-type" class="tref internalDFN">node type</a> and
   a <a href="#dfn-value-type" title="value-type" class="tref internalDFN">value type</a> are different.</p></div>
 
-<p>Generally speaking, a <dfn id="dfn-node-type" title="node-type">node type</dfn> specifies the type of thing
+<p>A <dfn id="dfn-node-type" title="node-type">node type</dfn> specifies the type of thing
   that is being described, like a person, place, event, or web page. A
   <dfn id="dfn-value-type" title="value-type">value type</dfn> specifies the data type of a particular value, such
   as an integer, a floating point number, or a date.</p>

--- a/spec/latest/json-ld-api/index.html	Wed Oct 30 15:25:09 2013 +0100
+++ b/spec/latest/json-ld-api/index.html	Thu Oct 31 15:17:25 2013 +0100
@@ -178,52 +178,6 @@
   </ul>
 
   <p>Changes since the
-    <a href="http://www.w3.org/TR/2013/WD-json-ld-api-20130411/">11&nbsp;April&nbsp;2013 Last Call Working Draft</a>:</p>
-
-  <ul>
-    <li>Use of DOM Futures instead of callbacks in the Application Programming Interface</li>
-    <li>Processing of terms that are redefined to themselves without raising an
-      <code class="error"><a href="#idl-def-JsonLdErrorCode.cyclic-IRI-mapping">cyclic IRI mapping</a></code> error</li>
-    <li>Raise an <code class="error"><a href="#idl-def-JsonLdErrorCode.invalid-IRI-mapping">invalid IRI mapping</a></code>
-      error if relative URLs are used in term definitions</li>
-    <li>Support relative IRIs in <code>@base</code></li>
-    <li>Remove default value of <code class="idlMemberName"><a href="#idl-def-JsonLdOptions">JsonLdOption's</a></code>
-      <code class="idlMemberName"><a href="#widl-JsonLdOptions-base">base</a></code> member</li>
-    <li>Support lists of lists when serializing RDF as JSON-LD</li>
-    <li>Support for relative URLs in <code>@base</code> and documents that
-      do not have a base value</li>
-  </ul>
-
-  <p>Changes since the
-    <a href="http://www.w3.org/TR/2013/WD-json-ld-api-20130516/">16&nbsp;May&nbsp;2013 Last Call Working Draft</a>:</p>
-
-  <ul>
-    <li>Ensure determinism of the Deserialize JSON-LD to RDF algorithm by specifying the processing order</li>
-    <li>Change the default value of the <em>use native types</em> flag in the Serialize RDF as JSON-LD
-      algorithm to <code>false</code></li>
-    <li>Clarify that the <i>identifier map</i> and the <i>counter</i> used by the
-      Generate Blank Node Identifier algorithm are reset before running the Flattening
-      and the Deserialize JSON-LD to RDF algorithms</li>
-    <li>Raise an error if a blank node is used as data type</li>
-    <li>Clarify that blank node identifier are supported as value of <code>@vocab</code></li>
-    <li>When generating RDF, exclude <tref title="rdf triple">triples</tref> containing a
-      <tref>blank node</tref> <tref title="rdf predicate">predicate</tref>, unless the
-      <i>produce generalized RDF</i> flag is set; discard <tref title="rdf triple">triples</tref>
-      containing relative IRIs and graphs with a relative IRI as graph name</li>
-    <li>Update reference to DOM Promises (have been called DOM Futures)</li>
-    <li>Fix bug in <a href="#serialize-rdf-as-json-ld-algorithm">Serialize RDF to JSON-LD algorithm</a> to
-      handle lists correctly</li>
-    <li>Support processing of documents with a <code>+json</code> media type as defined in
-      [[RFC6839]]</li>
-    <li>Use the <a>LoadDocumentCallback</a> (previously <code>LoadContextCallback</code>)
-      to retrieve remote contexts and remote documents</li>
-    <li>Allow contexts to be passed into the API directly. Previously only context documents, i.e.,
-      objects having a <code>@context</code> member were allowed.</li>
-    <li>Clarify the usage of the
-      <code class="idlMemberName"><a href="#widl-JsonLdOptions-documentLoader">documentLoader</a></code> option.</li>
-  </ul>
-
-  <p>Changes since the
     <a href="http://www.w3.org/TR/2013/CR-json-ld-api-20130910/">10&nbsp;September&nbsp;2013 Candidate Recommendation</a>:</p>
 
   <ul>

--- a/spec/latest/json-ld/index.html	Wed Oct 30 15:25:09 2013 +0100
+++ b/spec/latest/json-ld/index.html	Thu Oct 31 15:17:25 2013 +0100
@@ -157,25 +157,6 @@
   </ul>
 
   <p>Changes since the
-    <a href="http://www.w3.org/TR/2013/WD-json-ld-20130411/">11&nbsp;April&nbsp;2013 Last Call Working Draft</a>:</p>
-
-  <ul>
-    <li>Allow keyword aliases to be defined using expanded term definitions</li>
-    <li>Mention profile URIs also in the sections describing the various document forms</li>
-    <li>Support relative IRIs in <code>@base</code></li>
-    <li>Clarify how the <code>profile</code> media type parameter is used in the content
-      negotiation process</li>
-    <li>Update grammar to disallow blank nodes as data types</li>
-    <li>Update grammar to allow blank node identifiers as value of <code>@vocab</code></li>
-    <li>Align the JSON-LD Data Model with the RDF Data Model</li>
-    <li>Support processing of documents with a <code>+json</code> media type as defined in
-      [[RFC6839]]</li>
-    <li>Added a brief description of the data model to the introduction.</li>
-    <li>Fixed a number of document readability and flow issues related to all
-      of the updates made over the last several months</li>
-  </ul>
-
-  <p>Changes since the
     <a href="http://www.w3.org/TR/2013/CR-json-ld-20130910/">10&nbsp;September&nbsp;2013 Candidate Recommendation</a>:</p>
 
   <ul>
@@ -1185,7 +1166,7 @@
   with a <tref>node</tref>. The concept of a <tref>node type</tref> and
   a <tref>value type</tref> are different.</p>
 
-<p>Generally speaking, a <tdef>node type</tdef> specifies the type of thing
+<p>A <tdef>node type</tdef> specifies the type of thing
   that is being described, like a person, place, event, or web page. A
   <tdef>value type</tdef> specifies the data type of a particular value, such
   as an integer, a floating point number, or a date.</p>