Presentation attestation - new page

Author: cljung

articles/active-directory/verifiable-credentials/TOC.yml

@@ -38,13 +38,13 @@
     items:
     - name: Directory based - Employee
       href: how-to-use-quickstart-verifiedemployee.md
-    - name: ID Token Hint attestation
+    - name: Id token hint attestation
       href: how-to-use-quickstart.md
-    - name: ID Token attestation
+    - name: Id token attestation
       href: how-to-use-quickstart-idtoken.md      
     - name: Presentation attestation
-      href: how-to-use-quickstart-vc.md
-    - name: Self Issued attestation
+      href: how-to-use-quickstart-presentation.md
+    - name: Self issued attestation
       href: how-to-use-quickstart-selfissued.md
   - name: Use the Verified ID Network
     href: how-use-vcnetwork.md

articles/active-directory/verifiable-credentials/credential-design.md

@@ -101,7 +101,7 @@ The following four attestation types are currently available to be configured in
 
 * **ID token hint**: The sample App and Tutorial use the ID token Hint. When this option is configured, the relying party app will need to provide claims that should be included in the verifiable credential in the Request Service API issuance request. Where the relying party app gets the claims from is up to the app, but it can come from the current sign-in session, from backend CRM systems or even from self asserted user input. To configure this option, please see this [how to guide](how-to-use-quickstart.md)
 
-* **Verifiable credentials**: The end result of an issuance flow is to produce a verifiable credential but you may also ask the user to Present a verifiable credential in order to issue one. The rules definition is able to take specific claims from the presented verifiable credential and include those claims in the newly issued verifiable credential from your organization.  To configure this option, please see this [how to guide](how-to-use-quickstart-vc.md)
+* **Verifiable credentials**: The end result of an issuance flow is to produce a verifiable credential but you may also ask the user to Present a verifiable credential in order to issue one. The rules definition is able to take specific claims from the presented verifiable credential and include those claims in the newly issued verifiable credential from your organization.  To configure this option, please see this [how to guide](how-to-use-quickstart-presentation.md)
 
 * **Self-attested claims**: When this option is selected, the user can type information directly into Authenticator. At this time, strings are the only supported input for self attested claims. To configure this option, please see this [how to guide](how-to-use-quickstart-selfissued.md)
 

articles/active-directory/verifiable-credentials/how-to-use-quickstart-vc.md renamed to articles/active-directory/verifiable-credentials/how-to-use-quickstart-presentation.md

@@ -27,7 +27,7 @@ In the Azure portal, when you select **Add credential**, you get the option to l
 
 On the **Create a new credential** page, enter the JSON code for the display and the rules definitions. In the **Credential name** box, give the credential a name. This name is just an internal name for the credential in the portal. The type name of the credential is defined in the `vc.type` property name in the rules definition. To create the credential, select **Create**.
 
-![Screenshot of the "Create a new credential" page, displaying JSON samples for the display and rules files.](media/how-to-use-quickstart/quickstart-create-new.png)
+:::image type="content" source="media/how-to-use-quickstart/quickstart-create-new.png" alt-text="Screenshot of the "Create a new credential" page, displaying JSON samples for the display and rules files.":::
 
 ## Sample JSON display definitions
 
@@ -123,7 +123,7 @@ Values
 
 During issuance, Authenticator prompts the user to select a matching credential. If the user has multiple matching credentials in the wallet, the user must select which one to present.
 
-![Screenshot of presentations claims input.](media/how-to-use-quickstart-vc\issue-verifiedid-vc.png)
+:::image type="content" source="media/how-to-use-quickstart-presentation/issue-presentation.png" alt-text="Screenshot of presentations claims input.":::
 
 ## Configure the samples to issue your custom credential
 
@@ -135,7 +135,7 @@ To configure your sample code to issue and verify your custom credential, you ne
 
 The easiest way to find this information for a custom credential is to go to your credential in the Azure portal. Select **Issue credential**. Then you have access to a text box with a JSON payload for the Request Service API. Replace the placeholder values with your environment's information. The issuer’s DID is the authority value.
 
-![Screenshot of the quickstart custom credential issue.](media/how-to-use-quickstart/quickstart-config-sample-2.png)
+:::image type="content" source="media/how-to-use-quickstart/quickstart-config-sample-2.png" alt-text="Screenshot of the quickstart custom credential issue.":::
 
 ## Next steps