From 85931bedf98b760eaf202386bc70595c37e9f589 Mon Sep 17 00:00:00 2001
From: Jack Carter <128555021+SunsetDrifter@users.noreply.github.com>
Date: Thu, 24 Sep 2026 10:59:59 +0200
Subject: [PATCH] docs: explain why the old Signal route is removed after the
 switch

---
 .../maintenance/scaling/high-availability-from-installer.mdx    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/pages/selfhosted/maintenance/scaling/high-availability-from-installer.mdx b/src/pages/selfhosted/maintenance/scaling/high-availability-from-installer.mdx
index c7578b73..f292f850 100644
--- a/src/pages/selfhosted/maintenance/scaling/high-availability-from-installer.mdx
+++ b/src/pages/selfhosted/maintenance/scaling/high-availability-from-installer.mdx
@@ -329,7 +329,7 @@ Plan this step for a maintenance window. Peers learn the Signal URL when they lo
    Setting `signalUri` turns off the server's built-in Signal.
 2. Restart the server: `docker compose restart netbird-server`.
 3. On every device that was connected during the change, run `netbird down` and then `netbird up`. Include devices that are always on, such as routing peers, exit nodes and servers. Each one connects to `signal.example.com` straight away. Check with `netbird status`, which shows `Signal: Connected to https://signal.example.com:443`.
-4. Remove the `/signalexchange.SignalExchange/*` route from the `app.example.com` load balancer. Nothing serves it any more.
+4. Remove the `/signalexchange.SignalExchange/*` route from the `app.example.com` load balancer. It carried Signal only until this step.
 
 ## Step 6: Add node 2