Merge pull request #48838 from wwlpublish/ad2f39b00aa22f539778f3524d570e813cd513f899a8a2bd47c0914c3f510140-live

v-dirichards · web-flow · commit 502e65bb2c62 · 2025-01-24T13:29:13.000-06:00
Modules/M01-azure-cosmos-db
diff --git a/learn-pr/wwl-azure/explore-azure-cosmos-db/1-introduction.yml b/learn-pr/wwl-azure/explore-azure-cosmos-db/1-introduction.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Introduction
   description: "Introduction"
-  ms.date: 07/12/2024
+  ms.date: 01/24/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/1-introduction.md)]
+  [!include[](includes/1-introduction.md)]
diff --git a/learn-pr/wwl-azure/explore-azure-cosmos-db/10-summary.yml b/learn-pr/wwl-azure/explore-azure-cosmos-db/10-summary.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Summary
   description: "Summary"
-  ms.date: 07/12/2024
+  ms.date: 01/24/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/10-summary.md)]
+  [!include[](includes/10-summary.md)]
diff --git a/learn-pr/wwl-azure/explore-azure-cosmos-db/2-cosmos-db-benefits.yml b/learn-pr/wwl-azure/explore-azure-cosmos-db/2-cosmos-db-benefits.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Identify key benefits of Azure Cosmos DB
   description: "Identify key benefits of Azure Cosmos DB"
-  ms.date: 07/12/2024
+  ms.date: 01/24/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/2-cosmos-db-benefits.md)]
+  [!include[](includes/2-cosmos-db-benefits.md)]
diff --git a/learn-pr/wwl-azure/explore-azure-cosmos-db/3-cosmos-db-resource-hierarchy.yml b/learn-pr/wwl-azure/explore-azure-cosmos-db/3-cosmos-db-resource-hierarchy.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Explore the resource hierarchy
   description: "Explore the resource hierarchy"
-  ms.date: 07/12/2024
+  ms.date: 01/24/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/3-cosmos-db-resource-hierarchy.md)]
+  [!include[](includes/3-cosmos-db-resource-hierarchy.md)]
diff --git a/learn-pr/wwl-azure/explore-azure-cosmos-db/4-cosmos-db-consistency-levels-overview.yml b/learn-pr/wwl-azure/explore-azure-cosmos-db/4-cosmos-db-consistency-levels-overview.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Explore consistency levels
   description: "Explore consistency levels"
-  ms.date: 07/12/2024
+  ms.date: 01/24/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/4-cosmos-db-consistency-levels-overview.md)]
+  [!include[](includes/4-cosmos-db-consistency-levels-overview.md)]
diff --git a/learn-pr/wwl-azure/explore-azure-cosmos-db/5-choose-cosmos-db-consistency-level.yml b/learn-pr/wwl-azure/explore-azure-cosmos-db/5-choose-cosmos-db-consistency-level.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Choose the right consistency level
   description: "Choose the right consistency level"
-  ms.date: 07/12/2024
+  ms.date: 01/24/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/5-choose-cosmos-db-consistency-level.md)]
+  [!include[](includes/5-choose-cosmos-db-consistency-level.md)]
diff --git a/learn-pr/wwl-azure/explore-azure-cosmos-db/6-cosmos-db-supported-apis.yml b/learn-pr/wwl-azure/explore-azure-cosmos-db/6-cosmos-db-supported-apis.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Explore supported APIs
   description: "Explore supported APIs"
-  ms.date: 07/12/2024
+  ms.date: 01/24/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/6-cosmos-db-supported-apis.md)]
+  [!include[](includes/6-cosmos-db-supported-apis.md)]
diff --git a/learn-pr/wwl-azure/explore-azure-cosmos-db/7-cosmos-db-request-units.yml b/learn-pr/wwl-azure/explore-azure-cosmos-db/7-cosmos-db-request-units.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: Discover request units
   description: "Discover request units"
-  ms.date: 07/12/2024
+  ms.date: 01/24/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 3
 content: |
-  [!include[](includes/7-cosmos-db-request-units.md)]
+  [!include[](includes/7-cosmos-db-request-units.md)]
diff --git a/learn-pr/wwl-azure/explore-azure-cosmos-db/8-create-cosmos-db-resources-portal.yml b/learn-pr/wwl-azure/explore-azure-cosmos-db/8-create-cosmos-db-resources-portal.yml
@@ -6,12 +6,12 @@ metadata:
   prefetch-feature-rollout: true
   title: 'Exercise: Create Azure Cosmos DB resources by using the Azure portal'
   description: "Exercise: Create Azure Cosmos DB resources by using the Azure portal"
-  ms.date: 07/12/2024
+  ms.date: 01/24/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
   ms.custom:
   - N/A
 durationInMinutes: 10
 content: |
-  [!include[](includes/8-create-cosmos-db-resources-portal.md)]
+  [!include[](includes/8-create-cosmos-db-resources-portal.md)]
diff --git a/learn-pr/wwl-azure/explore-azure-cosmos-db/9-knowledge-check.yml b/learn-pr/wwl-azure/explore-azure-cosmos-db/9-knowledge-check.yml
@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Knowledge check
   description: "Knowledge check"
-  ms.date: 07/12/2024
+  ms.date: 01/24/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: unit
@@ -37,4 +37,4 @@ quiz:
       explanation: "Incorrect. RUs represent system resources such as CPU, IOPS, and memory that are required to perform the database operations supported by Azure Cosmos DB."
     - content: "A unit of storage used to measure the amount of data stored in Azure Cosmos DB."
       isCorrect: false
-      explanation: "Incorrect. RUs represent the cost of all database operations in Azure Cosmos DB, not the amount of data stored."
+      explanation: "Incorrect. RUs represent the cost of all database operations in Azure Cosmos DB, not the amount of data stored."
diff --git a/learn-pr/wwl-azure/explore-azure-cosmos-db/includes/5-choose-cosmos-db-consistency-level.md b/learn-pr/wwl-azure/explore-azure-cosmos-db/includes/5-choose-cosmos-db-consistency-level.md
@@ -16,7 +16,7 @@ Strong consistency offers a linearizability guarantee. Linearizability refers to
 
 ### Bounded staleness consistency
 
-In bounded staleness consistency, the lag of data between any two regions is always less than a specified amount. The amount can be "K" versions (that is, "updates") of an item or by "T" time intervals, whichever is reached first. In other words, when you choose bounded staleness, the maximum "staleness" of the data in any region can be configured in two ways:
+In bounded staleness consistency, the lag of data between any two regions is always less than a specified amount. The amount can be *K* versions (that is, *updates*) of an item or by *T* time intervals, whichever is reached first. In other words, when you choose bounded staleness, the maximum "staleness" of the data in any region can be configured in two ways:
 
 *   The number of versions (*K*) of the item
 *   The time interval (*T*) reads might lag behind the writes
@@ -27,15 +27,15 @@ For a single-region account, Bounded Staleness provides the same write consisten
 
 ### Session consistency
 
-In session consistency, within a single client session, reads are guaranteed to honor the read-your-writes, and write-follows-reads guarantees. This guarantee assumes a single “writer” session or sharing the session token for multiple writers.
+In session consistency, within a single client session, reads are guaranteed to honor the read-your-writes, and write-follows-reads guarantees. This guarantee assumes a single “writer" session or sharing the session token for multiple writers.
 
 Like all consistency levels weaker than Strong, writes are replicated to a minimum of three replicas (in a four replica set) in the local region, with asynchronous replication to all other regions.
 
 ### Consistent prefix consistency
 
 In consistent prefix, updates made as single document writes see eventual consistency. Updates made as a batch within a transaction, are returned consistent to the transaction in which they were committed. Write operations within a transaction of multiple documents are always visible together.
 
-Assume two write operations are performed on documents *Doc 1* and *Doc 2*, within transactions T1 and T2. When client does a read in any replica, the user sees either “*Doc 1* v1 and *Doc 2* v1” or “*Doc 1* v2 and *Doc 2* v2”, but never “*Doc 1* v1 and *Doc 2* v2” or “*Doc 1* v2 and *Doc 2* v1” for the same read or query operation.
+Assume two write operations are performed on documents *Doc 1* and *Doc 2*, within transactions T1 and T2. When client does a read in any replica, the user sees either "*Doc 1* v1 and *Doc 2* v1" or "*Doc 1* v2 and *Doc 2* v2," but never "*Doc 1* v1 and *Doc 2* v2" or "*Doc 1* v2 and *Doc 2* v1" for the same read or query operation.
 
 ### Eventual consistency
 
diff --git a/learn-pr/wwl-azure/explore-azure-cosmos-db/includes/6-cosmos-db-supported-apis.md b/learn-pr/wwl-azure/explore-azure-cosmos-db/includes/6-cosmos-db-supported-apis.md
@@ -1,14 +1,14 @@
 Azure Cosmos DB offers multiple database APIs, which include NoSQL, MongoDB, PostgreSQL, Cassandra, Gremlin, and Table. By using these APIs, you can model real world data using documents, key-value, graph, and column-family data models. These APIs allow your applications to treat Azure Cosmos DB as if it were various other databases technologies, without the overhead of management, and scaling approaches. Azure Cosmos DB helps you to use the ecosystems, tools, and skills you already have for data modeling and querying with its various APIs.
 
-All the APIs offer automatic scaling of storage and throughput, flexibility, and performance guarantees. There's no one best API, and you may choose any one of the APIs to build your application
+All the APIs offer automatic scaling of storage and throughput, flexibility, and performance guarantees. There's no one best API, and you can choose any one of the APIs to build your application
 
 ## Considerations when choosing an API
 
 API for NoSQL is native to Azure Cosmos DB.
 
 API for MongoDB, PostgreSQL, Cassandra, Gremlin, and Table implement the wire protocol of open-source database engines. These APIs are best suited if the following conditions are true:
 
-* If you have existing MongoDB, PostgreSQL Cassandra, or Gremlin applications
+* If you have existing MongoDB, PostgreSQL, Cassandra, or Gremlin applications
 * If you don't want to rewrite your entire data access layer
 * If you want to use the open-source developer ecosystem, client-drivers, expertise, and resources for your database
 
diff --git a/learn-pr/wwl-azure/explore-azure-cosmos-db/includes/7-cosmos-db-request-units.md b/learn-pr/wwl-azure/explore-azure-cosmos-db/includes/7-cosmos-db-request-units.md
@@ -12,6 +12,6 @@ The type of Azure Cosmos DB account you're using determines the way consumed RUs
 
 *  **Provisioned throughput mode**: In this mode, you provision the number of RUs for your application on a per-second basis in increments of 100 RUs per second. To scale the provisioned throughput for your application, you can increase or decrease the number of RUs at any time in increments or decrements of 100 RUs. You can make your changes either programmatically or by using the Azure portal. You can provision throughput at container and database granularity level.
 
-*  **Serverless mode**: In this mode, you don't have to provision any throughput when creating resources in your Azure Cosmos DB account. At the end of your billing period, you get billed for the number of request units that have been consumed by your database operations.
+*  **Serverless mode**: In this mode, you don't have to provision any throughput when creating resources in your Azure Cosmos DB account. At the end of your billing period, you get billed for the number of request units consumed by your database operations.
 
 * **Autoscale mode:** In this mode, you can automatically and instantly scale the throughput (RU/s) of your database or container based on its usage. This scaling operation doesn't affect the availability, latency, throughput, or performance of the workload. This mode is well suited for mission-critical workloads that have variable or unpredictable traffic patterns, and require SLAs on high performance and scale.
diff --git a/learn-pr/wwl-azure/explore-azure-cosmos-db/index.yml b/learn-pr/wwl-azure/explore-azure-cosmos-db/index.yml
@@ -5,14 +5,14 @@ metadata:
   prefetch-feature-rollout: true
   title: Explore Azure Cosmos DB
   description: "Learn the core features and functionality of Azure Cosmos DB."
-  ms.date: 07/12/2024
+  ms.date: 01/24/2025
   author: wwlpublish
   ms.author: jeffko
   ms.topic: module
   ms.custom:
   - N/A
   ms.service: azure-cosmos-db
-  ai-usage: human-only
+  ai-usage: ai-assisted
 title: Explore Azure Cosmos DB
 summary: Learn the core features and functionality of Azure Cosmos DB.
 abstract: |
@@ -57,4 +57,4 @@ units:
 - learn.wwl.explore-azure-cosmos-db.knowledge-check
 - learn.wwl.explore-azure-cosmos-db.summary
 badge:
-  uid: learn.wwl.explore-azure-cosmos-db.badge
+  uid: learn.wwl.explore-azure-cosmos-db.badge
