--- a/spec/latest/index.html	Wed Oct 05 17:18:21 2011 +0200
+++ b/spec/latest/index.html	Wed Oct 05 17:52:13 2011 +0200
@@ -319,8 +319,8 @@
 out-of-band. The syntax is designed to not disturb already deployed systems
 running on JSON, but provide a smooth upgrade path from JSON to JSON with
 added semantics. Finally, the format is intended to be easy to parse, efficient to
-generate, stream-based and document-based processing compatible, and require
-a very small memory footprint in order to operate.
+generate, convertible to RDF in one pass, and require a very small memory footprint
+in order to operate.
 </p>
 
 <section>
@@ -469,8 +469,8 @@
  and support a simplified syntax instead. So, while Zero Edits is a goal,
  it is not always possible without adding great complexity to the language.
  </dd>
- <dt>Streaming</dt>
- <dd>The format supports both document-based and stream-based processing.</dd>
+ <dt>One-pass Conversion to RDF</dt>
+ <dd>JSON-LD supports one-pass conversion to RDF with a very small memory footprint.</dd>
 </dl>
 </section>
 
@@ -658,6 +658,11 @@
 <tref>prefix</tref>es that can be used to expand JSON keys and values into
 <tref>IRI</tref>s.</p>
 
+<p class="note">To ensure the best possible performance, it is a best practice to
+put the context 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 context is processed.
+This creates a memory and complexity burden for one-pass processors.</p>
+
 </section>
 
 <section>
@@ -841,6 +846,12 @@
 <code>http://example.org/people#joebob</code>.
 </p>
 
+<p class="note">To ensure the best possible performance, it is a best practice to
+put the <code>@subject</code> key before other key-value pairs in an object. If
+it isn't listed first, processors have to save each key-value pair until
+<code>@subject</code> is processed before they can create valid triples. This
+creates a memory and complexity burden for one-pass processors.</p>
+
 </section>
 
 <section>
@@ -3526,8 +3537,7 @@
   <p>
     JSON-LD is intended to have an easy to parse grammar that closely models existing
     practice in using JSON for describing object representations. This allows the use
-    of existing libraries for parsing JSON in a document-oriented fashion, or can allow
-    for stream-based parsing similar to SAX.
+    of existing libraries for parsing JSON.
   </p>
   <p>
     As with other grammars used for describing <tref>Linked Data</tref>, a key concept is that of