From f6dff682c3bc20b57aa938f60c37071ba09b361e Mon Sep 17 00:00:00 2001 From: grausof Date: Wed, 31 Jul 2024 11:17:10 +0200 Subject: [PATCH] Update relying-party-solution.rst --- docs/en/relying-party-solution.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/relying-party-solution.rst b/docs/en/relying-party-solution.rst index 7f0c0da3b..eabd1c452 100644 --- a/docs/en/relying-party-solution.rst +++ b/docs/en/relying-party-solution.rst @@ -11,7 +11,7 @@ This section describes how a remote Relying Party or a Verifier App requests to In this section the following flows are described: -- :ref:`Remote Flow`, where the User presents a Credential to a remote Relying Party according to `OpenID4VP `_ Draft 20. In this scenario the user-agent and the Wallet Instance can be used in the same device (**Same Device Flow**), or in different devices (**Cross Device Flow**). +- :ref:`Remote Flow`, where the User presents a Credential to a remote Relying Party according to `OpenID4VP`_ Draft 20. In this scenario the user-agent and the Wallet Instance can be used in the same device (**Same Device Flow**), or in different devices (**Cross Device Flow**). - :ref:`Proximity Flow`, where the User presents a Credential to a Verifier App according to ISO 18013-5. The User interacts with a Verifier using proximity connection technologies such as QR Code and Bluetooth Low Energy (BLE). .. include:: remote-flow.rst