Updating merge cancellation behavior

Author: deborahc

articles/cosmos-db/merge.md

@@ -183,7 +183,7 @@ az cosmosdb mongodb collection merge \
 
 Partition merge is a long-running operation and there's no SLA on how long it takes to complete. The time depends on the amount of data in the container and the number of physical partitions. It's recommended to allow at least 5-6 hours for merge to complete.
 
-While partition merge is running on your container, it isn't possible to change any container settings (TTL, indexing policy, unique keys, etc.), with the exception of the provisioned RU/s setting. Wait until the merge operation completes before changing your container settings. If you increase your RU/s while a merge is running, the merge operation will be cancelled and your container's RU/s will be updated with your new value. If you decrease your RU/s while a merge is running, the RU/s will be immediately changed 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.
+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 cancelled. If you increase your RU/s while a merge is running, the ongoing merge operation will be cancelled 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** and filtering for the events **Merge the physical partitions of a MongoDB collection** or **Merge the physical partitions of a SQL container**.