From 1c32ee76130e358403de838898daa9f31e4863e9 Mon Sep 17 00:00:00 2001
From: Pixelguin <11445611+Pixelguin@users.noreply.github.com>
Date: Mon, 5 Jan 2026 08:36:56 -0800
Subject: [PATCH] Clarify wording

---
 docs/troubleshooting.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md
index 4b45a939..7cdd4cda 100644
--- a/docs/troubleshooting.md
+++ b/docs/troubleshooting.md
@@ -136,7 +136,8 @@ Sorry, there is no way to debug or get the logs from the iOS app (yet), outside
 
 If all of your topics are showing as "Reconnecting" and notifications are taking a long time (30+ minutes) to come in, or if you're only getting new pushes with a manual refresh, double-check your configuration:
 
-* If ntfy is behind a reverse proxy, make sure `behind_proxy` is enabled.
-* If ntfy is behind Nginx, make sure WebSockets are enabled.
-* Make sure you have granted permission to access all of your topics, either to a logged-in user account or to `everyone`. All subscribed topics are joined into a single WebSocket/JSON, so a single topic that receives `403 Forbidden` will prevent the entire request from going through.
+* If ntfy is behind a reverse proxy (such as Nginx):
+  * Make sure `behind_proxy` is enabled in ntfy's config.
+  * Make sure WebSockets are enabled in the reverse proxy config.
+* Make sure you have granted permission to access all of your topics, either to a logged-in user account or to `everyone`. All subscribed topics are joined into a single WebSocket/JSON request, so a single topic that receives `403 Forbidden` will prevent the entire request from going through.
   * In particular, double-check that `everyone` has permission to write to `up*` and your user has permission to read `up*` if you are using UnifiedPush.