Updates per feedback

SnehaGunda · SnehaGunda · commit 45fc798f27d7 · 2018-11-12T22:42:18.000-08:00
diff --git a/articles/cosmos-db/TOC.yml b/articles/cosmos-db/TOC.yml
@@ -69,7 +69,7 @@
         href: create-table-python.md
   - name: Concepts
     items:
-    - name: Working with Azure Cosmos DB account
+    - name: Working with Azure Cosmos account
       href: account-overview.md
     - name: Containers and items
       items:
@@ -80,7 +80,7 @@
         - name: Overview
           href: indexing-overview.md
         - name: Indexing policy
-          href: indexing-policy.md
+          href: index-policy.md
         - name: Index types
           href: index-types.md
         - name: Index paths
@@ -90,7 +90,7 @@
         - name: Overview
           href: change-feed.md
         - name: Reading change feed
-          href: change-feed-reading.md
+          href: read-change-feed.md
         - name: Change feed processor
           href: change-feed-processor.md
         - name: Change feed with Azure Functions 
diff --git a/articles/cosmos-db/account-overview.md b/articles/cosmos-db/account-overview.md
@@ -13,17 +13,17 @@ ms.reviewer: sngun
 
 # Working with Azure Cosmos DB accounts
 
-Azure Cosmos DB is a fully managed platform-as-a-service (PaaS). To begin using Azure Cosmos DB, you should initially create an Azure Cosmos DB account in your Azure subscription. Your Azure Cosmos DB account contains a unique DNS name and you can manage an account by using Azure portal, Azure CLI or by using different language-specific SDKs. For more information, see [how to manage your account](how-to-manage-database-account.md).
+Azure Cosmos DB is a fully managed platform-as-a-service (PaaS). To begin using Azure Cosmos DB, you should initially create an Azure Cosmos DB account in your Azure subscription. Your Azure Cosmos account contains a unique DNS name and you can manage an account by using Azure portal, Azure CLI or by using different language-specific SDKs. For more information, see [how to manage your Azure Cosmos account](how-to-manage-database-account.md).
 
-The Azure Cosmos DB account is the fundamental unit of global distribution and high availability. For globally distributing your data and throughput across multiple Azure regions, you can add and remove Azure regions to your account at any time. You can configure your account to have either a single or multiple write regions. For more information, see [how to add and remove Azure regions to your Azure Cosmos account](how-to-manage-database-account.md). You can configure the [default consistency](consistency-levels.md) level on Azure Cosmos account. Azure Cosmos DB provides comprehensive SLAs encompassing throughput, latency at the 99th percentile, consistency, and high availability. For more information, see [Azure Cosmos DB SLAs](https://azure.microsoft.com/en-us/support/legal/sla/cosmos-db/v1_2/).
+The Azure Cosmos DB account is the fundamental unit of global distribution and high availability. For globally distributing your data and throughput across multiple Azure regions, you can add and remove Azure regions to your Azure Cosmos account at any time. You can configure your Azure Cosmos account to have either a single or multiple write regions. For more information, see [how to add and remove Azure regions to your Azure Cosmos account](how-to-manage-database-account.md). You can configure the [default consistency](consistency-levels.md) level on Azure Cosmos account. Azure Cosmos DB provides comprehensive SLAs encompassing throughput, latency at the 99th percentile, consistency, and high availability. For more information, see [Azure Cosmos DB SLAs](https://azure.microsoft.com/en-us/support/legal/sla/cosmos-db/v1_2/).
 
-To securely manage access to all the data within your Azure Cosmos DB account, you can use the master keys associated with your account. To further secure access to your data, you can configure a VNET service endpoint and IP-firewall on your Azure Cosmos account. 
+To securely manage access to all the data within your Azure Cosmos account, you can use the master keys associated with your account. To further secure access to your data, you can configure a VNET service endpoint and IP-firewall on your Azure Cosmos account. 
 
 ## Elements in an Azure Cosmos account
 
 Azure Cosmos DB container is the fundamental unit of scalability. You can virtually have an unlimited provisioned throughput (RU/s) and storage on a container. Azure Cosmos DB transparently partitions your container using the logical partition key that you specify in order to elastically scale your provisioned throughput and storage. For more information, see [working with Azure Cosmos containers and items](databases-containers-items.md).
 
-Currently, you can create a maximum of 100 Azure Cosmos DB accounts under an Azure subscription. A single account can virtually manage unlimited amount of data and provisioned throughput. To manage your data and provisioned throughput, you can create one or more Azure Cosmos databases under your account and within that database, you can create one or more containers. The following image shows the hierarchy of elements in an Azure Cosmos account:
+Currently, you can create a maximum of 100 Azure Cosmos accounts under an Azure subscription. A single Azure Cosmos account can virtually manage unlimited amount of data and provisioned throughput. To manage your data and provisioned throughput, you can create one or more Azure Cosmos databases under your account and within that database, you can create one or more containers. The following image shows the hierarchy of elements in an Azure Cosmos account:
 
 ![Hierarchy of a Azure Cosmos account](./media/account-overview/hierarchy.png)
 
diff --git a/articles/cosmos-db/change-feed-functions.md b/articles/cosmos-db/change-feed-functions.md
@@ -60,7 +60,7 @@ The Azure Cosmos DB Trigger leverages the Change Feed Processor library internal
 You can now proceed to learn more about change feed in the following articles:
 
 * [Overview of change feed](change-feed.md)
-* [Ways to read change feed](change-feed-reading.md)
+* [Ways to read change feed](read-change-feed.md)
 * [Using change feed processor library](change-feed-processor.md)
 * [How to work with change feed processor library](change-feed-processor.md)
 * [Serverless database computing using Azure Cosmos DB and Azure Functions](serverless-computing-database.md)
diff --git a/articles/cosmos-db/change-feed-processor.md b/articles/cosmos-db/change-feed-processor.md
@@ -71,5 +71,5 @@ You are charged for RUs consumed, since data movement in and out of Cosmos conta
 You can now proceed to learn more about change feed in the following articles:
 
 * [Overview of change feed](change-feed.md)
-* [Ways to read change feed](change-feed-reading.md)
+* [Ways to read change feed](read-change-feed.md)
 * [Using change feed with Azure Functions](change-feed-functions.md)
diff --git a/articles/cosmos-db/change-feed.md b/articles/cosmos-db/change-feed.md
@@ -119,6 +119,6 @@ Change feed is available for each logical partition key within the container, an
 
 You can now proceed to learn more about change feed in the following articles:
 
-* [Options to read change feed](change-feed-reading.md)
+* [Options to read change feed](read-change-feed.md)
 * [Using change feed with Azure Functions](change-feed-functions.md)
 * [Using change feed processor library](change-feed-processor.md)
diff --git a/articles/cosmos-db/database-transactions-optimistic-concurrency.md b/articles/cosmos-db/database-transactions-optimistic-concurrency.md
@@ -35,7 +35,7 @@ The database engine in Azure Cosmos DB supports full ACID (Atomicity, Consistenc
 | Paginated Query | Read | Multi-item transaction |
 | Execute UDF as part of the paginated query | Read | Multi-item transaction |
 
-## Multi-item transactions in JavaScript
+## Multi-item transactions
 
 Azure Cosmos DB allows you to write stored procedures, pre/post triggers, user-defined-functions (UDFs) and merge procedures in JavaScript. Azure Cosmos DB natively supports JavaScript execution inside its database engine. You can register stored procedures, pre/post triggers, user-defined-functions (UDFs) and merge procedures on a container and later execute them transactionally within the Azure Cosmos database engine. Writing application logic in JavaScript allows natural expression of control flow, variable scoping, assignment, and integration of exception handling primitives within the database transactions directly in the JavaScript language.
 
diff --git a/articles/cosmos-db/databases-containers-items.md b/articles/cosmos-db/databases-containers-items.md
@@ -13,9 +13,9 @@ ms.reviewer: sngun
 
 # Working with Azure Cosmos databases, containers and items
 
-After you create an [Azure Cosmos DB account](account-overview.md) under your Azure subscription, you can manage data in your account by creating databases, containers, and items. This article describes each of these entities: databases, containers, and items. The following image shows the hierarchy of different entities in Azure Cosmos DB:
+After you create an [Azure Cosmos DB account](account-overview.md) under your Azure subscription, you can manage data in your account by creating databases, containers, and items. This article describes each of these entities: databases, containers, and items. The following image shows the hierarchy of different entities in an Azure Cosmos account:
 
-![Azure Cosmos DB entities](./media/databases-containers-items/cosmos-entities.png)
+![Azure Cosmos account entities](./media/databases-containers-items/cosmos-entities.png)
 
 ## Azure Cosmos databases
 
@@ -30,7 +30,7 @@ You can create one or more Azure Cosmos databases under your account. A database
 
 ### Operations on an Azure Cosmos database
 
-You can interact with an Azure Cosmos database using the following Azure Cosmos DB APIs:
+You can interact with an Azure Cosmos database using the following Azure Cosmos APIs:
 
 | **Operation** | **Azure CLI**|**SQL API** | **Cassandra API** | **MongoDB API** | **Gremlin API** | **Table API** |
 | --- | --- | --- | --- | --- | --- | --- |
@@ -129,7 +129,7 @@ Azure Cosmos item supports the following operations that can be performed using
 
 ## Next steps
 
-You can now proceed to learn how to provision throughput on  Azure Cosmos account or see other concepts associated with Azure Cosmos DB:
+You can now proceed to learn how to provision throughput on Azure Cosmos account or see other concepts:
 
 * [How to configure provisioned throughput on a Azure Cosmos database](how-to-provision-database-throughput.md)
 * [How to configure provisioned throughput on a Azure Cosmos container](how-to-provision-container-throughput.md)
diff --git a/articles/cosmos-db/how-to-manage-indexing-policy.md b/articles/cosmos-db/how-to-manage-indexing-policy.md
@@ -47,11 +47,11 @@ client.CreateDocumentAsync(UriFactory.CreateDocumentCollectionUri("myDatabaseNam
     new RequestOptions { IndexingDirective = IndexingDirective.Include });
 ```
 
-## Next Steps
+## Next steps
 
 Read more about the indexing in the following articles:
 
 * [Indexing Overview](indexing-overview.md)
-* [Indexing policy](indexing-policy.md)
+* [Indexing policy](index-policy.md)
 * [Index types](index-types.md)
 * [Index paths](index-paths.md)
diff --git a/articles/cosmos-db/how-to-time-to-live.md b/articles/cosmos-db/how-to-time-to-live.md
@@ -103,7 +103,7 @@ SalesOrder salesOrder = new SalesOrder
 };
 ```
 
-## Reset time to live on an item
+## Reset time to live
 
 You can reset the time to live on an item by performing a write or update operation on the item. The write or update operation will set the `_ts` to the current time, and the TTL for the item to expire  will begin again. If you wish to change the TTL of an item, you can update the field just as you update any other field.
 
@@ -121,7 +121,7 @@ readDocument.TimeToLive = 60 * 30 * 30; // update time to live
 response = await client.ReplaceDocumentAsync(readDocument);
 ```
 
-## Turn off time to live for an item
+## Turn off time to live
 
 If time to live has been set on an item and you no longer want that item to expire, then you can get the item, remove the TTL field, and replace the item on the server. When the TTL field is removed from the item, the default TTL value assigned to the container is applied to the item. Set the TTL value to -1 to prevent an item from expiring and to not inherit the TTL value from the container.
 
@@ -154,7 +154,7 @@ collection.DefaultTimeToLive = null;
 await client.ReplaceDocumentCollectionAsync(collection);
 ```
 
-## Next Steps
+## Next steps
 
 Learn more about time to live in the following article:
 
diff --git a/articles/cosmos-db/index-policy.md b/articles/cosmos-db/index-policy.md
@@ -19,7 +19,7 @@ You can override the default indexing policy on an Azure Cosmos container by con
 
 * **Configure index modes**: By using the indexing policy on a container, you can configure different indexing modes such as *Consistent* or *None*.
 
-## Indexing modes on a container 
+## Indexing modes 
 
 Azure Cosmos DB supports two indexing modes that you can configure on an Azure Cosmos container. You can configure the following two indexing modes through the indexing policy: 
 
diff --git a/articles/cosmos-db/indexing-overview.md b/articles/cosmos-db/indexing-overview.md
@@ -54,7 +54,7 @@ For a range query, GermanTax is a user-defined function executed as part of quer
 
 Read more about indexing in the following articles:
 
-- [Indexing policy](indexing-policy.md)
+- [Indexing policy](index-policy.md)
 - [Index types](index-types.md)
 - [Index paths](index-paths.md)
 - [How to manage indexing policy](how-to-manage-indexing-policy.md)
diff --git a/articles/cosmos-db/media/account-overview/hierarchy.png b/articles/cosmos-db/media/account-overview/hierarchy.png
diff --git a/articles/cosmos-db/media/indexing/index-paths-patterns.png b/articles/cosmos-db/media/indexing/index-paths-patterns.png
diff --git a/articles/cosmos-db/media/indexing/index-types-examples.png b/articles/cosmos-db/media/indexing/index-types-examples.png
diff --git a/articles/cosmos-db/read-change-feed.md b/articles/cosmos-db/read-change-feed.md
diff --git a/articles/cosmos-db/unique-keys.md b/articles/cosmos-db/unique-keys.md
@@ -46,17 +46,6 @@ You can define unique keys only when creating a Cosmos container. A unique key i
 
 * Unique key names are case-sensitive. For example, consider a container with the unique key constraint set to /address/zipcode. If your data has a field named ZipCode, Cosmos DB inserts "null" as the unique key because "zipcode" is not same as "ZipCode". Due to this case sensitivity, all other records with ZipCode can't be inserted because the duplicate "null" will violate the unique key constraint.
 
-## Supported APIs and SDKs
-
-The unique keys feature is currently supported by the following Cosmos DB APIs and client SDKs: 
-
-|Client drivers|SQL API|Cassandra API|MongoDB API|Gremlin API|Table API|
-|---|---|---|---|---|---|
-|.NET|Yes|No|Yes|No|No|
-|Java|Yes|No|Yes|No|No|
-|Python|Yes|No|Yes|No|No|
-|Node/JS|Yes|No|Yes|No|No|
-
 ## Next steps
 
 * Learn more about [logical partitions](partition-data.md)
