--- a/spec/latest/json-ld-api/index.html	Tue Dec 04 18:19:29 2012 +0100
+++ b/spec/latest/json-ld-api/index.html	Tue Dec 04 18:37:18 2012 +0100
@@ -450,13 +450,23 @@
     MAY, and OPTIONAL in this specification are to be interpreted as described
     in [[!RFC2119]].</p>
 
-  <p>There is only one class of product that can claim conformance to this
-    specification: a <tref>JSON-LD processor</tref>.
+  <p>There are two classes of products that can claim conformance to this
+    specification: <tref title="JSON-LD Implementation">JSON-LD Implementations</tref>
+    and <tref title="JSON-LD Processor">JSON-LD Processors</tref>.
 
-  <p>A conforming <tdef>JSON-LD processor</tdef> is a system capable of transforming
-    JSON-LD documents according the algorithms defined in this specification.
-    This specification does not define how JSON-LD processors handle non-conforming
-    input documents.</p>
+  <p>A conforming <tdef>JSON-LD Implementation</tdef> is a system capable of transforming
+    JSON-LD documents according the algorithms defined in this specification.</p>
+
+  <p>A conforming <tdef>JSON-LD Processor</tdef> is a conforming <tref>JSON-LD Implementation</tref>
+    that exposes the application programming interface (API) defined in this specification.</p>
+
+  <p>The algorithms in this specification are generally written with more concern for clarity than
+    over efficiency. Thus, JSON-LD Implementations and Processors may implement the algorithms
+    given in this specification in any way desired, so long as the end result is indistinguishable
+    from the result that would be obtained by the specification's algorithms.</p>
+
+  <p>This specification does not define how JSON-LD Implementations or Processors handle
+    non-conforming input documents.</p>
 
   <p class="note">Implementers can partially check their level of conformance to
     this specification by successfully passing the test cases of the JSON-LD test