From 36dc049d78fad373a52ae142af3bd2d14f822872 Mon Sep 17 00:00:00 2001
From: fenggwsx <49786884+fenggwsx@users.noreply.github.com>
Date: Sat, 11 Jan 2025 14:59:02 +0800
Subject: [PATCH] WEBSOCKET_ENABLED was renamed to ENABLE_WEBSOCKET after
 v1.29.0

---
 Enabling-WebSocket-notifications.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Enabling-WebSocket-notifications.md b/Enabling-WebSocket-notifications.md
index a42d72d..02c4fda 100644
--- a/Enabling-WebSocket-notifications.md
+++ b/Enabling-WebSocket-notifications.md
@@ -13,8 +13,8 @@ If you do use a reverse proxy like nginx or Apache HTTPd, then you need to make
 
 <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).
+The old `WEBSOCKET_ENABLED` and `WEBSOCKET_PORT` have been deprecated since v1.29.0 of Vaultwarden and will be ignored.<br>
+After v1.29.0, you can disable Websocket notifications by setting `ENABLE_WEBSOCKET` to the `false` value, which will reduce resources used by Vaultwarden (though not that much).
 
 <br>