Fixed a editorial issues in Section 4 of JSON-LD spec.
--- a/spec/latest/json-ld-syntax/index.html Sun Jan 20 18:29:32 2013 -0500
+++ b/spec/latest/json-ld-syntax/index.html Sun Jan 20 18:31:59 2013 -0500
@@ -392,11 +392,18 @@
<section class="normative">
<h1>Conformance</h1>
-<p>The JSON-LD specification describes the conformance criteria for JSON-LD documents (relevant to authors and authoring tool implementors).</p>
-
-<p>A <tref>JSON-LD document</tref> complies with this specification if it follows the normative statements for documents defined in sections <a href="#referencing-contexts-from-json-documents"></a> and <a href="#json-ld-grammar"></a>. For convenience, normative statements for documents are often phrased as statements on the properties of the document.</p>
-
-<p>The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL in this Recommendation have the meaning defined in [[!RFC2119]].</p>
+<p>This specification describes the conformance criteria for JSON-LD documents.
+This criteria is relevant to authors and authoring tool implementors.</p>
+
+<p>A <tref>JSON-LD document</tref> complies with this specification if it
+follows the normative statements for documents defined in sections
+<a href="#referencing-contexts-from-json-documents"></a> and
+<a href="#json-ld-grammar"></a>. For convenience, normative statements for
+documents are often phrased as statements on the properties of the document.</p>
+
+<p>The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
+SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL in this
+Recommendation have the meaning defined in [[!RFC2119]].</p>
</section>