--- a/spec/latest/json-ld-api/index.html	Tue Jul 30 17:12:59 2013 +0200
+++ b/spec/latest/json-ld-api/index.html	Tue Jul 30 17:39:31 2013 +0200
@@ -121,8 +121,7 @@
   <p>This specification defines an Application Programming Interface (API)
     and a set of algorithms for programmatic transformations of JSON-LD
     documents. Restructuring data according to the defined transformations
-    often dramatically simplifies its usage.<br>
-</p>
+    often dramatically simplifies its usage.</p>
 </section>
 
 <section id="sotd">
@@ -3145,32 +3144,29 @@
       Please note that RDF does not allow a <tref>blank node</tref> to be used
       as a <tref>property</tref>, while JSON-LD does.  Therefore, by default
       RDF triples that would have contained blank nodes as properties are
-      discarded when interpreting JSON-LD as RDF.  
-      For authors and developers working with
-    <tref title="blank node">blank nodes</tref> as
-    <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
-      property should be mapped to an IRI that is documented as unstable.</li>
-    <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 (non-standard)
-    <tref href="http://www.w3.org/TR/rdf11-concepts/#fn-generalized-rdf-dataset">generalized RDF Dataset</tref>,
-    there is an option, <i>produce generalized RDF</i>, 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 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>,
-    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>
+      discarded when interpreting JSON-LD as RDF. For authors and developers
+      working with <tref title="blank node">blank nodes</tref> as
+      <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
+        property should be mapped to an IRI that is documented as unstable.</li>
+      <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 (non-standard)
+        <tref href="http://www.w3.org/TR/rdf11-concepts/#fn-generalized-rdf-dataset">generalized RDF Dataset</tref>,
+        there is an option, <i>produce generalized RDF</i>, 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 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>,
+        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>
 
     <div class="issue atrisk" data-number="3" title="Allow blank nodes to be used as properties">
       <p class="atrisk-head">Note: This feature is