--- a/spec/latest/json-ld-syntax/index.html	Sat Sep 29 17:42:51 2012 -0400
+++ b/spec/latest/json-ld-syntax/index.html	Sat Sep 29 20:07:08 2012 -0400
@@ -469,7 +469,7 @@
 <li>It has a syntax that is familiar across a large number of programming 
   languages.</li>
 <li>It is capable of representing many different types of data using two
-universal data structures; a collection of name/value pairs and lists.</li>
+universal data structures; a collection of key-value pairs and lists.</li>
 </ol>
 
 <p>
@@ -569,12 +569,13 @@
 <p style="text-align: center;">
 Figure 1: An example of a linked data graph.
 </p>
-<p>JSON-LD defines a mechanism to map JSON terms, i.e., keys and values, to IRIs. This does not mean
+<p>There are a number of best practices that can ensure that developers 
+will generate good Linked Data for the Web. JSON-LD
+formalizes those techniques by providing a mechanism to map JSON data, 
+i.e., keys and values, to <tref>IRI</tref>s. This does not mean
 that JSON-LD requires every key or value to be an IRI, but rather ensures that
 keys and values can be mapped to IRIs if the developer desires to transform
-their data into <tref>Linked Data</tref>. There are a few techniques that can ensure
-that developers will generate good Linked Data for the Web. JSON-LD
-formalizes those techniques.
+their data into <tref>Linked Data</tref>. 
 </p>
 
 </section>
@@ -709,7 +710,7 @@
   Developers and machines need the same sort of definition of terms. <tref title="IRI">IRIs</tref> provide a way to
   ensure that these terms are unambiguous. For example, the term <code>name</code> may
   map directly to the IRI <code>http://xmlns.com/foaf/0.1/name</code>. This allows JSON-LD documents to be constructed
-  using the common JSON practice of simple name/value pairs while ensuring that the data is useful outside of the
+  using the common JSON practice of simple key-value pairs while ensuring that the data is useful outside of the
   page, API or database in which it resides. The value of a term mapping
   MUST be either; 1) a simple string with the lexical form of an <tref>absolute IRI</tref> or
   2) <tref>compact IRI</tref>, or 3) an <tref>JSON object</tref> containing an
@@ -2682,7 +2683,7 @@
 <section id="grammar-node-definition">
 <h3>Node Definition</h3>
 <p>A <tref>node definition</tref> is a <tref>JSON object</tref>
-  containing one or more key/value pairs. Keys are <tref>IRI</tref>s,
+  containing one or more key-value pairs. Keys are <tref>IRI</tref>s,
   <tref>compact IRI</tref>s,
   <tref>term</tref>s defined within the <tref>active context</tref>, or one of the
   following keywords:</p>
@@ -2970,7 +2971,7 @@
 <section id="grammar-context">
 <h2>Context Definition</h2>
 <p>A <tdef>context definition</tdef> is a <tref>JSON object</tref>
-  containing one or more key/value pairs. Keys are non-keyword <tref title="string">strings</tref>
+  containing one or more key-value pairs. Keys are non-keyword <tref title="string">strings</tref>
   or the <code>@language</code> or <code>@vocab</code> <tref title="keyword">keywords</tref>.
   A <tref>context definition</tref>
   SHOULD NOT contain any keys having the lexical form of <tref>keyword</tref> other than