From f1525279cd31a57e67cdc8b7c7bc09d5e67fd4b0 Mon Sep 17 00:00:00 2001 From: Giuseppe De Marco Date: Tue, 8 Aug 2023 11:54:28 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Francesco Grauso --- docs/en/relying-party-solution.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/en/relying-party-solution.rst b/docs/en/relying-party-solution.rst index e256deb2e..1103cf3ff 100644 --- a/docs/en/relying-party-solution.rst +++ b/docs/en/relying-party-solution.rst @@ -27,8 +27,7 @@ Remote Protocol Flow In this scenario the Relying Party provides the URL where the signed presentation request object is available for download. -The Relying Party MUST detect the device type of the requestor (Wallet Instance), if it is a mobile device or a workstation, and activate one the supported remote flows: - +Depending on whether the Relying Party client is on a mobile device or a workstation, it must activate one of the supported remote flows: * **Same Device**, the Relying Party MUST provide a HTTP redirect (302) location to the Wallet Instance; * **Cross Device**, the Relying Party MUST provide a QR Code which the User frames with their Wallet Instance.