Apply suggestions from code review

Co-authored-by: Sidney Andrews <[email protected]>

Author: nayakshweta

articles/cosmos-db/import-data.md

@@ -62,8 +62,7 @@ While the import tool includes a graphical user interface (dtui.exe), it can als
 
 > [!NOTE]
 > We recommend using [container copy jobs](intra-account-container-copy.md) for copying data within the same Azure Cosmos DB account.
-
-> [!NOTE]
+> 
 > You should only use the Azure Cosmos DB migration tool for small migrations. For large migrations, view our [guide for ingesting data](migration-choices.md).
 
 ## <a id="Install"></a>Installation

articles/cosmos-db/partitioning-overview.md

@@ -88,7 +88,7 @@ A partition key has two components: **partition key path** and the **partition k
 
 To learn about the limits on throughput, storage, and length of the partition key, see the [Azure Cosmos DB service quotas](concepts-limits.md) article.
 
-Selecting your partition key is a simple but important design choice in Azure Cosmos DB. Once you select your partition key, it is not possible to change it in-place. If you need to change your partition key, you should move your data to a new container with your new desired partition key. ( [Container copy jobs](intra-account-container-copy.md) for NoSQL and Cassandra APIs help with this process. )
+Selecting your partition key is a simple but important design choice in Azure Cosmos DB. Once you select your partition key, it is not possible to change it in-place. If you need to change your partition key, you should move your data to a new container with your new desired partition key. ([Container copy jobs](intra-account-container-copy.md) for NoSQL and Cassandra APIs help with this process.)
 
 For **all** containers, your partition key should:
 

articles/cosmos-db/set-throughput.md

@@ -85,7 +85,7 @@ You can combine the two models. Provisioning throughput on both the database and
 * The container named *B* is guaranteed to get the *"P"* RUs throughput all the time. It's backed by SLAs.
 
 > [!NOTE]
-> A container with provisioned throughput cannot be converted to shared database container. Conversely a shared database container cannot be converted to have a dedicated throughput. You will need to move the data to a container with the desired throughput setting. ( [Container copy jobs](intra-account-container-copy.md) for NoSQL and Cassandra APIs help with this process. )
+> A container with provisioned throughput cannot be converted to shared database container. Conversely a shared database container cannot be converted to have a dedicated throughput. You will need to move the data to a container with the desired throughput setting. ([Container copy jobs](intra-account-container-copy.md) for NoSQL and Cassandra APIs help with this process.)
 
 ## Update throughput on a database or a container