Merge pull request #53036 from JeffKoMS/bug-fixes-20260102

SE Bug fixes for three different modules

Author: JamesJBarnett

learn-pr/wwl-azure/explore-api-management/9-knowledge-check.yml

@@ -17,7 +17,7 @@ durationInMinutes: 3
 quiz:
   title: "Check your knowledge"
   questions:
-  - content: "Which of the following components of the API Management service would a developer use if they need to create an account and subscribe to get API keys?"
+  - content: "Which of the following components of the API Management service would a developer use if they need to create an account and subscribe to get subscription keys?"
     choices:
     - content: "API gateway"
       isCorrect: false
@@ -27,7 +27,7 @@ quiz:
       explanation: "Incorrect. The Azure portal is the administrative interface where you set up your API program."
     - content: "Developer portal"
       isCorrect: true
-      explanation: "Correct. The Developer portal serves as the main web presence for developers, and is where they can subscribe to get API keys."
+      explanation: "Correct. The Developer portal serves as the main web presence for developers, and is where they can subscribe to get subscription keys."
   - content: "Which of the following API Management policies applies a policy based on a condition?"
     choices:
     - content: "forward-request"

learn-pr/wwl-azure/explore-azure-cosmos-db/includes/6-cosmos-db-supported-apis.md

@@ -14,7 +14,7 @@ API for MongoDB, PostgreSQL, Cassandra, Gremlin, and Table implement the wire pr
 
 ## API for NoSQL
 
-The Azure Cosmos DB API for NoSQL stores data in document format. It offers the best end-to-end experience as we have full control over the interface, service, and the SDK client libraries. Any new feature that is rolled out to Azure Cosmos DB is first available on API for NoSQL accounts. NoSQL accounts provide support for querying items using the Structured Query Language (SQL) syntax.
+The Azure Cosmos DB API for NoSQL stores data as JSON documents (called items). It offers the best end-to-end experience as we have full control over the interface, service, and the SDK client libraries. Any new feature that is rolled out to Azure Cosmos DB is first available on API for NoSQL accounts. NoSQL accounts provide support for querying items using the Structured Query Language (SQL) syntax.
 
 ## API for MongoDB
 

learn-pr/wwl-azure/introduction-to-azure-app-service/includes/6-network-features.md

@@ -9,7 +9,7 @@ There are two main deployment types for Azure App Service:
 
 Azure App Service is a distributed system. The roles that handle incoming HTTP or HTTPS requests are called *front ends*. The roles that host the customer workload are called *workers*. All the roles in an App Service deployment exist in a multitenant network. Because there are many different customers in the same App Service scale unit, you can't connect the App Service network directly to your network.
 
-Instead of connecting the networks, you need features to handle the various aspects of application communication. The features that handle requests to your app can't be used to solve problems when you're making calls from your app. Likewise, the features that solve problems for calls from your app can't be used to solve problems to your app.
+Instead of directly connecting the networks, App Service provides networking features for different aspects of application communication. Inbound features control traffic coming to your app, and outbound features govern connections your app makes to external endpoints. Use inbound features to solve inbound problems and outbound features to solve outbound problems.
 
 | Inbound features | Outbound features |
 |--|--|
@@ -45,7 +45,7 @@ You can find the same information by running the following Azure CLI command in
 ```bash
 az webapp show \
     --resource-group <group_name> \
-    --name <app_name> \ 
+    --name <app_name> \
     --query outboundIpAddresses \
     --output tsv
 ```
@@ -54,8 +54,8 @@ To find all possible outbound IP addresses for your app, regardless of pricing t
 
 ```bash
 az webapp show \
-    --resource-group <group_name> \ 
-    --name <app_name> \ 
+    --resource-group <group_name> \
+    --name <app_name> \
     --query possibleOutboundIpAddresses \
     --output tsv
 ```