fixed comments

Author: vida-tonkova

articles/cosmos-db/media/monitor-activity-logs-elastic-operations/activity-log-scale-up-overview.png

@@ -244,7 +244,7 @@ Partition merge is a long-running operation and there's no SLA on how long it ta
 
 While partition merge is running on your container, if you change container settings (TTL, indexing policy, unique keys, etc.), the ongoing merge operation will be canceled. If you increase your RU/s while a merge is running, the ongoing merge operation will be canceled and your container's RU/s will be updated with your new value. Depending on the RU/s requested, your [scale-up may be instant or take longer](scaling-provisioned-throughput-best-practices.md#step-2-calculate-the-default-maximum-throughput). If you decrease your RU/s while a merge is running, the RU/s will be instantly updated to the new RU/s. The in-progress merge will continue, with the same target partition count based on the RU/s set at the time the merge was triggered. As a best practice, it is recommended to wait until the merge operation completes before changing your container or throughput settings. 
 
-You can track whether merge is still in progress by checking the [Activity Log](monitor-activity-logs-elastic-operations.md) and filtering for the events **Merge the physical partitions of a MongoDB collection** or **Merge the physical partitions of a SQL container**.
+You can track whether the merge is still in progress by checking the [Activity Log](monitor-activity-logs-elastic-operations.md) and filtering for the events **Merge the physical partitions of a MongoDB collection** or **Merge the physical partitions of a SQL container**.
 
 ## Limitations
 
@@ -291,7 +291,7 @@ Find the latest version of the supported SDK:
 | --- | --- | --- |
 | **.NET SDK v3** | *>= 3.27.0* | <https://www.nuget.org/packages/Microsoft.Azure.Cosmos> |
 | **Java SDK v4** | *>= 4.42.0* | <https://mvnrepository.com/artifact/com.azure/azure-cosmos> |
-| **Javascript SDK v4** | *>= 4.3.0* | <https://www.npmjs.com/package/@azure/cosmos> |
+| **JavaScript SDK v4** | *>= 4.3.0* | <https://www.npmjs.com/package/@azure/cosmos> |
 | **Python SDK v4** | *>= 4.14.2* | <https://pypi.org/project/azure-cosmos/> |
 
 > [!TIP]

articles/cosmos-db/media/monitor-activity-logs-elastic-operations/merge-in-progress-json.png

@@ -17,6 +17,8 @@ appliesto:
 
 # Activity logs for elastic (split/merge) operations
 
+This article explains how to use the Azure Activity Log to monitor partition split and merge operations in Azure Cosmos DB.
+
 ## Background
 
 In Azure Cosmos DB, each physical partition supports up to 10,000 RU/s of throughput. When you increase the provisioned throughput of a database or container beyond the capacity of the current physical partitions, Azure Cosmos DB must split those partitions to accommodate the extra throughput.
@@ -150,7 +152,7 @@ The Activity Log displays entries in the portal stacked top-down, with the most
 
 :::image type="content" source="media/monitor-activity-logs-elastic-operations/multi-round-split-activity-log.png" lightbox="media/monitor-activity-logs-elastic-operations/multi-round-split-activity-log.png" alt-text="Screenshot of the Activity Log showing multiple rounds of partition splits with Started and In Progress entries for each round.":::
 
-For this example, the Activity Log outputs results every 5 minutes. Round 1 of the split is surrounded by the blue box and shows a Started status, followed by 2 In Progress entries. Round 2 follows a similar pattern and is enclosed by the purple box.
+In this example view, Round 1 of the split is surrounded by the blue box and shows a Started status, followed by 2 In Progress entries. Round 2 follows a similar pattern and is enclosed by the purple box.
 
 :::image type="content" source="media/monitor-activity-logs-elastic-operations/multi-round-split-rounds.png" lightbox="media/monitor-activity-logs-elastic-operations/multi-round-split-rounds.png" alt-text="Screenshot of the Activity Log portal view showing Round 1 and Round 2 split entries highlighted in separate boxes.":::