From 91cd15a21d28f7892b9944ec8d375d9a2bf0e07b Mon Sep 17 00:00:00 2001
From: Sunjung Park <spark@gitlab.com>
Date: Fri, 30 Jul 2021 12:10:41 +0000
Subject: [PATCH] Geo docs: Update file names with `Node`
---
.../geo/disaster_recovery/planned_failover.md | 2 +-
.../runbooks/planned_failover_multi_node.md | 2 +-
.../runbooks/planned_failover_single_node.md | 2 +-
doc/administration/geo/replication/configuration.md | 4 ++--
..._node_v13_3.png => adding_a_secondary_v13_3.png} | Bin
..._dashboard_v14_0.png => geo_dashboard_v14_0.png} | Bin
...e_health_v14_0.png => geo_site_health_v14_0.png} | Bin
.../geo/replication/troubleshooting.md | 2 +-
8 files changed, 6 insertions(+), 6 deletions(-)
rename doc/administration/geo/replication/img/{adding_a_secondary_node_v13_3.png => adding_a_secondary_v13_3.png} (100%)
rename doc/administration/geo/replication/img/{geo_node_dashboard_v14_0.png => geo_dashboard_v14_0.png} (100%)
rename doc/administration/geo/replication/img/{geo_node_health_v14_0.png => geo_site_health_v14_0.png} (100%)
diff --git a/doc/administration/geo/disaster_recovery/planned_failover.md b/doc/administration/geo/disaster_recovery/planned_failover.md
index 5c15523ac78e5..8b55bebb42bb8 100644
--- a/doc/administration/geo/disaster_recovery/planned_failover.md
+++ b/doc/administration/geo/disaster_recovery/planned_failover.md
@@ -118,7 +118,7 @@ On the **secondary** node:
objects aren't yet replicated (shown in gray), consider giving the node more
time to complete
- 
+ 
If any objects are failing to replicate, this should be investigated before
scheduling the maintenance window. Following a planned failover, anything that
diff --git a/doc/administration/geo/disaster_recovery/runbooks/planned_failover_multi_node.md b/doc/administration/geo/disaster_recovery/runbooks/planned_failover_multi_node.md
index 14a6decc7deca..27990748071bb 100644
--- a/doc/administration/geo/disaster_recovery/runbooks/planned_failover_multi_node.md
+++ b/doc/administration/geo/disaster_recovery/runbooks/planned_failover_multi_node.md
@@ -72,7 +72,7 @@ On the **secondary** node:
objects aren't yet replicated (shown in gray), consider giving the node more
time to complete.
- 
+ 
If any objects are failing to replicate, this should be investigated before
scheduling the maintenance window. After a planned failover, anything that
diff --git a/doc/administration/geo/disaster_recovery/runbooks/planned_failover_single_node.md b/doc/administration/geo/disaster_recovery/runbooks/planned_failover_single_node.md
index c78cad52d3703..9d5e65cd1942b 100644
--- a/doc/administration/geo/disaster_recovery/runbooks/planned_failover_single_node.md
+++ b/doc/administration/geo/disaster_recovery/runbooks/planned_failover_single_node.md
@@ -57,7 +57,7 @@ and there should be no failures (shown in red). If a large proportion of
objects aren't yet replicated (shown in gray), consider giving the node more
time to complete.
-
+
If any objects are failing to replicate, this should be investigated before
scheduling the maintenance window. After a planned failover, anything that
diff --git a/doc/administration/geo/replication/configuration.md b/doc/administration/geo/replication/configuration.md
index fabca9ca8a3cb..2b6ca695db6be 100644
--- a/doc/administration/geo/replication/configuration.md
+++ b/doc/administration/geo/replication/configuration.md
@@ -199,7 +199,7 @@ keys must be manually replicated to the **secondary** site.
1. On the top bar, select **Menu >** **{admin}** **Admin**.
1. On the left sidebar, select **Geo > Sites**.
1. Select **New site**.
- 
+ 
1. Fill in **Name** with the `gitlab_rails['geo_node_name']` in
`/etc/gitlab/gitlab.rb`. These values must always match *exactly*, character
for character.
@@ -273,7 +273,7 @@ The initial replication, or 'backfill', is probably still in progress. You
can monitor the synchronization process on each Geo site from the **primary**
site's **Geo Sites** dashboard in your browser.
-
+
If your installation isn't working properly, check the
[troubleshooting document](troubleshooting.md).
diff --git a/doc/administration/geo/replication/img/adding_a_secondary_node_v13_3.png b/doc/administration/geo/replication/img/adding_a_secondary_v13_3.png
similarity index 100%
rename from doc/administration/geo/replication/img/adding_a_secondary_node_v13_3.png
rename to doc/administration/geo/replication/img/adding_a_secondary_v13_3.png
diff --git a/doc/administration/geo/replication/img/geo_node_dashboard_v14_0.png b/doc/administration/geo/replication/img/geo_dashboard_v14_0.png
similarity index 100%
rename from doc/administration/geo/replication/img/geo_node_dashboard_v14_0.png
rename to doc/administration/geo/replication/img/geo_dashboard_v14_0.png
diff --git a/doc/administration/geo/replication/img/geo_node_health_v14_0.png b/doc/administration/geo/replication/img/geo_site_health_v14_0.png
similarity index 100%
rename from doc/administration/geo/replication/img/geo_node_health_v14_0.png
rename to doc/administration/geo/replication/img/geo_site_health_v14_0.png
diff --git a/doc/administration/geo/replication/troubleshooting.md b/doc/administration/geo/replication/troubleshooting.md
index 7031f15d3a83f..08c6a05ca99e5 100644
--- a/doc/administration/geo/replication/troubleshooting.md
+++ b/doc/administration/geo/replication/troubleshooting.md
@@ -39,7 +39,7 @@ to help identify if something is wrong:
- Is the node's secondary tracking database connected?
- Is the node's secondary tracking database up-to-date?
-
+
For information on how to resolve common errors reported from the UI, see
[Fixing Common Errors](#fixing-common-errors).
--
GitLab