diff --git a/docs/wallet/developer-mode.md b/docs/wallet/developer-mode.md
index 4a34e25..48c1a09 100644
--- a/docs/wallet/developer-mode.md
+++ b/docs/wallet/developer-mode.md
@@ -1,30 +1,34 @@
 # Developer Mode
 
-Updated the 14th of October 2024.
+Updated the 30th of October 2024.
 
-The developer mode allow any technical users to get internal information about the wallet data and logic. It modifies the display of verifiable credentials and it provides data of the wallet calls and responses.
+The developer mode allow any technical users to get internal information about the wallet data and logic. It modifies the display of verifiable credentials and it includes breakpoint in the code flow for debugging purposes.
 
-The developer mode can be removed from the settings menu of the wallet through the Wallet Provider Backend.
+The developer mode can be removed from the settings menu of the wallet through the wallet provider backend.
 
 Below are all the wallet features which are enhanced or modified in the developer mode.
 
-## Display raw data of verifiable credentials
+## Verifiable credentials in raw
 
 Verifiable credentials are displayed in their original form as json-ld or jwt. For jwt users have an access to the header and payload of the credentials. For sd-jwt vc, jwt are displayed with all disclosures decoded.
 
-## Display of the wallet instance attestation
+## Wallet instance attestation
 
-If the wallet is used with the wallet provider backend the developer mode gives access to the wallet instance attestation which is displayed on the main screen of the wallet.
+If the wallet is used with the wallet provider backend the developer mode gives access to the wallet instance attestation which is displayed on the main screen of the wallet in grey with a jwt format.
 
 ## Verifiable credentials status and validity details
 
-In case of signature failure or invalid status, the reasons of the problems are provided in details.
+In case of signature failure or invalid status, the reasons of the failure are provided in details.
 
-## Display Issuer configuration and protocol flow requests and responses data
+## Issuance flow
 
 After scanning an OIDC4VC QR code a popup proposes to users to:
 
-* display the QR code data and the OpeinID issuer metadata,
+* display:
+
+  * the credential offer,
+  * the credential issuer metadata (from /.well-known/openid-redential-issuer),
+  * the authorization server metadata (from /.well-known/oauth-autyhorization-server),
 * download this information as a text file,
 * skip to bypass.
 
@@ -33,6 +37,16 @@ Within the OIDC4VCI flow, the wallet proposes to display or download the data re
 - the token endpoint,
 - the credential endpoint.
 
+## Presentation flow
+
+After scanning an OIDC4VP or SIOPV2 QR code a popup proposes to users to:
+
+* display:
+  * the authorization request,
+  * the client metadata,
+* download this information as a text file,
+* skip to bypass.
+
 ## Display of errors details
 
 In case of an error response from issuers or verifiers, users have an access to the `error_description` data returned.
diff --git a/static/img/ssi_screen/altme_discover.png b/static/img/ssi_screen/altme_discover.png
index 8587628..fb0ccfe 100644
Binary files a/static/img/ssi_screen/altme_discover.png and b/static/img/ssi_screen/altme_discover.png differ