From d850b700cd4c28d9fd19c71e4c087fb55636323b Mon Sep 17 00:00:00 2001
From: Manuel Grabowski <mgrabowski@gitlab.com>
Date: Mon, 29 Jan 2024 09:02:37 +0000
Subject: [PATCH] Clarify general Geo upgrade note

---
 .../geo/replication/upgrading_the_geo_sites.md               | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/doc/administration/geo/replication/upgrading_the_geo_sites.md b/doc/administration/geo/replication/upgrading_the_geo_sites.md
index 20d140d4da8c..de30b85f4a7d 100644
--- a/doc/administration/geo/replication/upgrading_the_geo_sites.md
+++ b/doc/administration/geo/replication/upgrading_the_geo_sites.md
@@ -26,9 +26,8 @@ Upgrading Geo sites involves performing:
 ## General upgrade steps
 
 NOTE:
-These general upgrade steps are not intended for multi-site deployments,
-and cause downtime. If you want to avoid downtime, consider using
-[zero downtime upgrades](../../../update/zero_downtime.md#multi-node--ha-deployment-with-geo).
+These general upgrade steps require downtime in a multi-node setup.
+If you want to avoid downtime, consider using [zero downtime upgrades](../../../update/zero_downtime.md#multi-node--ha-deployment-with-geo).
 
 To upgrade the Geo sites when a new GitLab version is released, upgrade **primary**
 and all **secondary** sites:
-- 
GitLab