From 2293eda22a12ad5b5fff63290448fbb2e4936ee8 Mon Sep 17 00:00:00 2001
From: Peter Briggs <git@email.peter.briggs.seattle.wa.us>
Date: Mon, 29 Dec 2025 16:24:41 -0800
Subject: [PATCH] Improve Caddy 2 description in websockets.vue

Reword for clarity and remove duplicate sentence.
---
 frontend/src/page/help/websockets.vue | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/frontend/src/page/help/websockets.vue b/frontend/src/page/help/websockets.vue
index 64f376aa3..e922ad69c 100644
--- a/frontend/src/page/help/websockets.vue
+++ b/frontend/src/page/help/websockets.vue
@@ -89,8 +89,7 @@ example.com {
           <v-card color="secondary-light">
             <v-card-text>
               <p>
-                WebSocket proxying automatically works in Caddy 2. There is no need to enable this as necessary for Caddy 1, Apache, and NGINX. In addition,
-                Caddy 2 may automatically create and update Let's Encrypt HTTPS certificates.
+                WebSocket proxying works out of the box in Caddy 2. There is no need to enable anything in your config, unlike other reverse proxies.
               </p>
               <p>Example configuration:</p>
               <pre>