Fix broken links in specification.

index.html

@@ -3988,7 +3988,7 @@ <h3>JSON-LD</h3>
 
         <p>
 As elaborated upon in Section
-<a href="#credential-type-specific-processing"></a>, some software applications
+<a href="#json-processing"></a>, some software applications
 might not perform generalized JSON-LD processing. Authors of <a>conforming
 documents</a> are advised that interoperability might be reduced if JSON-LD
 keywords in the `@context` value are used to globally affect values in a
@@ -4003,7 +4003,7 @@ <h3>JSON-LD</h3>
         <p>
 In order to increase interoperability, <a>conforming document</a> authors are
 urged to not use JSON-LD features that are not easily detected when performing
-<a href="#credential-type-specific-processing">
+<a href="#json-processing">
 credential-type-specific processing</a>. These features include:
         </p>
 
@@ -5560,17 +5560,17 @@ <h4>Inappropriate Use</h4>
 While valid cryptographic signatures and successful status checks
 signify the reliability of <a>credentials</a>, they do not signify that all <a>credentials</a>
 are interchangeable for all contexts. It is crucial that <a>verifiers</a>
-also <a>validate</a> any claims which might be relevant, considering the source and
-nature of the claim as well as privilege or service for which the credential is
-presented.
+also <a href="#validation-0">validate</a> any claims which might be relevant,
+considering the source and nature of the claim as well as privilege or service
+for which the credential is presented.
         </p>
         <p>
 For instance, in scenarios where a certified medical diagnosis is required, a
 self-asserted <a>credential</a> carrying the necessary data might not suffice
 because it lacks validity from an authoritative medical source. To ensure the
 propriety of <a>credential</a> use, stakeholders are urged to assess the
-<a>credential's</a> relevance and authority within the specific context of their
-intended application.
+<a href="#dfn-credential">credential's</a> relevance and authority within the
+specific context of their intended application.
         </p>
       </section>
     </section>