changed files by pdets auto publish service, publishid[3ed86ec3-009c-4d20-a165-cb9bd755aae0] and do [publish].

Author: wwlpublish

learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/6-knowledge-check.yml

@@ -34,7 +34,7 @@ quiz:
       explanation: "Correct. Setting the ``indexingMode`` property to ``none`` disables all indexing."
     - content: "``excludedPaths``"
       isCorrect: false
-      explanation: "Incorrect. The ``excludedPaths`` property determines which paths are excluded from the index, not whether the indexer will run."
+      explanation: "Incorrect. The ``excludedPaths`` property determines which paths are excluded from the index, not whether the indexer runs."
     - content: "``automatic``"
       isCorrect: false
       explanation: "Incorrect. Disabling ``automatic`` indexing using a boolean value of ``false`` doesn't disable all indexing for the container."

learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/includes/4-review-write-heavy-index-patterns.md

@@ -1,6 +1,6 @@
 If you want your NoSQL queries to be endlessly flexible, why exclude any paths at all? Well, each insert or update operation requires the indexer to run to update the inverted index with data from your newly created or updated item. More oversized items, or bulk workloads, can cause the indexing to use many RU/s or take a significant amount of time.
 
-Let’s consider an example JSON object that is much larger than previous examples.
+Let’s consider an example JSON object that is larger than previous examples.
 
 ```json
 {
@@ -76,7 +76,7 @@ WHERE
     p.price = <numeric-value>
 ```
 
-An indexing policy that excludes all paths, except for the **price** property path, would be appropriate here. This policy will still index items, but it will do so quickly because only one property is added to the inverted index.
+An indexing policy that excludes all paths, except for the **price** property path, would be appropriate here. This policy will still index items, but it does so quickly because only one property is added to the inverted index.
 
 ```json
 {
@@ -96,9 +96,9 @@ An indexing policy that excludes all paths, except for the **price** property pa
 ```
 
 > [!TIP]
-> Again, the drawback to this approach is that you will need to update the index anytime you change your schema.
+> Again, the drawback to this approach is that you'll need to update the index anytime you change your schema.
 
-Here is a diagram of the inverted index showing that it only has a single property to traverse and then multiple potential values.
+Here's a diagram of the inverted index showing that it only has a single property to traverse and then multiple potential values.
 
 ![Inverted tree with a single property node of price and multiple child nodes](../media/4-inverted-tree.png)
 

learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/includes/5-exercise-optimize-containers-index-policy-common-operations.md

@@ -1,7 +1,7 @@
 ### Set up environment
 
 > [!NOTE]
-> To complete this exercise, you will need a [Microsoft Azure subscription](https://azure.microsoft.com/free?azure-portal=true) in which you have administrative access.
+> To complete this exercise, you'll need a [Microsoft Azure subscription](https://azure.microsoft.com/free?azure-portal=true) in which you have administrative access.
 
 To set up the lab environment for this exercise, sign into your Azure subscription and follow these instructions to provision your Azure resources: