rephrased and removed a few remarks

Author: AvijitkGupta

articles/cosmos-db/mongodb/vcore/background-indexing.md

@@ -8,7 +8,7 @@ ms.reviewer: gahllevy
 ms.service: cosmos-db
 ms.subservice: mongodb-vcore
 ms.topic: conceptual
-ms.date: 06/27/2024
+ms.date: 07/01/2024
 ---
 
 # Background indexing (Preview)
@@ -17,8 +17,6 @@ ms.date: 06/27/2024
 
 Background indexing is a technique that enables a database system to perform indexing operations on a collection without blocking other queries or updates. Azure Cosmos DB for Mongo vcore accepts the background indexing request and asynchronously performs it in background.
 
-Background indexing can be enabled using the property `enableIndexBuildBackground` set to `true`. All indexes would be created in background except the unique indexes, post enabling the property.
-
 If working with smaller tiers or workloads with higher I/O needs, it's recommended to predefine indexes on empty collections and avoid relying on background indexing.
 
 > [!NOTE]

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

@@ -2,20 +2,20 @@
 title: Scale or configure a cluster
 titleSuffix: Azure Cosmos DB for MongoDB vCore
 description: Scale an Azure Cosmos DB for MongoDB vCore cluster by changing the tier and disk size or change the configuration by enabling high availability.
-author: gahl-levy
-ms.author: gahllevy
-ms.reviewer: sidandrews
+author: avijitgupta
+ms.author: avijitgupta
+ms.reviewer: gahllevy
 ms.service: cosmos-db
 ms.subservice: mongodb-vcore
 ms.topic: how-to
-ms.date: 06/20/2024
+ms.date: 07/01/2024
 ---
 
 # Scaling and configuring Your Azure Cosmos DB for MongoDB vCore cluster
 
 [!INCLUDE[MongoDB vCore](~/reusable-content/ce-skilling/azure/includes/cosmos-db/includes/appliesto-mongodb-vcore.md)]
 
-Azure Cosmos DB for MongoDB vCore provides seamless scalability and high availability. This document serves as a quick guide for developers who want to learn how to scale and configure their clusters. When changes are made, they're performed live to the cluster without downtime.
+Azure Cosmos DB for MongoDB vCore provides seamless scalability and high availability. This document serves as a quick guide for developers who want to learn how to scale and configure their clusters. Changes to the cluster are performed live without downtime.
 
 ## Prerequisites
 
@@ -32,9 +32,9 @@ To change the configuration of your cluster, use the **Scale** section of the Az
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
-1. Navigate to the existing Azure Cosmos DB for MongoDB vCore cluster page.
+2. Navigate to the existing Azure Cosmos DB for MongoDB vCore cluster page.
 
-1. From the Azure Cosmos DB for MongoDB vCore cluster page, select the **Scale** navigation menu option.
+3. From the Azure Cosmos DB for MongoDB vCore cluster page, select the **Scale** navigation menu option.
 
    :::image type="content" source="media/how-to-scale-cluster/select-scale-option.png" lightbox="media/how-to-scale-cluster/select-scale-option.png" alt-text="Screenshot of the Scale option on the page for an Azure Cosmos DB for MongoDB vCore cluster.":::
 
@@ -48,8 +48,10 @@ The cluster tier you select influences the amount of vCores and RAM assigned to
 
     > [!NOTE]
     > This change is performed live to the cluster without downtime.
+    >
+    > Upgrade or downgrade from burstable tiers to memory optimized tier isn't supported at the moment.
 
-1. Select **Save** to persist your change.
+2. Select **Save** to persist your change.
 
 ## Increase disk size
 
@@ -62,7 +64,7 @@ You can increase the storage size to give your database more room to grow. For e
     > [!NOTE]
     > This change is performed live to the cluster without downtime. Also, storage size can only be increased, not decreased.
 
-1. Select **Save** to persist your change.
+2. Select **Save** to persist your change.
 
 ## Enable or disable high availability
 
@@ -72,7 +74,7 @@ You can enable or disable [high availability (HA)](./high-availability.md) to su
 
    :::image type="content" source="media/how-to-scale-cluster/configure-high-availability.png" alt-text="Screenshot of the high availability checkbox in the Scale page of a cluster.":::
 
-1. Select **Save** to persist your change.
+2. Select **Save** to persist your change.
 
 ## Next steps
 

articles/cosmos-db/mongodb/vcore/indexing.md

@@ -8,7 +8,7 @@ ms.reviewer: gahllevy
 ms.service: cosmos-db
 ms.subservice: mongodb-vcore
 ms.topic: conceptual
-ms.date: 06/27/2024
+ms.date: 07/01/2024
 ---
 
 # Manage indexing in Azure Cosmos DB for MongoDB vcore
@@ -69,7 +69,7 @@ One query can use multiple single field indexes where available.
 
 ## Compound indexes
 
-Compound indexes are required if your query needs the ability to **query or sort** data from two or more fields in each document in a collection.
+Compound indexes improve database performance by allowing efficient **querying and sorting** based on multiple fields within documents. This optimization reduces the need to scan entire collections, speeding up data retrieval and organization.
 
 The following command creates a compound index on the fields `author` and `launchDate` in opposite sort order.