Corrects out of sync link titles in section 4.3 to json-ld spec (#955)

* Corrects out of sync link titles in section 4.3 to json-ls spec

* Remove unmatched </a>

Author: richardbergquist

index.html

@@ -1419,9 +1419,9 @@ <h3>Types</h3>
         <p class="note">
 The <a>type</a> system for the Verifiable Credentials Data Model is the same as
 for [[JSON-LD]] and is detailed in
-<a href="https://www.w3.org/TR/json-ld/#specifying-the-type">Section 5.4:
+<a href="https://www.w3.org/TR/json-ld/#specifying-the-type">Section 3.5:
 Specifying the Type</a> and
-<a href="https://www.w3.org/TR/json-ld/#json-ld-grammar">Section 8: JSON-LD
+<a href="https://www.w3.org/TR/json-ld/#json-ld-grammar">Section 9: JSON-LD
 Grammar</a>. When using a JSON-LD context (see Section
 <a href="#extensibility"></a>), this specification aliases the
 <code>@type</code> keyword to <code>type</code> to make the JSON-LD documents
@@ -1717,7 +1717,7 @@ <h3>Proofs (Signatures)</h3>
 and embedded proofs. An <dfn class="lint-ignore">external proof</dfn> is one
 that wraps an expression of this data model, such as a JSON Web Token, which is
 elaborated on in the Securing Verifiable Credentials using JSON Web Tokens
-[[?VC-JWT]] specification</a>. An <dfn>embedded proof</dfn> is a mechanism where
+[[?VC-JWT]] specification. An <dfn>embedded proof</dfn> is a mechanism where
 the proof is included in the data, such as a Data Integrity Proof, which is
 elaborated upon in Verifiable Credential Data Integrity [[?VC-DATA-INTEGRITY]].
         </p>