Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into ETL2

Author: dagiro

articles/cosmos-db/TOC.yml

@@ -759,14 +759,6 @@
         items:
         - name: 1 - Query data
           href: tutorial-query-graph.md
-      - name: Reference
-        items:
-        - name: Response Headers
-          href: gremlin-headers.md
-        - name: Limits
-          href: gremlin-limits.md
-        - name: Compatibility
-          href: gremlin-compatibility.md
       - name: How-to guides
         items:
         - name: Graph data modeling
@@ -794,6 +786,14 @@
           href: powershell-samples-gremlin.md
         - name: Manage using Azure CLI
           href: cli-samples-gremlin.md
+      - name: Reference
+        items:
+        - name: Response Headers
+          href: gremlin-headers.md
+        - name: Limits
+          href: gremlin-limits.md
+        - name: Compatibility
+          href: gremlin-compatibility.md
     - name: Table API
       items:
       - name: Overview

articles/cosmos-db/change-feed-design-patterns.md

@@ -93,7 +93,7 @@ For example, consider a retail application using the event sourcing design patte
 
 1. Customer adds Item A to their shopping cart
 2. Customer adds Item B to their shopping cart
-3. Customer adds removes Item A from their shopping cart
+3. Customer removes Item A from their shopping cart
 4. Customer checks out and shopping cart contents are shipped
 
 A materialized view of current shopping cart contents is maintained for each customer. This application must ensure that these events are processed in the order in which they occur. If, for example, the cart checkout were to be processed before Item A's removal, it is likely that the customer would have had Item A shipped, as opposed to the desired Item B. In order to guarantee that these four events are processed in order of their occurrence, they should fall within the same partition key value. If you select **username** (each customer has a unique username) as the partition key, you can guarantee that these events show up in the change feed in the same order in which they are written to Azure Cosmos DB.