Implement @abhijitpai change requests

Author: seesharprun

articles/cosmos-db/how-to-container-copy.md

@@ -9,48 +9,42 @@ ms.author: shwetn
 ---
 
 # Create and manage intra-account container copy jobs in Azure Cosmos DB (Preview)
+[!INCLUDE[appliesto-sql-cassandra-api](includes/appliesto-sql-cassandra-api.md)]
 
-[!INCLUDE[appliesto-sql-api](includes/appliesto-sql-api.md)]
-[!INCLUDE[appliesto-cassandra-api](includes/appliesto-cassandra-api.md)]
+[Container copy jobs](intra-account-container-copy.md) creates offline copies of collections within an Azure Cosmos DB account.
 
-[Container copy jobs](./intra-account-container-copy.md) allow to create offline copies of collections within an Azure Cosmos DB account
+This article describes how to create, monitor, and manage intra-account container copy jobs using Azure CLI commands.
 
-This article describes you to create, monitor and manage intra-account container copy jobs using Azure CLI commands.
+## Set shell variables
+
+First, set all of the variables that each individual script will use.
+
+```azurecli-interactive
+$accountName = "<cosmos-account-name>"
+$resourceGroup = "<resource-group-name>"
+$jobName = ""
+$sourceDatabase = ""
+$sourceContainer = ""
+$destinationDatabase = ""
+$destinationContainer = ""
+```
 
 ## Create an intra-account container copy job for SQL API account
 
 Create a job to copy a container within an Azure Cosmos DB SQL API account:
 
 ```azurecli-interactive
-
-$cosmosdbaccountname = "cosmosDBAccountName"
-$rg = "resourceGroupName"
-$copyJobName = ""
-$sourceKeySpace = ""
-$sourceTable = ""
-$destinationKeySpace = ""
-$destinationTable = ""
-
-az cosmosdb dts copy -g $rg --job-name $jobName --account-name $cosmosdbaccountname \
-    --source-sql-container database=$sourceContainer container=$sourceDb \
-    --dest-sql-container database=$destinationContainer container=$destinationDb
+az cosmosdb dts copy --resource-group $resourceGroup --job-name $jobName --account-name $accountName \
+    --source-sql-container database=$sourceDatabase container=$sourceContainer \
+    --dest-sql-container database=$destinationDatabase container=$destinationContainer
 ```
 
 ## Create intra-account container copy job for Cassandra API account
 
 Create a job to copy a container within an Azure Cosmos DB Cassandra API account:
 
 ```azurecli-interactive
-
-$cosmosdbaccountname = "cosmosDBAccountName"
-$rg = "resourceGroupName"
-$copyJobName = ""
-$sourceKeySpace = ""
-$sourceTable = ""
-$destinationKeySpace = ""
-$destinationTable = ""
-
-az cosmosdb dts copy -g $rg --job-name $jobName --account-name $cosmosdbaccountname \
+az cosmosdb dts copy --resource-group $resourceGroup --job-name $jobName --account-name $accountName \
     --source-cassandra-table keyspace=$sourceKeySpace table=$sourceTable \
     --dest-cassandra-table keyspace=$destinationKeySpace table=$destinationTable
 ```
@@ -60,29 +54,33 @@ az cosmosdb dts copy -g $rg --job-name $jobName --account-name $cosmosdbaccountn
 View the progress and status of a copy job:
 
 ```azurecli-interactive
-az cosmosdb dts show --account-name  $cosmosdbaccountname -g $rg --job-name $copyJobname
+az cosmosdb dts show --account-name $accountName --resource-group $resourceGroup --job-name $jobName
 ```
 
 ## List all the container copy jobs created in an account
 
 To list all the container copy jobs created in an account:
 
 ```azurecli-interactive
-az cosmosdb dts list --account-name  $cosmosdbaccountname -g $rg
+az cosmosdb dts list --account-name $accountName --resource-group $resourceGroup
 ```
 
 ## Pause a container copy job
 
 In order to pause an ongoing container copy job, you may use the command:
 
 ```azurecli-interactive
-az cosmosdb dts pause --account-name  $cosmosdbaccountname -g $rg --job-name $copyJobname
+az cosmosdb dts pause --account-name $accountName --resource-group $resourceGroup --job-name $jobName
 ```
 
 ## Resume a container copy job
 
 In order to resume an ongoing container copy job, you may use the command:
 
 ```azurecli-interactive
-az cosmosdb dts resume --account-name  $cosmosdbaccountname -g $rg --job-name $copyJobname
-```
+az cosmosdb dts resume --account-name $accountName --resource-group $resourceGroup --job-name $jobName
+```
+
+## Next steps
+
+- For more information about intra-account container copy jobs, see [Container copy jobs](intra-account-container-copy.md).

articles/cosmos-db/includes/appliesto-sql-cassandra-api.md

@@ -0,0 +1 @@
+APPLIES TO: :::image type="icon" source="../media/applies-to/yes.png" border="false":::SQL API :::image type="icon" source="../media/applies-to/yes.png" border="false":::Cassandra API

articles/cosmos-db/intra-account-container-copy.md

@@ -9,22 +9,24 @@ ms.author: shwetn
 ---
 
 # Intra-account container copy jobs (Preview)
-
-[!INCLUDE[appliesto-sql-api](includes/appliesto-sql-api.md)]
-[!INCLUDE[appliesto-cassandra-api](includes/appliesto-cassandra-api.md)]
+[!INCLUDE[appliesto-sql-cassandra-api](includes/appliesto-sql-cassandra-api.md)]
 
 You can perform offline container copy within an Azure Cosmos DB account using container copy jobs.
 
-You may need to copy data within your Azure Cosmos DB account if you want to achieve either of these scenarios:
+You may need to copy data within your Azure Cosmos DB account if you want to achieve any of these scenarios:
 
 * Copy all items from one container to another.
-* Change the [granularity at which throughput is provisioned - from database to container](./set-throughput.md) and vice-versa.
-* Change the [partition key](./partitioning-overview.md#choose-partitionkey) of a container.
-* Update the [unique keys](./unique-keys.md) for a container.
+* Change the [granularity at which throughput is provisioned - from database to container](set-throughput.md) and vice-versa.
+* Change the [partition key](partitioning-overview.md#choose-partitionkey) of a container.
+* Update the [unique keys](unique-keys.md) for a container.
 * Rename a container/database.
 * Adopt new features that are only supported on new containers.
 
-Intra-account container copy jobs can be currently [created and managed using CLI commands](./how-to-copy-container.md).
+Intra-account container copy jobs can be currently [created and managed using CLI commands](how-to-container-copy.md).
+
+## Getting started
+
+To get started using container copy jobs, enroll in the preview by filing a support ticket in the [Azure portal](https://portal.azure.com). 
 
 ## How does intra-account container copy work?
 
@@ -37,24 +39,28 @@ Intra-account container copy jobs perform offline data copy using the source con
 * The platform may de-allocate the instances if they're idle for >15 mins.
 
 > [!NOTE]
-> We currently only support offline container copy. So, we strongly recommend to stop performing any operations on the source container prior to beginning the container copy. \
-> Item deletions and updates done on the source container after beginning the copy job would not be captured. Hence, continuing to perform operations on the source container while the container job is in progress may result in data missing on the target container.
+> We currently only support offline container copy. So, we strongly recommend to stop performing any operations on the source container prior to beginning the container copy.
+> Item deletions and updates done on the source container after beginning the copy job may not be captured. Hence, continuing to perform operations on the source container while the container job is in progress may result in data missing on the target container.
 
 ## Overview of steps needed to do a container copy
 
 1. Stop the operations on the source container by pausing the application instances or any clients connecting to it.
-2. [Create the container copy job](./how-to-copy-container.md).
-3. [Monitor the progress of the container copy job](./how-to-copy-container.md#monitor-the-progress-of-container-copy-job) and wait until it's completed.
+2. [Create the container copy job](how-to-container-copy.md).
+3. [Monitor the progress of the container copy job](how-to-container-copy.md#monitor-the-progress-of-a-container-copy-job) and wait until it's completed.
 4. Resume the operations by appropriately pointing the application or client to the source or target container copy as intended.
 
 ## Factors affecting the rate of container copy job
 
 The rate of container copy job progress is determined by these factors:
 
 * Source container/database throughput setting.
+
 * Target container/database throughput setting.
-* Server-side compute instances allocated to the Azure Cosmos DB account for the performing the data transfer.\
-The default is two 4-vCPU 16-GB server-side instances per account, available for free. You may opt to sign up for paid [larger SKUs](#large-skus-preview) preview.
+
+* Server-side compute instances allocated to the Azure Cosmos DB account for the performing the data transfer.
+
+    > [!IMPORTANT]
+    > The default SKU offers two 4-vCPU 16-GB server-side instances per account. You may opt to sign up for [larger SKUs](#large-skus-preview) in preview.
 
 ## FAQs
 
@@ -64,15 +70,15 @@ Container copy jobs are currently supported on best-effort basis. We don't provi
 
 ### Can I create multiple container copy jobs within an account?
 
-Yes, you can create multiple jobs within the same account. The jobs will run consecutively. You can [list all the jobs](./how-to-copy-container.md#list-all-the-container-copy-jobs-created-in-an-account) created within an account and monitor their progress.
+Yes, you can create multiple jobs within the same account. The jobs will run consecutively. You can [list all the jobs](how-to-container-copy.md#list-all-the-container-copy-jobs-created-in-an-account) created within an account and monitor their progress.
 
 ### Can I copy an entire database within the Azure Cosmos DB account?
 
 You'll have to create a job for each collection in the database.
 
 ### I have an Azure Cosmos DB account with multiple regions. In which region will the container copy job run?
 
-The container copy job will run in the write region. If there are accounts configured with multi-region writes, the job will run in the first region from the list.
+The container copy job will run in the write region. If there are accounts configured with multi-region writes, the job will run in one of the regions from the list.
 
 ### What happens to the container copy jobs when the account's write region changes?
 
@@ -82,11 +88,8 @@ The account's write region may change in the rare scenario of a region outage or
 
 If you want to run the container copy jobs faster, you may do so by adjusting one of the [factors that affect the rate of the copy job](#factors-affecting-the-rate-of-container-copy-job). In order to adjust the configuration of the server-side compute instances, you may sign up for "Large SKU support for container copy" preview.
 
-This preview will allow you to choose larger SKUs sizes for the server-side instances. You can also choose a node count of up to 5 for these instances.
-
-> [!NOTE]
-> Large SKU sizes are payable.
+This preview will allow you to choose larger a SKU size for the server-side instances. Large SKU sizes are billable at a higher rate. You can also choose a node count of up to 5 of these instances.
 
 ## Next Steps
 
-You can learn about [how to create, monitor and manage container copy jobs within Azure Cosmos DB account using CLI commands](./how-to-copy-container.md).
+- You can learn about [how to create, monitor and manage container copy jobs within Azure Cosmos DB account using CLI commands](how-to-container-copy.md).