italia · steps88 · Sep 30, 2025 · Sep 30, 2025 · Oct 1, 2025 · Oct 1, 2025
diff --git a/docs/en/brand-identity.rst b/docs/en/brand-identity.rst
@@ -18,7 +18,9 @@ Primary Actors MUST use these Official Resources and MUST comply with all relate
 Naming
 -------
 
-"IT-Wallet System" is the official name that MUST be used in all written and verbal contexts, both physical and digital. Below are the requirements for the correct spelling and pronunciation:
+The term "IT-Wallet System", as defined by the establishing regulation, is the official name that SHOULD be used in institutional, formal, or legal contexts to refer to the system.  
+
+The contracted form "IT-Wallet" is the official Brand name that MUST be used in all communications and disclosures, whether written or verbal, physical or digital, to refer to the "IT-Wallet System". Below are the requirements for the correct spelling and pronunciation:
 
 - The use of uppercase letters for "IT" and the initials of "Wallet" and "System" MUST be followed;
 
@@ -30,7 +32,7 @@ Naming
 Visual Identity
 ----------------
 
-The IT-Wallet System has its own Visual Identity. All actors within the ecosystem MUST ensure that their Visual Identity and that of their Technical Solutions are distinct yet compatible and cohesive with the Visual Identity of IT-Wallet System. Specifically, all Primary Actors MAY use the Official Resources related to the Visual Identity of the IT-Wallet System. Their use MUST be exclusively aimed at representing the participation in the IT-Wallet System and not at replacing the Visual Identity of their own Technical Solutions.
+The IT-Wallet Brand has its own Visual Identity. All actors within the ecosystem MUST ensure that their Visual Identity and that of their Technical Solutions are distinct yet compatible and cohesive with the Visual Identity of IT-Wallet System. Specifically, all Primary Actors MAY use the Official Resources related to the Visual Identity of the IT-Wallet System. Their use MUST be exclusively aimed at representing the participation in the IT-Wallet System and not at replacing the Visual Identity of their own Technical Solutions.
 
 Logo
 ^^^^^

diff --git a/docs/en/functionalities.rst b/docs/en/functionalities.rst
@@ -147,8 +147,8 @@ Below are illustrated the User Experience requirements for the issuance of an El
 
 - The User interacts with the Engagement Button clearly displayed in the Touchpoint interface; 
 - The User selects the Wallet Solution with which to proceed, through an interface that SHOULD follow the directions and functionalities described for the *Selection Page* in the :ref:`functionalities:Authentication` section; 
-- (*cross-device only*) the User scans the QR code that invokes the opening of their chosen Wallet Instance, through an interface that SHOULD follow the directions and functionalities described for the *QR Code Page* in the :ref:`functionalities:Authentication` section; 
-- (*cross-device only*) the User displays a message inviting them to continue on their chosen Wallet Instance, through an interface that SHOULD follow the directions and functionalities described for the *Waiting Page* in the :ref:`functionalities:Authentication` section; 
+- (*cross-device only*) the User scans the QR code that invokes the opening of their chosen Wallet Instance, through an interface that MUST follow the directions and functionalities described for the *QR Code Page* in the :ref:`functionalities:Authentication` section; 
+- (*cross-device only*) the User displays a message inviting them to continue on their chosen Wallet Instance, through an interface that MUST follow the directions and functionalities described for the *Waiting Page* in the :ref:`functionalities:Authentication` section; 
 - The User accesses their Wallet Instance using the unlock method previously set; 
 - The User views the PID data, if required for the request of the Electronic Attestation of Attributes, the name of the related Electronic Attestation of Attributes Provider, and any related information policy. The User gives their consent to proceed, presenting their PID data to the Electronic Attestation of Attributes Provider, or cancels the operation; 
 - The User views any additional information on requirements and/or limitations related to obtaining the Electronic Attestation of Attributes; 
@@ -238,6 +238,7 @@ Below are the User Experience requirements related to both methods that the Wall
 **Same-Device Mode**
 
 - The User clicks the Engagement Button provided on the Relying Party's Touchpoint;
+- The User selects the Wallet Solution to proceed with, through an interface that MUST follow the instructions and functionalities provided for the Selection Page described in the :ref:`functionalities:Authentication` section;
 - The User accesses their Wallet Instance using the unlock method previously set;
 - The User reviews the requested PID and/or EAA data, the name of the requesting Relying Party, and any related policy. The User decides whether to present any non-mandatory PID and/or EAA data (Selective Disclosure). The User provides consent to proceed or cancels the operation;
 - The User authorizes the operation using the unlock method previously set;
@@ -249,8 +250,8 @@ In case of errors using the Wallet Instance, the Wallet Provider MUST guarantee
 **Cross-Device Mode**
 
 - The User clicks the Engagement Button provided on the Touchpoint of the Relying Party while accessing the service from a different device than the one where the Wallet Instance is installed;
-- The User accesses the desired Wallet Instance from the device where it is installed, using the unlock method previously set;
-- The User scans the QR Code provided by the Relying Party using their Wallet Instance;
+- The User selects the Wallet Solution to proceed with, through an interface that MUST follow the instructions and functionalities provided for the Selection Page described in the :ref:`functionalities:Authentication` section;
+- The User scans the QR Code provided by the Relying Party using their Wallet Instance or the camera on their device; the QR code interface MUST follow the instructions and functionalities provided for the QR Code Page described in the :ref:`functionalities:Authentication` section;
 - The User reviews the requested PID and/or EAA data, the name of the requesting Relying Party, and any related policy. The User decides whether to present any non-mandatory personal data (Selective Disclosure). The User provides consent to proceed or cancels the operation.
 - The User authorizes the operation using the unlock method previously set;
 - The User receives confirmation of the successful presentation within the Wallet Instance;
@@ -703,11 +704,17 @@ Issuance of Electronic Attestations of Attributes Errors
   * - Error type
     - Actor in charge
   * - The Wallet Instance and/or the PID are not active
-    - Wallet Provider
+    - Wallet Instance
   * - The service for obtaining an Electronic Attestation of Attributes is unavailable (e.g. technical errors)
     - Electronic Attestations of Attributes Provider, Authentic Source
   * - The User is unable to obtain a specific Electronic Attestation of Attributes in their Wallet Instance (e.g. no eligibility, invalid or expired physical version, etc.)
     - Authentic Source
+  * - The service for obtaining an Electronic Attestation of Attributes cannot be processed within the defined time interval 
+    - Electronic Attestations of Attributes Provider 
+  * - The service for obtaining an Electronic Attestation of Attributes cannot be completed synchronously. The User is requested to wait until the Attestation becomes available (deferred flow) 
+    - Electronic Attestations of Attributes Provider, Authentic Source 
+  * - The service for obtaining an Electronic Attestation of Attributes cannot be processed as the request exceeds the permitted limit (e.g. multiple Attestations requested at once) 
+    - Electronic Attestations of Attributes Provider 
 
 Presentation of Electronic Attestations Errors
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -719,7 +726,7 @@ Presentation of Electronic Attestations Errors
   * - Error type
     - Actor in charge
   * - The User does not hold the required Attributes contained in one or more Electronic Attestations within their Wallet Instance to access a specific service
-    - Wallet Provider
+    - Wallet Instance
   * - The Wallet Provider's services or the Relying Party's services are unresponsive (e.g. technical errors or lack of connection)
     - Wallet Provider, Relying Party
 
@@ -736,6 +743,8 @@ Management of Electronic Attestations Errors
     - Electronic Attestations of Attributes Provider
   * - The service for revocation of PID is unavailable (e.g. technical errors)
     - PID Provider
+  * - The service for erasing information sent to a Relying Party is unavailable (e.g. technical errors) 
+    - Relying Party 
 
 Deactivation of the Wallet Instance Errors
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

diff --git a/docs/it/brand-identity.rst b/docs/it/brand-identity.rst
@@ -19,9 +19,11 @@ Gli Attori Primari DEVONO utilizzare esclusivamente queste Risorse Ufficiali e D
 Naming 
 ------
 
-"Sistema IT-Wallet" (IT-Wallet System in inglese) o "IT-Wallet" in forma contratta è il nome ufficiale che DEVE essere utilizzato in contesti scritti o verbali, fisici o digitali. Di seguito i relativi requisiti per la corretta scrittura e pronuncia: 
+Il termine "Sistema IT-Wallet", così come definito dalla norma istitutiva, rappresenta la denominazione ufficiale che DOVREBBE essere utilizzata in contesti a carattere istituzionale, formale o giuridico per riferirsi al sistema.  
 
-- si DEVE rispettare l'uso delle maiuscole nel termine “IT” e nelle iniziali di “Wallet” e “Sistema”; 
+La declinazione contratta "IT-Wallet" rappresenta, invece, il Brand naming ufficiale che DEVE essere utilizzato in ogni contesto comunicativo e divulgativo, scritto o verbale, fisico o digitale, per riferirsi al "Sistema IT-Wallet".  Di seguito i relativi requisiti per la corretta scrittura e pronuncia: 
+
+- si DEVE rispettare l'uso delle maiuscole nel termine "IT" e nelle iniziali di "Wallet" e "Sistema"; 
 
 - si DEVE rispettare l'uso del trattino tra i termini “IT” e “Wallet”, senza l'uso di spaziature; 
 
@@ -31,7 +33,7 @@ Naming
 Identità Visiva
 ---------------
 
-Il Sistema IT-Wallet ha una propria Identità Visiva. I partecipanti dell'ecosistema DEVONO applicarla in modo che si distingua e allo stesso tempo dialoghi e coesista con l'Identità Visiva propria e delle proprie Soluzioni Tecniche. In particolare, tutti gli Attori Primari DEVONO utilizzare le Risorse Ufficiali relative all'Identità Visiva del Sistema IT-Wallet. Il loro utilizzo ha lo scopo di rappresentare la partecipazione al Sistema IT-Wallet senza sostituire l'Identità Visiva della propria Soluzione Tecnica. 
+Il Brand "IT-Wallet" ha una propria Identità Visiva. I partecipanti dell'ecosistema DEVONO applicarla in modo che si distingua e allo stesso tempo dialoghi e coesista con l'Identità Visiva propria e delle proprie Soluzioni Tecniche. In particolare, tutti gli Attori Primari DEVONO utilizzare le Risorse Ufficiali relative all'Identità Visiva del Sistema IT-Wallet. Il loro utilizzo ha lo scopo di rappresentare la partecipazione al Sistema IT-Wallet senza sostituire l'Identità Visiva della propria Soluzione Tecnica. 
 
 Logo 
 ^^^^
@@ -69,7 +71,7 @@ Di seguito i requisiti generali per il suo utilizzo, validi sia in riferimento a
 
 - il Trust Mark DEVE essere esposto esclusivamente dalle Soluzioni Tecniche che hanno concluso con successo il processo di certificazione; 
 
-- il Trust Mark DEVE essere quello presente all'interno delle Risorse Ufficiali e DEVE rispettare le tutte le relative specifiche di utilizzo fornite, per garantirne un'adeguata visibilità in tutte le fasi dell'Esperienza Utente; 
+- il Trust Mark DEVE essere quello presente all'interno delle Risorse Ufficiali e DEVE rispettare tutte le relative specifiche di utilizzo fornite, per garantirne un'adeguata visibilità in tutte le fasi dell'Esperienza Utente; 
 
 - il Trust Mark NON DEVE essere alterato, distorto, modificato o sostituito da loghi non ufficiali.