--- a/spec/latest/json-ld-syntax/index.html	Mon Nov 05 19:20:30 2012 +0100
+++ b/spec/latest/json-ld-syntax/index.html	Wed Nov 07 15:18:26 2012 +0100
@@ -199,12 +199,10 @@
 </ul>
 
 <p>Developers that require any of the facilities listed above will find JSON-LD
-  of interest. The syntax does not necessarily require applications to change their
-  JSON, but allows one to easily add meaning by simply adding or referencing a context.
-  The syntax is designed to not disturb already deployed systems running on JSON,
-  but provide a smooth upgrade path from JSON to JSON-LD. Finally, the format is
-  intended to be easy to parse, efficient to generate, and can operate inside of
-  devices that contain very little memory.</p>
+  of interest. The syntax is designed to not disturb already deployed systems
+  running on JSON, but provide a smooth upgrade path from JSON to JSON-LD.
+  Finally, the format is intended to be easy to parse, efficient to generate,
+  and can operate inside of devices that contain very little memory.</p>
 
 
 <section>
@@ -267,11 +265,10 @@
  <dt>Zero Edits, most of the time</dt>
  <dd>JSON-LD must provide a
  <a href="#referencing-contexts-from-json-documents">mechanism</a>
- that allows developers to specify <tref>context</tref> in a way that is
- out-of-band.
- This allows organizations that have
- already deployed large JSON-based infrastructure to add meaning to their
- JSON documents in a way that is not disruptive to their day-to-day operations and is
+ that allows developers to reference <tref title="context">contexts</tref> in
+ responses using plain old JSON. This allows organizations that have
+ already deployed large JSON-based infrastructure to use JSON-LD's features
+ in a way that is not disruptive to their day-to-day operations and is
  transparent to their current customers. At times, mapping JSON to
  a graph representation can become difficult. In these instances, rather than
  having JSON-LD support an esoteric use case, we chose not to support the
@@ -661,7 +658,7 @@
 <strong>homepage</strong>, and <strong>depiction</strong>,
 are defined in a <tref>context</tref>, and that context is used to resolve the
 names in <tref title="JSON object">JSON objects</tref>, machines are able to automatically expand the terms to
-something meaningful and unambiguous, like this:</p>
+something unambiguous like this:</p>
 
 <pre class="example" data-transform="updateExample"
      title="Expanded terms">
@@ -761,8 +758,7 @@
 <p>JSON keys that do not expand to an absolute IRI are ignored, or removed
 in some cases, by the [[JSON-LD-API]]. However, JSON keys that do not include
 a mapping in the <tref>context</tref> are still considered valid expressions
-in JSON-LD documents - the keys just don't have any machine-readable,
-semantic meaning.</p>
+in JSON-LD documents - the keys just don't expand to unambiguous identifiers.</p>
 
 <p><tref>Prefix</tref>es are expanded when the form of the value is a
   <tref>compact IRI</tref> represented as a <code>prefix:suffix</code>