Update terminology to align with the UI text

doc/administration/geo/disaster_recovery/planned_failover.md

@@ -144,7 +144,7 @@ ensure these processes are close to 100% as possible during active use.
 On the **secondary** node:
 
 1. On the top bar, select **Menu > Admin**.
-1. On the left sidebar, select **Geo > Nodes**.
+1. On the left sidebar, select **Geo > Sites**.
    Replicated objects (shown in green) should be close to 100%,
    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
@@ -174,7 +174,7 @@ On the **primary** node:
 1. On the top bar, select **Menu > Admin**.
 1. On the left sidebar, select **Messages**.
 1. Add a message notifying users on the maintenance window.
-   You can check under **Geo > Nodes** to estimate how long it
+   You can check under **Geo > Sites** to estimate how long it
    takes to finish syncing.
 1. Select **Add broadcast message**.
 
@@ -206,7 +206,7 @@ GitLab 13.9 through GitLab 14.3 are affected by a bug in which the Geo secondary
       those with `geo` in the name to drop to 0.
       These queues contain work that has been submitted by your users; failing over
       before it is completed, causes the work to be lost.
-   1. On the left sidebar, select **Geo > Nodes** and wait for the
+   1. On the left sidebar, select **Geo > Sites** and wait for the
       following conditions to be true of the **secondary** node you are failing over to:
 
       - All replication meters reach 100% replicated, 0% failures.

doc/development/architecture.md

@@ -347,7 +347,7 @@ Component statuses are linked to configuration documentation for each component.
 | [Elasticsearch](#elasticsearch)                       | Improved search within GitLab                                        |       ⤓        |       ⚙        |      ⤓       |        ⤓         |     ✅      |   ⤓    |  ⚙ | EE Only |
 | [Gitaly](#gitaly)                                     | Git RPC service for handling all Git calls made by GitLab            |       ✅       |       ✅        |      ✅       |        ✅         |     ✅      |   ⚙    |  ✅  | CE & EE |
 | [GitLab Exporter](#gitlab-exporter)                   | Generates a variety of GitLab metrics                                |       ✅       |       ✅        |      ✅       |        ✅         |     ✅      |   ❌    |  ❌  | CE & EE |
-| [GitLab Geo Node](#gitlab-geo)                        | Geographically distributed GitLab nodes                              |       ⚙        |       ⚙      |        ❌      |        ❌         |     ✅      |   ❌    |  ⚙  | EE Only |
+| [GitLab Geo](#gitlab-geo)                        | Geographically distributed GitLab site                              |       ⚙        |       ⚙      |        ❌      |        ❌         |     ✅      |   ❌    |  ⚙  | EE Only |
 | [GitLab Pages](#gitlab-pages)                         | Hosts static websites                                                |       ⚙       |       ⚙        |      ❌       |        ❌         |     ✅      |   ⚙    |  ⚙  | CE & EE |
 | [GitLab agent](#gitlab-agent)              | Integrate Kubernetes clusters in a cloud-native way                  |       ⚙       |       ⚙        |      ⚙       |        ❌         |     ❌      |   ⤓    |  ⚙   | EE Only |
 | [GitLab self-monitoring: Alertmanager](#alertmanager) | Deduplicates, groups, and routes alerts from Prometheus              |       ⚙       |       ⚙        |      ✅       |        ⚙         |     ✅      |   ❌    |  ❌  | CE & EE |

doc/user/admin_area/geo_nodes.md

@@ -12,7 +12,7 @@ You can configure various settings for GitLab Geo sites. For more information, s
 On either the primary or secondary site:
 
 1. On the top bar, select **Menu > Admin**.
-1. On the left sidebar, select **Geo > Nodes**.
+1. On the left sidebar, select **Geo > Sites**.
 
 ## Common settings