Clean up grammar and flow in IANA Considerations section.

Author: msporny

Diff for: index.html

@@ -7144,8 +7144,8 @@ <h2>IANA Considerations</h2>
       <section id="vc-ld-media-type">
         <h2>application/vc</h2>
         <p>
-This specification registers the `application/vc` Media Type specifically for
-identifying documents conforming to the Verifiable Credentials format.
+This specification registers the `application/vc` media type specifically for
+identifying documents conforming to the [=verifiable credentials=] format.
         </p>
         <table>
           <tr>
@@ -7163,15 +7163,15 @@ <h2>application/vc</h2>
           <tr>
             <td>Encoding considerations: </td>
             <td>
-Resources that use the "`application/vc`" Media Type are required to conform to
-all of the requirements for the "`application/ld+json`" Media Type and are
+Resources that use the `application/vc` media type are required to conform to
+all of the requirements for the `application/ld+json` media type and are
 therefore subject to the same encoding considerations specified in Section 11 of
-[[RFC7159]].
+[[[RFC7159]]].
             </td>
           </tr>
           <tr>
             <td>Security considerations: </td>
-            <td>As defined in this specification.</td>
+            <td>As defined in the [[[VC-DATA-MODEL-2.0]]].</td>
           </tr>
           <tr>
             <td>Contact: </td>
@@ -7183,32 +7183,33 @@ <h2>application/vc</h2>
         </table>
 
         <p>
-Note that while the Verifiable Credentials format uses JSON-LD conventions,
-there are a number of constraints and additional requirements for Verifiable
-Credential implementations that justify the use of a specific media type.
+Note that while the [=verifiable credentials=] format uses JSON-LD conventions,
+there are a number of constraints and additional requirements for [=verifiable
+credential=] implementations that justify the use of a specific media type.
         </p>
 
         <p>
-This media type can be used in an [=enveloping proof=] to denote the enveloped payload.
+This media type can be used in an [=enveloping proof=] to denote the enveloped
+payload.
         </p>
 
         <p>
 The credential is expected to be a valid
 <a data-cite="JSON-LD11#dfn-json-ld-document">JSON-LD document</a>.
-Credentials served with the "`application/vc`" media type are expected
-to have all [[JSON-LD11]] context information, including references to
+[=Verifiable credentials=] served with the `application/vc` media type are expected
+to have all [[[JSON-LD11]]] context information, including references to
 external contexts, within the body of the document. Contexts linked via a
 `http://www.w3.org/ns/json-ld#context` HTTP Link Header
 (see <a data-cite="JSON-LD11#interpreting-json-as-json-ld">Section 6.1</a>
-of [[JSON-LD11]]) are ignored.
+of [[[JSON-LD11]]]) are ignored.
         </p>
       </section>
 
       <section id="vp-ld-media-type">
         <h2>application/vp</h2>
         <p>
-This specification registers the `application/vp` Media Type specifically for
-identifying documents conforming to the Verifiable Presentations format.
+This specification registers the `application/vp` media type specifically for
+identifying documents conforming to the [=verifiable presentations=] format.
         </p>
         <table>
           <tr>
@@ -7226,15 +7227,15 @@ <h2>application/vp</h2>
           <tr>
             <td>Encoding considerations: </td>
             <td>
-Resources that use the "`application/vp`" Media Type are required to conform to
-all of the requirements for the "`application/ld+json`" Media Type and are
+Resources that use the `application/vp` media type are required to conform to
+all of the requirements for the `application/ld+json` media type and are
 therefore subject to the same encoding considerations specified in Section 11 of
-[[RFC7159]].
+[[[RFC7159]]].
             </td>
           </tr>
           <tr>
             <td>Security considerations: </td>
-            <td>As defined in this specification.</td>
+            <td>As defined in [[[VC-DATA-MODEL-2.0]]].</td>
           </tr>
           <tr>
             <td>Contact: </td>
@@ -7246,22 +7247,24 @@ <h2>application/vp</h2>
         </table>
 
         <p>
-Note that while the Verifiable Credentials format uses JSON-LD conventions,
-there are a number of constraints and additional requirements for Verifiable
-Credential implementations that justify the use of a specific media type.
+Note that while the [=verifiable presentations=] format uses JSON-LD
+conventions, there are a number of constraints and additional requirements for
+[=verifiable presentation=] implementations that justify the use of a specific
+media type.
         </p>
 
         <p>
-This media type can be used in an [=enveloping proof=] to denote the enveloped payload.
+This media type can be used in an [=enveloping proof=] to denote the enveloped
+payload.
         </p>
         <p>
 The presentation is expected to be a valid
-<a data-cite="JSON-LD11#dfn-json-ld-document">JSON-LD document</a>.
-Presentations served with the "`application/vp`" media type are expected
-to have all [[JSON-LD11]] context information, including references to
-external contexts, within the body of the document. Contexts linked via a
-`http://www.w3.org/ns/json-ld#context` HTTP Link Header
-(see <a data-cite="JSON-LD11#interpreting-json-as-json-ld">Section 6.1</a>
+<a data-cite="JSON-LD11#dfn-json-ld-document">JSON-LD document</a>. [=Verifiable
+presentations=] served with the `application/vp` media type are expected to have
+all [[[JSON-LD11]]] context information, including references to external
+contexts, within the body of the document. Contexts linked via a
+`http://www.w3.org/ns/json-ld#context` HTTP Link Header (see <a
+data-cite="JSON-LD11#interpreting-json-as-json-ld">Section 6.1</a>
 of [[JSON-LD11]]) are ignored.
         </p>
       </section>