diff --git a/Enabling-WebSocket-notifications.md b/Enabling-WebSocket-notifications.md
index aa428d7..ec99a0f 100644
--- a/Enabling-WebSocket-notifications.md
+++ b/Enabling-WebSocket-notifications.md
@@ -2,22 +2,27 @@ WebSocket notifications are used to inform the browser, desktop and Browser Exte
 
 Note that WebSocket notifications are not applicable to the mobile (Android/iOS) Bitwarden clients. These clients use the native push notification service instead ([FCM](https://firebase.google.com/docs/cloud-messaging) for Android, [APNs](https://developer.apple.com/go/?id=push-notifications) for iOS). These have to be configured separately using push credentials from Bitwarden's cloud service, also available since v1.29.0.
 
+<br>
+
 WebSocket's are enabled by default since v1.29.0 of Vaultwarden. Previous versions needed a reverse proxy because WebSockets were running on a different port than then default HTTPS port.<br>
 The old implementation is still available in v1.29.0 to not break during updates for now. But this will be removed in the future.<br>
 
-
 <br>
+
 If you do use a reverse proxy like nginx or Apache HTTPd, then you need to make sure you configure it correctly to pass through the WebSocket `Upgrade` and `Connection` headers. Some reverse proxies do this by default like Traefik for example.
 
-
 <br>
+
 The old `WEBSOCKET_ENABLED` and `WEBSOCKET_PORT` are not needed anymore since v1.29.0 of Vaultwarden and can be ignored.<br>
 In fact, if you use the native implementation setting `WEBSOCKET_ENABLED` back to the default `false` value will reduce resources used by Vaultwarden (though not that much).
 
 <br>
-Example configurations are included in [[Proxy examples|proxy-examples]].<br>
+
+Example configurations are included in [[Proxy examples|proxy-examples]].
+<br>
 **Note that some examples are not yet updated for the v1.29.0 version.**
 
+<br>
 
 ## Test the WebSockets connection