Merge pull request #101055 from SnehaGunda/master

Updating mongoDB pre-migration doc

Author: PRMerger10

articles/cosmos-db/cassandra-introduction.md

@@ -12,7 +12,7 @@ ms.reviewer: sngun
 
 # Introduction to the Azure Cosmos DB Cassandra API
 
-Azure Cosmos DB Cassandra API can be used as the data store for apps written for [Apache Cassandra](https://cassandra.apache.org/). This means that by using existing [Apache drivers](https://cassandra.apache.org/doc/latest/getting_started/drivers.html?highlight=driver) compliant with CQLv4, your existing Cassandra application can now communicate with the Azure Cosmos DB Cassandra API. In many cases, you can switch from using Apache Cassandra to using Azure Cosmos DB 's Cassandra API, by just changing a connection string. 
+Azure Cosmos DB Cassandra API can be used as the data store for apps written for [Apache Cassandra](http://cassandra.apache.org). This means that by using existing [Apache drivers](http://cassandra.apache.org/doc/latest/getting_started/drivers.html?highlight=driver) compliant with CQLv4, your existing Cassandra application can now communicate with the Azure Cosmos DB Cassandra API. In many cases, you can switch from using Apache Cassandra to using Azure Cosmos DB 's Cassandra API, by just changing a connection string. 
 
 The Cassandra API enables you to interact with data stored in Azure Cosmos DB using the Cassandra Query Language (CQL) , Cassandra-based tools (like cqlsh) and Cassandra client drivers that you’re already familiar with.
 

articles/cosmos-db/mongodb-compass.md

@@ -5,8 +5,8 @@ ms.service: cosmos-db
 ms.subservice: cosmosdb-mongo
 ms.topic: overview
 ms.date: 06/24/2019
-author: roaror
-ms.author: roaror
+author: LuisBosquez
+ms.author: lbosq
 ---
 
 # Use MongoDB Compass to connect to Azure Cosmos DB's API for MongoDB 

articles/cosmos-db/mongodb-post-migration.md

@@ -1,12 +1,12 @@
 ---
 title: Post-migration optimization steps with Azure Cosmos DB’s API for MongoDB 
 description: This doc provides the post-migration optimization techniques from MongoDB to Azure Cosmos DB's APi for Mongo DB.
-author: roaror
+author: LuisBosquez
 ms.service: cosmos-db
 ms.subservice: cosmosdb-mongo
 ms.topic: conceptual
 ms.date: 04/18/2019
-ms.author: roaror
+ms.author: lbosq
 
 ---
 

articles/cosmos-db/mongodb-pre-migration.md

@@ -19,15 +19,19 @@ Before you migrate your data from MongoDB (either on-premises or in the cloud) t
 4. [Pick an optimal partition key for your data](#partitioning)
 5. [Understand the indexing policy that you can set on your data](#indexing)
 
-If you have already completed the above pre-requisites for migration, you can [Migrate MongoDB data to Azure Cosmos DB's API for MongoDB using the Azure Database Migration Service](../dms/tutorial-mongodb-cosmos-db.md). Additionally, if you haven't created an account, you can browse any of the [Quickstarts](create-mongodb-dotnet.md).
+If you have already completed the above pre-requisites for migration, you can [Migrate MongoDB data to Azure Cosmos DB's API for MongoDB using the Azure Database Migration Service](../dms/tutorial-mongodb-cosmos-db.md). Additionally, if you haven't created an account, you can browse any of the [Quickstarts](create-mongodb-dotnet.md) that show the steps to create an account.
 
-## <a id="considerations"></a>Main considerations when using Azure Cosmos DB's API for MongoDB
+## <a id="considerations"></a>Considerations when using Azure Cosmos DB's API for MongoDB
 
 The following are specific characteristics about Azure Cosmos DB's API for MongoDB:
+
 - **Capacity model**: Database capacity on Azure Cosmos DB is based on a throughput-based model. This model is based on [Request Units per second](request-units.md), which is a unit that represents the number of database operations that can be executed against a collection on a per-second basis. This capacity can be allocated at [a database or collection level](set-throughput.md), and it can be provisioned on an allocation model, or using the [AutoPilot model](provision-throughput-autopilot.md).
-- **Request Units**: Every database operation has an associated Request Units (RUs) cost in Azure Cosmos DB. When executed, this is subtracted from the available request units level on a given second. If a request requires more RUs than currently allocated the two options are increasing the amount of RUs, or waiting until the next second starts, then retrying the operation.
+
+- **Request Units**: Every database operation has an associated Request Units (RUs) cost in Azure Cosmos DB. When executed, this is subtracted from the available request units level on a given second. If a request requires more RUs than the currently allocated RU/s there are two options to solve the issue - increase the amount of RUs, or wait until the next second starts and then retry the operation.
+
 - **Elastic capacity**: The capacity for a given collection or database can change at any time. This allows for the database to elastically adapt to the throughput requirements of your workload.
-- **Automatic sharding**: Azure Cosmos DB provides an automatic partitioning system that only requires a shard (or partitioning) key. The [automatic partitioning mechanism](partition-data.md) is shared across all Azure Cosmos DB APIs and it allows for seamless data and throughout scaling through horizontal distribution.
+
+- **Automatic sharding**: Azure Cosmos DB provides an automatic partitioning system that only requires a shard (or a partition key). The [automatic partitioning mechanism](partition-data.md) is shared across all the Azure Cosmos DB APIs and it allows for seamless data and throughout scaling through horizontal distribution.
 
 ## <a id="options"></a>Migration options for Azure Cosmos DB's API for MongoDB
 
@@ -49,7 +53,9 @@ You can use the [Azure Cosmos DB Capacity Calculator](https://cosmos.azure.com/c
 
 The following are key factors that affect the number of required RUs:
 - **Document size**: As the size of an item/document increases, the number of RUs consumed to read or write the item/document also increases.
+
 - **Document property count**:The number of RUs consumed to create or update a document is related to the number, complexity and length of its properties. You can reduce the request unit consumption for write operations by [limiting the number of indexed properties](mongodb-indexing.md).
+
 - **Query patterns**: The complexity of a query affects how many request units are consumed by the query. 
 
 The best way to understand the cost of queries is to use sample data in Azure Cosmos DB, [and run sample queries from the MongoDB Shell](connect-mongodb-account.md) using the `getLastRequestStastistics` command to get the request charge, which will output the number of RUs consumed:

articles/cosmos-db/mongodb-troubleshoot.md

@@ -1,12 +1,12 @@
 ---
 title: Troubleshoot common errors in Azure Cosmos DB's API for Mongo DB
 description: This doc discusses the ways to troubleshoot common issues encountered in Azure Cosmos DB's API for MongoDB.
-author: roaror
+author: LuisBosquez
 ms.service: cosmos-db
 ms.subservice: cosmosdb-mongo
 ms.topic: troubleshooting
 ms.date: 06/05/2019
-ms.author: roaror
+ms.author: lbosq
 
 ---