Various fixes.

Author: niklarin

articles/cosmos-db/mongodb/vcore/cross-region-replication.md

@@ -9,7 +9,7 @@ ms.subservice: mongodb-vcore
 ms.custom:
   - build-2024
 ms.topic: concept-article
-ms.date: 05/09/2024
+ms.date: 05/20/2024
 #Customer Intent: As a database adminstrator, I want to configure cross-region replication, so that I can have disaster recovery plans in the event of a regional outage.
 ---
 
@@ -43,15 +43,15 @@ When you create a replica by enabling cross-region replication, it doesn't inher
 
 The replica inherits the admin account from the primary cluster. User accounts need to be managed on the primary cluster. You can connect to the primary cluster and its replica cluster using the same user accounts.
 
-When cross-region replication is enabled, applications can use the replica cluster connection string to perform reads from the cluster replica. The primary cluster is available for read and write operations using a read-write connection string. The global read-write connection string is updated as a part of replica promotion process to point to the current read-write cluster.
+When cross-region replication is enabled, applications can use the replica cluster connection string to perform reads from the cluster replica. The primary cluster is available for read and write operations using its own connection string.
 
 ## Replica cluster promotion
 
 If a region outage occurs, you can perform disaster recovery operation by promoting your cluster replica in another region to become available for writes. During replica promotion operation, these steps are happening:
 
 1. Writes on the replica in region B are enabled in addition to reads. The former replica becomes a new read-write cluster.
-1. The global read-write string now points to the promoted cluster in region B.
-1. The cluster in region A is set to read-only.
+1. The promoted replica cluster accepts writes using its connection string.
+1. The cluster in region A is set to read-only and keeps its connection string.
 
 > [!IMPORTANT]
 > Because replication is asynchronous, some data from cluster in region A might not be replicated to region B when cluster replica in region B is promoted. If this is the case, promotion would result in the un-replicated data not present on both clusters.

articles/cosmos-db/mongodb/vcore/how-to-cluster-replica.md

@@ -9,7 +9,7 @@ ms.subservice: mongodb-vcore
 ms.custom:
   - build-2024
 ms.topic: how-to
-ms.date: 05/09/2024
+ms.date: 05/20/2024
 #Customer Intent: As a database adminstrator, I want to configure cross-region replication, so that I can have disaster recovery plans in the event of a regional outage.
 ---
 
@@ -52,7 +52,7 @@ To enable cross-region replication on a new cluster *at any time after cluster c
 1. Once cluster is created, on the cluster sidebar, under **Settings**, select **Global distribution (preview)**.
 1. Select **Add new read replica**.
 1. Provide a replica cluster name in the **Read replica name** field. 
-1. Select a region in the **Read replica region**. This is the Azure region where replica cluster will be hosted.
+1. Select a region in the **Read replica region**. The replica cluster is hosted in the selected Azure region.
 1. Verify your selection and select the **Save** button to confirm replica creation.
 
 ## Promote a replica
@@ -90,15 +90,24 @@ If you need to delete the primary and replica clusters, you would need to delete
 
 ## Use connection strings
 
-You can connect to the cluster replica as you would to a regular read-write cluster. When global distribution is enabled on the cluster, you can use global read-write connection string for reads and writes. This global read-write connection string would always point to the current read-write cluster.
+You can connect to the cluster replica as you would to a regular read-write cluster. 
 Follow these steps to [get the connection strings for different cases](./cross-region-replication.md#read-operations-on-cluster-replicas-and-connection-strings):
 
 1. Select the primary cluster or its cluster replica in the portal.
 1. On the cluster sidebar, under **Settings**, select **Connection strings**.
-1. On the primary cluster, copy the global read-write connection string for connections to the current read-write cluster. 
-1. Copy the connection string for currently selected cluster to connect to that cluster as you would with a regular read-write cluster.
+1. Copy the connection string for currently selected cluster to connect to that cluster.
+
+Connection strings are preserved after [the cluster replica promotion](./cross-region-replication.md#replica-cluster-promotion). You can continue to use either string for read opertions. You need to change connection string to point to the promoted replica cluster to continue writes to the database after promotino is completed.
+
+## Cross-region replication limits and limitations
+The following section describes various limits in the cross-region replication feature.
 
-Connection strings are preserved after [the cluster replica promotion](./cross-region-replication.md#replica-cluster-promotion).
+- Cross-region replication is not supported in [the Free tier](./free-tier.md).
+- [Burstable compute](./burstable-tier.md) is not supported on replica clusters.
+- Cross-region replication is supported only on clusters with one shard.
+- Compute, storage, and shard count configuration is the same on the primary and replica clusters and can't be changed.
+- High availability is not supported on replica clusters.
+- Replica of a replica cluster is not supported.
 
 ## Related content