Bug Fixes

Author: v-meluri

learn-pr/wwl-azure/implement-secure-ai-ready-infrastructure-azure-services/6-knowledge-check.yml

@@ -24,7 +24,7 @@ quiz:
     - content: "The private endpoint configuration is blocking managed identity token validation and needs a service endpoint exception rule"
       isCorrect: false
       explanation: "Incorrect. Private endpoints don't interfere with managed identity authentication—tokens are validated through Azure Active Directory, not through network connectivity to the service."
-  - content: "Your compliance team requires that all AI service requests and responses remain within European Azure regions to satisfy GDPR data residency requirements. You've deployed Azure OpenAI Service in West Europe with a private endpoint. Which more configuration ensures complete data residency compliance?"
+  - content: "Your compliance team requires that all AI service requests and responses remain within European Azure regions to satisfy regulatory data residency requirements. You've deployed Azure OpenAI Service in West Europe with a private endpoint. Which more configuration ensures complete data residency compliance?"
     choices:
     - content: "Configure diagnostic settings to send logs to a Log Analytics workspace located in the same West Europe region where the OpenAI service is deployed"
       isCorrect: true

learn-pr/wwl-azure/implement-secure-ai-ready-infrastructure-azure-services/includes/3-secure-azure-openai-cognitive-services.md

@@ -27,9 +27,9 @@ Building on this concept, you can create custom content filters when standard ca
 
 ## Data residency and compliance boundaries
 
-Consider what happens when your European fraud detection team needs Azure OpenAI Service for analyzing transactions. GDPR requires that EU customer data stays within European Economic Area borders, but Azure OpenAI's default deployment might process requests in any global region. This creates compliance risk that could result in regulatory fines and damage customer trust.
+Consider what happens when your European fraud detection team needs Azure OpenAI Service for analyzing transactions. Regulatory requires that EU customer data stays within European Economic Area borders, but Azure OpenAI's default deployment might process requests in any global region. This creates compliance risk that could result in regulatory fines and damage customer trust.
 
-Azure OpenAI Service supports regional deployments that guarantee data processing stays within specific geographies. When you create an OpenAI resource, you select an Azure region like West Europe or North Europe. All model training, inference processing, and data storage for that resource occurs within your chosen region. Your Foundry Hub configuration can enforce this requirement by restricting project creation to approved regions. The fraud detection project deploys its OpenAI instance in West Europe, ensuring GDPR compliance, while the US-based customer service project uses East US for lower latency to American call centers.
+Azure OpenAI Service supports regional deployments that guarantee data processing stays within specific geographies. When you create an OpenAI resource, you select an Azure region like West Europe or North Europe. All model training, inference processing, and data storage for that resource occurs within your chosen region. Your Foundry Hub configuration can enforce this requirement by restricting project creation to approved regions. The fraud detection project deploys its OpenAI instance in West Europe, ensuring regulatory compliance, while the US-based customer service project uses East US for lower latency to American call centers.
 
 :::image type="content" source="../media/azure-service-support-regional-deployments.png" alt-text="Diagram showing how Azure OpenAI Service supports regional deployments that guarantee data processing.":::