--- a/spec/latest/json-ld-syntax/index.html	Fri Jun 22 22:44:41 2012 -0400
+++ b/spec/latest/json-ld-syntax/index.html	Fri Jun 22 22:55:53 2012 -0400
@@ -759,7 +759,8 @@
 <p class="note">To ensure the best possible performance, it is a best practice to
 put the <tref>context</tref> definition at the top of the JSON-LD document. If it isn't listed
 first, processors have to save each key-value pair until the <tref>context</tref> is processed.
-This creates a memory and complexity burden for one-pass processors.</p>
+This creates a memory and complexity burden for certain types of
+low-memory footprint JSON-LD processors.</p>
 
 <p class="note">The <code>null</code> value is processed in a special way
 in JSON-LD. Unless otherwise specified, a JSON-LD processor MUST act as if a 
@@ -996,11 +997,14 @@
   <tref>unlabeled node</tref>.</p>
 
 <p class="note">To ensure the best possible performance, it is a best practice
-to put the <code>@id</code> <tref>keyword</tref> before other key-value pairs in a <tref>JSON object</tref>.
-If it isn't listed first, processors have to save each key-value pair until
-<code>@id</code> is processed before they can start generating triples.
-Not specifying the <code>@id</code> keyword first creates a memory and
-complexity burden for one-pass processors.</p>
+to put JSON-LD <tref>keyword</tref>s, such as
+<code>@id</code> and <code>@context</code> before other key-value pairs in a 
+<tref>JSON object</tref>.
+If keywords are not listed first, processors have to save each key-value 
+pair until at least the <code>@context</code> and the </code><code>@id</code> 
+are processed. Not specifying those keywords first creates a memory and
+complexity burden for low-memory footprint processors, forcing them to use
+more memory and computing cycles than necessary.</p>
 
 </section>