Geo docs: Update file names with `Node`

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

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

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

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).

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).