From 282fdfcfc4d0d84fb41b7ce37e41db9527f1fd81 Mon Sep 17 00:00:00 2001
From: Nicolas Delahaie <91760731+Nicolas-Delahaie@users.noreply.github.com>
Date: Sun, 7 Sep 2025 19:10:27 +0200
Subject: [PATCH] Changing "Bitwarden mobile app" to "every clients"

---
 Enabling-Mobile-Client-push-notification.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Enabling-Mobile-Client-push-notification.md b/Enabling-Mobile-Client-push-notification.md
index 664b6a9..325281c 100644
--- a/Enabling-Mobile-Client-push-notification.md
+++ b/Enabling-Mobile-Client-push-notification.md
@@ -24,7 +24,7 @@ Since version `1.29.0` of Vaultwarden, you can activate Mobile Client push notif
 docker compose up -d vaultwarden
 ```
 
-4. Log out and log back in your Bitwarden mobile app so that the device re-registers its push token with the server.
+4. Log out and log back in to your Bitwarden clients so they can retrieve the push configuration from the server.
 
 > [!WARNING]
 > If you have already connected your Bitwarden app before [v1.30.2](https://github.com/dani-garcia/vaultwarden/releases/tag/1.30.2) push notifications **will not work** for your device (because the device token was never saved). You have to **clear the app data** of your mobile app (or **reinstall the app**) and connect your Vaultwarden account again to register the push token with [Bitwarden's Azure Notification Hub](https://contributing.bitwarden.com/architecture/deep-dives/push-notifications/mobile/#self-hosted-implementation).