Apply suggestions from code review

Author: NataliaIvakina

modules/ROOT/content-nav.adoc

@@ -168,8 +168,8 @@
 *** xref:clustering/monitoring/endpoints.adoc[]
 *** xref:clustering/monitoring/status-check.adoc[]
 ** Resilient cluster deployment
-*** xref:clustering/multi-region-deployment/multi-data-center-routing.adoc[]
 *** xref:clustering/multi-region-deployment/geo-redundant-deployment.adoc[]
+*** xref:clustering/multi-region-deployment/multi-data-center-routing.adoc[]
 *** xref:clustering/multi-region-deployment/disaster-recovery.adoc[]
 //** xref:clustering/internals.adoc[]
 ** xref:clustering/settings.adoc[]

modules/ROOT/pages/clustering/index.adoc

@@ -14,7 +14,7 @@ This chapter describes the following:
 ** xref:clustering/setup/discovery.adoc[Cluster server discovery] -- How servers in a cluster discover each other and form a cluster.
 ** xref:clustering/setup/routing.adoc[Leadership, routing and load balancing] -- Election of leaders, routing and load balancing.
 ** xref:clustering/setup/encryption.adoc[Intra-cluster encryption] -- How to secure the cluster communication.
-* xref:clustering/servers.adoc[Managing servers in a cluster] -- How to manage manage the servers in a cluster.
+* xref:clustering/servers.adoc[Managing servers in a cluster] -- How to manage the servers in a cluster.
 * xref:clustering/unbind.adoc[Unbind a server] -- How to remove and archive the cluster state of a cluster server so that it can rebind to a cluster.
 * xref:clustering/databases.adoc[Managing databases in a cluster] -- How to manage the databases in a cluster.
 * Monitoring -- Monitoring of a cluster.
@@ -23,8 +23,8 @@ This chapter describes the following:
 ** xref:clustering/monitoring/endpoints.adoc[Monitor cluster endpoints for status information] -- The endpoints and semantics of endpoints used to monitor the health of the cluster.
 ** xref:clustering/monitoring/status-check.adoc[Monitor replication status] -- The procedure to monitor which members of a clustered database are up-to-date and can participate in a successful replication.
 * Resilient cluster deployment -- Recommendations and guidance on how to set up a resilient cluster which ensures your database stays available, fast, and recoverable even under failures.
-** xref:clustering/multi-region-deployment/multi-data-center-routing.adoc[Multi-data center routing] -- Clusters on multi-data centers.
 ** xref:clustering/multi-region-deployment/geo-redundant-deployment.adoc[] -- Recommended patterns of cluster deployment across multiple cloud regions / data centers.
+** xref:clustering/multi-region-deployment/multi-data-center-routing.adoc[Multi-data center routing] -- Clusters on multi-data centers.
 ** xref:clustering/multi-region-deployment/disaster-recovery.adoc[Disaster recovery] -- How to recover a cluster in the event of a disaster.
 * xref:clustering/settings.adoc[Settings reference] -- A summary of the most important cluster settings.
 * xref:clustering/server-syntax.adoc[Server commands reference] -- Reference of Cypher administrative commands to add and manage servers.

modules/ROOT/pages/clustering/multi-region-deployment/geo-redundant-deployment.adoc

@@ -147,7 +147,7 @@ In that case a failure of a member in DC1 means the database is write-unavailabl
 If leadership shifts to DC2, this makes all writes slow.
 
 Finally, there is no guarantee against data loss if DC1 goes down.
-Beacuse the primary member in DC2 may not be up to date with writes, even in append.
+Because the primary member in DC2 may not be up to date with writes, even in append.