--- a/spec/latest/json-ld-syntax/index.html	Wed Feb 27 13:46:22 2013 +0100
+++ b/spec/latest/json-ld-syntax/index.html	Wed Feb 27 09:17:19 2013 -0800
@@ -243,7 +243,7 @@
    <dt>Zero Edits, most of the time</dt>
    <dd>JSON-LD must make the transition to JSON-LD as simple as possible. In many cases,
      zero edits to the JSON document and the addition of one line to the HTTP response
-     should suffice (see <a href="#referencing-contexts-from-json-documents"></a>).
+     should suffice (see <a href="#interpreting-json-as-json-ld">Interpreting JSON as JSON-LD</a>).
      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
@@ -374,7 +374,7 @@
   <p>A <tref>JSON-LD document</tref> complies with this specification if it follows
     the normative statements in section <a href="#json-ld-grammar"></a>. JSON documents
     can be interpreted as JSON-LD by following the normative statements in section
-    <a href="#referencing-contexts-from-json-documents"></a>. For convenience, normative
+    <a href="#interpreting-json-as-json-ld">Interpreting JSON as JSON-LD</a>. For convenience, normative
     statements for documents are often phrased as statements on the properties of the document.</p>
 
   <p>The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT,