--- a/spec/latest/json-ld/index.html	Sat Jul 20 19:39:11 2013 -0400
+++ b/spec/latest/json-ld/index.html	Sat Jul 20 19:44:09 2013 -0400
@@ -264,8 +264,8 @@
 
   <dl>
    <dt>Simplicity</dt>
-   <dd>No extra processors or software libraries should be necessary to use JSON-LD
-     in its most basic form. The language will provide developers with a very easy
+   <dd>No extra processors or software libraries are necessary to use JSON-LD
+     in its most basic form. The language provides developers with a very easy
      learning curve. Developers only need to know JSON and two
      <tref title="keyword">keywords</tref> (<code>@context</code>
      and <code>@id</code>) to use the basic functionality in JSON-LD.</dd>
@@ -273,13 +273,13 @@
    <dd>A JSON-LD document is always a valid JSON document. This ensures that
     all of the standard JSON libraries work seamlessly with JSON-LD documents.</dd>
    <dt>Expressiveness</dt>
-   <dd>The syntax must be able to serialize directed graphs. This ensures that almost
+   <dd>The syntax serializes directed graphs. This ensures that almost
     every real world data model can be expressed.</dd>
    <dt>Terseness</dt>
-   <dd>The JSON-LD syntax must be very terse and human readable, requiring as
+   <dd>The JSON-LD syntax is very terse and human readable, requiring as
     little effort as possible from the developer.</dd>
    <dt>Zero Edits, most of the time</dt>
-   <dd>JSON-LD must ensure a smooth and simple transition from existing 
+   <dd>JSON-LD ensures a smooth and simple transition from existing 
      JSON-based systems. In many cases,
      zero edits to the JSON document and the addition of one line to the HTTP response
      should suffice (see <a class="sectionRef" href="#interpreting-json-as-json-ld"></a>).
@@ -291,12 +291,12 @@
      In these instances, rather than extending JSON-LD to support 
      esoteric use cases, we chose not to support the use case. While Zero 
      Edits is a design goal, it is not always possible without adding 
-     great complexity to the language. We should focus on simplicity when 
+     great complexity to the language. JSON-LD focuses on simplicity when 
      possible.</dd>
     <dt>Usable as RDF</dt>
-    <dd>JSON-LD must be usable by developers as
+    <dd>JSON-LD is usable by developers as
       idiomatic JSON, with no need to understand RDF [[RDF11-CONCEPTS]].
-      JSON-LD must also be usable as RDF, so people intending to use JSON-LD
+      JSON-LD is also usable as RDF, so people intending to use JSON-LD
       with RDF tools will find it can be used like any other RDF syntax.
       Complete details of how JSON-LD relates to RDF are in
       <a href="#relationship-to-rdf"></a>.</dd>