--- a/spec/latest/json-ld/index.html	Tue Jul 23 23:27:25 2013 +0200
+++ b/spec/latest/json-ld/index.html	Tue Jul 30 18:09:09 2013 +0200
@@ -2741,7 +2741,7 @@
 
   <p>If JSON-LD content is extracted as RDF [[RDF11-CONCEPTS]], it should be expanded into an
     <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-dataset">RDF Dataset</tref> using the
-    <cite><a href="../json-ld-api/#convert-to-rdf-algorithm">Convert to RDF Algorithm</a></cite>
+    <cite><a href="../json-ld-api/#deserialize-to-rdf-algorithm">Deserialize to RDF Algorithm</a></cite>
     [[JSON-LD-API]].</p>
 </section>
 
@@ -2829,9 +2829,9 @@
       <a href="http://www.w3.org/2011/rdf-wg/wiki/JSON-LD_Features_at_Risk">features "at risk" in JSON-LD 1.0</a></p>
     <p>RDF does not currently allow a <tref>blank node</tref> to be
       used as a <tref>property</tref>, while JSON-LD
-      does. JSON-LD to RDF converters can work around this restriction, when interpreting
+      does. JSON-LD to RDF deserializers can work around this restriction, when interpreting
       JSON-LD as RDF, by transforming such <tref title="blank node">blank nodes</tref> to
-      <tref title="IRI">IRIs</tref>, minting new "Skolem IRIs" as per
+      <tref title="IRI">IRIs</tref>, by minting new "Skolem IRIs" as per
       <cite><a href="http://www.w3.org/TR/rdf11-concepts/#section-skolemization">Replacing Blank Nodes with IRIs</a></cite>
       of [[RDF11-CONCEPTS]]. Based on feedback from implementors, the
       Working Group may decide to disallow blank node properties in JSON-LD.
@@ -3239,8 +3239,8 @@
 
   <p>For authors and developers working with
     <tref title="blank node">blank nodes</tref> as
-    <tref title="property">properties</tref> when converting to RDF, there are
-    three potential approaches (in order of preference):</p>
+    <tref title="property">properties</tref> when deserializing to RDF, 
+    three potential approaches are suggested (in descending order of preference):</p>
 
   <ol>
     <li>If the author is not yet ready to commit to a stable IRI, the
@@ -3248,17 +3248,18 @@
     <li>If the developer wishes to use
     <tref title="blank node">blank nodes</tref> as
     <tref title="property">properties</tref> and also wishes to interpret the
-    data as a
+    data as a (non-standard)
     <tref href="http://www.w3.org/TR/rdf11-concepts/#fn-generalized-rdf-dataset">generalized RDF Dataset</tref>,
-    there is an option in the [[JSON-LD-API]] to do so.</li>
+    there is an option, <i>produce generalized RDF</i>, 
+    in the [[JSON-LD-API]] to do so.</li>
     <li>If the author or developer wishes to use
     <tref title="blank node">blank nodes</tref> as
     <tref title="property">properties</tref> and wishes to interpret the data
-    as a non-generalized RDF Dataset, it is possible
+    as a standard (non-generalized) RDF Dataset, it is possible
     to losslessly interpret JSON-LD as RDF by
     transforming <tref title="blank node">blank nodes</tref> used as
     <tref title="property">properties</tref> to <tref title="IRI">IRIs</tref>,
-    minting new "Skolem IRIs" as per
+    by minting new "Skolem IRIs" as per
     <cite><a href="http://www.w3.org/TR/rdf11-concepts/#section-skolemization">Replacing Blank Nodes with IRIs</a></cite>
     of [[RDF11-CONCEPTS]].</li>
   </ol>
@@ -3279,11 +3280,11 @@
     datasets to process the information.</p>
 
   <section class="informative">
-    <h3>Transformation from JSON-LD to RDF</h3>
-
-    <p>The process of turning a JSON-LD document depends on executing the
+    <h3>Deserialization from JSON-LD to RDF</h3>
+
+    <p>The process of deserializing a JSON-LD document depends on executing the
       algorithms defined in
-      <cite><a href="../json-ld-api/#rdf-conversion-algorithms">RDF Conversion Algorithms</a></cite>
+      <cite><a href="../json-ld-api/#rdf-serialization-deserialization-algorithms">RDF Serialization-Deserialization Algorithms</a></cite>
       in the JSON-LD Processing Algorithms and API specification [[JSON-LD-API]].
       It is beyond the scope of this document to detail these algorithms any further,
       but a summary of the necessary operations is provided to illustrate the process.</p>
@@ -3355,7 +3356,7 @@
     -->
     </pre>
 
-    <p>Transforming this to RDF now is a straightforward process of turning
+    <p>Deserializing this to RDF now is a straightforward process of turning
       each <tref>node object</tref> into one or more RDF triples. This can be
       expressed in Turtle as follows:</p>