Ease readability in Getting Started section.

Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
Co-authored-by: Dave Longley <dlongley@digitalbazaar.com>

index.html

@@ -1056,11 +1056,22 @@ <h3>Getting Started</h3>
 
         <p>
 This specification is designed to ease the prototyping of new types of
-<a>verifiable credentials</a>. Developers are provided with the following
-template that they can copy-paste into common <a>verifiable credential</a>
+<a>verifiable credentials</a>. Developers can copy the
+template below and paste it into common <a>verifiable credential</a>
 tooling to start issuing, holding, and verifying prototype credentials.
         </p>
 
+        <p>
+It is expected that a developer will change `MyPrototypeCredential` below to
+the type of credential they would like to create. Since
+<a>verifiable credentials</a> talk about subjects, each property-value pair in
+the `credentialSubject` object expresses a particular attribute of the
+credential subject. Once a developer has added a number of these property-value
+combinations, the modified object can be sent to <a>verifiable credential</a>
+issuer sofware and a <a>verifiable credential</a> will be created for the
+developer. From a prototyping standpoint, that is all a developer needs to do.
+        </p>
+
         <pre class="example nohighlight" title="A template for creating prototype verifiable credentials">
 {
   "@context": ["https://www.w3.org/ns/credentials/v2"],
@@ -1071,24 +1082,15 @@ <h3>Getting Started</h3>
 }
         </pre>
 
-        <p>
-It is expected that a developer would change `MyPrototypeCredential` above to
-the type of credential they would like to create. Since
-<a>verifiable credentials</a> talk about subjects, each property-value pair in
-the `credentialSubject` object expresses a particular attribute of the
-credential subject. Once a developer has added a number of these property-value
-combinations, the modified object can be sent to a <a>verifiable credential</a>
-issuer sofware and a <a>verifiable credential</a> will be created for the
-developer. From a prototyping standpoint, that is all a developer needs to do.
-        </p>
-
         <p>
 Once a developer has prototyped their credential to a point where they believe
-all of the credential properties are stable, it is advised that they generate a
-vocabulary and context file for their application and publish it at a stable URL
+all of the credential properties are stable, it is advised that they generate
+vocabulary and context files for their application and publish them at stable URLs
 so that other developers can use the same vocabulary and context to achieve
 interoperability. This process is covered in Section
-<a href="#extensibility"></a>.
+<a href="#extensibility"></a>. Alternatively, developers can reuse existing vocabulary
+and context files that happen to fit their use case. They can explore the Verifiable
+Credential Specifications Directory [[VC-SPECS]] for reusable resources.
         </p>
 
       </section>