From 9cf236e41a2ae1100085cd2b16e1cd938c5b5d0c Mon Sep 17 00:00:00 2001
From: Gabe <7622243+decentralgabe@users.noreply.github.com>
Date: Thu, 13 Jun 2024 11:31:57 -0700
Subject: [PATCH] Update openid-4-verifiable-presentations-1_0.md

Co-authored-by: Kristina <52878547+Sakurann@users.noreply.github.com>
---
 openid-4-verifiable-presentations-1_0.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/openid-4-verifiable-presentations-1_0.md b/openid-4-verifiable-presentations-1_0.md
index 372b2b7b..b68336ba 100644
--- a/openid-4-verifiable-presentations-1_0.md
+++ b/openid-4-verifiable-presentations-1_0.md
@@ -1834,7 +1834,7 @@ When combining OpenID for Verifiable Presentations with [@!SIOPv2], the Verifier
 6. Based on the user's identity and the Verifier's context, the Verifier determines whether additional credentials are required.
    - If no additional credentials are needed, the Verifier proceeds with issuing the authentication token to the user.
    - If additional credentials are required, the Verifier initiates the OpenID for Verifiable Presentations flow by sending a new Authorization Request with the `presentation_definition` or `presentation_definition_uri` parameter.
-7. The Wallet processes the Authorization Request, requests the necessary presentation from the user, and sends the Authorization Response back to the Verifier.
+7. The Wallet processes the Authorization Request, obtains the necessary consent from the user, and sends the Authorization Response back to the Verifier.
 8. The Verifier validates the presentation and issues the authentication token to the user.
 
 This flow allows the Verifier to make an informed decision about requesting credentials based on the authenticated user's context.