When an email mentions an update prompt, the reader should move from the message to a known Ledger Wallet or version page rather than treating the email as the full instruction. The check is simple: entry source, version page, device screen, then a short local record.
Start from the entry source, not the message wording
Record the sender context and the page opened, then move to the expected Ledger Wallet entry if an update is actually needed. The update sequence can be compared with the firmware and app update order guide.
Check the version page before the device prompt
The version page should explain what is being updated and why the device is involved. If the reader is reviewing firmware order, the firmware update guide gives a current-page reference.
Use the hardware screen to confirm the task
The device screen should match the update page or app state. If the screen asks for a different action, pause and return to the page check. Device review boundaries are covered in the Secure Element overview.
Record the update path without sensitive material
The final note should list entry source, version page, device screen, and whether the action continued. It should not include recovery phrase words, PINs, or screenshots of private setup details.
