From 2d5207dcd1c20d9f0a1e9fde0e3403c4a5bd7f57 Mon Sep 17 00:00:00 2001
From: andreasabr <97103206+andreasabr@users.noreply.github.com>
Date: Fri, 16 Feb 2024 10:43:09 +0100
Subject: [PATCH] Typo errors fixed, added VIDWallet into the implementers
 table (#22)

* Added VIDWallet to the implementers' table
* Fixed a few typos
---
 ewc-rfc002-present-verifiable-credentials.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/ewc-rfc002-present-verifiable-credentials.md b/ewc-rfc002-present-verifiable-credentials.md
index 9fd851e..98de263 100644
--- a/ewc-rfc002-present-verifiable-credentials.md
+++ b/ewc-rfc002-present-verifiable-credentials.md
@@ -33,11 +33,11 @@
 
 # 1.0	Summary
 
-This specification implements the OID4VCI workflow for any verifier (relying party) as per reference specification [1]. This minimises risks towards interoperability across the European Wallet Ecosystem with a standard specification in the EUDI wallet ecosystem as per the ARF [2] requirements. 
+This specification implements the OIDC4VP workflow for any verifier (relying party) as per reference specification [1]. This minimises risks towards interoperability across the European Wallet Ecosystem with a standard specification in the EUDI wallet ecosystem as per the ARF [2] requirements. 
 
 # 2.0	Motivation
 
-The EWC LSP must align with the standard protocol for issuing credentials. This is the basis of interoperability between Verifies (Relying Parties) and Holders across the EWC LSPs. The assumption is that the user is familiar with the EWC-chosen protocols and standards and can refer to original standards references when necessary.
+The EWC LSP must align with the standard protocol for issuing credentials. This is the basis of interoperability between Verifiers (Relying Parties) and Holders across the EWC LSPs. The assumption is that the user is familiar with the EWC-chosen protocols and standards and can refer to original standards references when necessary.
 
 # 3.0	Messages
 
@@ -251,8 +251,10 @@ Some of the identifier deviations from success responses are as given:
    <td>ValidatedID
    </td>
    <td>
+     <a href="https://apps.apple.com/us/app/vidwallet/id1554340592">VIDwallet for iOS</a>, <a href="https://play.google.com/store/apps/details?id=com.validatedid.wallet">VIDwallet for Android</a>
    </td>
    <td>
+     Planned Mar’23
    </td>
   </tr>
   <tr>
@@ -288,4 +290,4 @@ Some of the identifier deviations from success responses are as given:
 1. OpenID Foundation (2023), 'OpenID for Verifiable Presentations (OID4VP)', Available at: [https://openid.net/specs/openid-4-verifiable-presentations-1_0.html](https://openid.net/specs/openid-4-verifiable-presentations-1_0.html) (Accessed: February 1, 2024).
 2. European Commission (2023) The European Digital Identity Wallet Architecture and Reference Framework (2023-04, v1.1.0)  [Online]. Available at: [/~https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/releases](/~https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/releases) (Accessed: October 16, 2023).
 3. RFC 9101 OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request (JAR) [https://www.rfc-editor.org/rfc/rfc9101.html#name-request-using-the-request_u](https://www.rfc-editor.org/rfc/rfc9101.html#name-request-using-the-request_u)  (Accessed: February 05, 2024)
-4. DIF Presentation Exchange:  [https://identity.foundation/presentation-exchange](https://identity.foundation/presentation-exchange)  (Accessed: February 07, 2024)
\ No newline at end of file
+4. DIF Presentation Exchange:  [https://identity.foundation/presentation-exchange](https://identity.foundation/presentation-exchange)  (Accessed: February 07, 2024)