From 98803b43069afc115c6adff192bac503df14849d Mon Sep 17 00:00:00 2001
From: Stefan Melmuk <509385+stefan0xC@users.noreply.github.com>
Date: Tue, 22 Aug 2023 11:37:18 +0200
Subject: [PATCH] Updated Enabling Mobile Client push notification (markdown)

---
 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 f9360b2..41460a2 100644
--- a/Enabling-Mobile-Client-push-notification.md
+++ b/Enabling-Mobile-Client-push-notification.md
@@ -24,4 +24,4 @@ docker compose up -d vaultwarden
 :warning: Unless you're using a freshly installed Bitwarden app, push notifications **will not work** with already connected clients. 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 the Bitwarden's Azure Notification Hub](https://contributing.bitwarden.com/architecture/deep-dives/push-notifications/mobile/#self-hosted-implementation).  
 :bulb: Push notifications will also only work on Bitwarden apps installed from the official mobile stores (App Store, Google Play Store) or when using alternative clients for the Google Play Store (such as Aurora Store). Push notifications **will not work** using Bitwarden clients installed from [F-Droid](https://mobileapp.bitwarden.com/fdroid/), NeoStore or other alternative stores. Those apps have been built without support for Firebase Messaging.
 
-5. Test if mobile push notifications work, for example by renaming a folder in your personal vault and see if it changes after a few seconds in your mobile app.
\ No newline at end of file
+5. Test if mobile push notifications work, for example by renaming a folder in the web vault and see if it changes after a few seconds in your mobile app.
\ No newline at end of file