diff --git a/doc/administration/geo/disaster_recovery/planned_failover.md b/doc/administration/geo/disaster_recovery/planned_failover.md
index 5c15523ac78e5da23effdcee14cefb52c36dcd2e..8b55bebb42bb804dfa40280f391d951d49e844b4 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
 
-   ![Replication status](../replication/img/geo_node_dashboard_v14_0.png)
+   ![Replication status](../replication/img/geo_dashboard_v14_0.png)
 
 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 14a6decc7deca592160f278a409453013fd0aed5..27990748071bbc1bdfadd17387ceb6a2e96e6328 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.
 
-   ![Replication status](../../replication/img/geo_node_dashboard_v14_0.png)
+   ![Replication status](../../replication/img/geo_dashboard_v14_0.png)
 
 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 c78cad52d3703c1dc662008e19db8f01243e249d..9d5e65cd1942bfc453ca6cb300b0fb3ec55871e3 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.
 
-![Replication status](../../replication/img/geo_node_dashboard_v14_0.png)
+![Replication status](../../replication/img/geo_dashboard_v14_0.png)
 
 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 fabca9ca8a3cb992b3390154cecc7a1bfa7491d8..2b6ca695db6beff2fb2680d228a7ed843bcd1186 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**.
-   ![Add secondary site](img/adding_a_secondary_node_v13_3.png)
+   ![Add secondary site](img/adding_a_secondary_v13_3.png)
 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.
 
-![Geo dashboard](img/geo_node_dashboard_v14_0.png)
+![Geo dashboard](img/geo_dashboard_v14_0.png)
 
 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 7031f15d3a83fef10467c726ce80b302818e5776..08c6a05ca99e55b522905de27c5d28de9a2f2dfa 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?
 
-![Geo health check](img/geo_node_health_v14_0.png)
+![Geo health check](img/geo_site_health_v14_0.png)
 
 For information on how to resolve common errors reported from the UI, see
 [Fixing Common Errors](#fixing-common-errors).