diff --git a/Enabling-Mobile-Client-push-notification.md b/Enabling-Mobile-Client-push-notification.md
index 6b4de19..ff0c941 100644
--- a/Enabling-Mobile-Client-push-notification.md
+++ b/Enabling-Mobile-Client-push-notification.md
@@ -11,7 +11,8 @@ Since version `1.29.0` of Vaultwarden, you can activate Mobile Client push notif
       - PUSH_INSTALLATION_ID=
       - PUSH_INSTALLATION_KEY= 
 ```
-> :information_source: If you have requested an INSTALLATION ID and KEY for `bitwarden.eu (European Union)` in the previous step, you also have to set
+> [!NOTE] 
+> If you have requested an INSTALLATION ID and KEY for `bitwarden.eu (European Union)` in the previous step, you also have to set
 ```yaml
       - PUSH_RELAY_URI=https://push.bitwarden.eu
       - PUSH_IDENTITY_URI=https://identity.bitwarden.eu
@@ -24,15 +25,18 @@ docker compose up -d vaultwarden
 ```
 
 4. Connect your app to your Vaultwarden instance.  
-> :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).
+> [!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).
 
-> :bulb: Push notifications will also **only work** on Bitwarden apps obtained 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.
+> [!IMPORTANT]
+> Push notifications will also **only work** on Bitwarden apps obtained 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 the web vault and see if it changes after a few seconds in your mobile app.
 
 ### Switching from US to EU servers (or vice versa)
  
-> :warning: Make sure you use the latest version [![GitHub Release](https://img.shields.io/github/release/dani-garcia/vaultwarden.svg)](https://github.com/dani-garcia/vaultwarden/releases/latest) before doing that change.
+> [!WARNING]
+> Make sure you use the latest version [![GitHub Release](https://img.shields.io/github/release/dani-garcia/vaultwarden.svg)](https://github.com/dani-garcia/vaultwarden/releases/latest) before doing that change.
 
 To switch from one data region to the other you'll have to:
 1. deauthorize all sessions and also clear the app data on the mobile app