From cab11c0dc54eff17f62a00de93cb1203d85792cc Mon Sep 17 00:00:00 2001
From: Jack Carter <128555021+SunsetDrifter@users.noreply.github.com>
Date: Wed, 23 Sep 2026 18:21:50 +0200
Subject: [PATCH] docs: use one term for the shared PostgreSQL in the
 comparison table

---
 .../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 c6e26d3f..72ac530b 100644
--- a/src/pages/selfhosted/maintenance/scaling/high-availability-from-installer.mdx
+++ b/src/pages/selfhosted/maintenance/scaling/high-availability-from-installer.mdx
@@ -22,7 +22,7 @@ The table compares what the installer set up on one host with what you have at t
 | Dashboard | One container on node 1 | One on every node |
 | TLS and routing | Traefik on node 1 | Your load balancer, in front of every node |
 | PostgreSQL | A container on node 1 | A highly available PostgreSQL service you prepare before you begin |
-| Login data (embedded identity provider) | An SQLite file on node 1 | The same PostgreSQL endpoint |
+| Login data (embedded identity provider) | An SQLite file on node 1 | The same PostgreSQL service |
 | Signal | Built into the server | A Signal pool behind the load balancer, at the same URL |
 | Relay | Built into the server | Separate relay instances, one address each |
 | Redis and NATS | None: one server keeps its cache and messaging in memory | Redis and a three-node NATS cluster you set up before you begin, shared by every node |