Fixed acrolinx issues in YML files

Author: R-C-Stewart

learn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/2-explore-multicloud-connectivity-model.yml

@@ -1,14 +1,14 @@
 ### YamlMime:ModuleUnit
 uid: learn.wwl.connect-hybrid-multicloud-environments-defender.explore-multicloud-connectivity-model
 metadata:
-  title: Explore the Defender for Cloud multi-cloud connectivity model
-  description: Learn how CSPM and CWPP coverage layers work, what federated authentication means for AWS and GCP connectors, and what becomes available after connecting each environment type.
+  title: Explore the Defender for Cloud multicloud connectivity model
+  description: Learn how Cloud Security Posture Management (CSPM) and Cloud Workload Protection Platform (CWPP) coverage layers work. Explore what federated authentication means for AWS and GCP connectors, and what becomes available after connecting each environment type.
   ms.date: 04/01/2026
   author: r-c-stewart
   ms.author: roberts
   ms.topic: unit
   ai-usage: ai-generated
-title: Explore the Defender for Cloud multi-cloud connectivity model
+title: Explore the Defender for Cloud multicloud connectivity model
 durationInMinutes: 8
 content: |
   [!include[](includes/2-explore-multicloud-connectivity-model.md)]

learn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/3-plan-connector-strategy.yml

@@ -1,14 +1,14 @@
 ### YamlMime:ModuleUnit
 uid: learn.wwl.connect-hybrid-multicloud-environments-defender.plan-connector-strategy
 metadata:
-  title: Plan a connector strategy for hybrid and multi-cloud environments
+  title: Plan a connector strategy for hybrid and multicloud environments
   description: Plan connector scope, scan interval, permission model, and deployment path for on-premises, AWS, and GCP environments in Microsoft Defender for Cloud.
   ms.date: 04/01/2026
   author: r-c-stewart
   ms.author: roberts
   ms.topic: unit
   ai-usage: ai-generated
-title: Plan a connector strategy for hybrid and multi-cloud environments
+title: Plan a connector strategy for hybrid and multicloud environments
 durationInMinutes: 8
 content: |
   [!include[](includes/3-plan-connector-strategy.md)]

learn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/7-verify-multicloud-coverage.yml

@@ -1,14 +1,14 @@
 ### YamlMime:ModuleUnit
 uid: learn.wwl.connect-hybrid-multicloud-environments-defender.verify-multicloud-coverage
 metadata:
-  title: Verify multi-cloud coverage and validate protection
-  description: Verify multi-cloud connector health, confirm CSPM recommendations and compliance standards are active, and validate CWPP plan activation across on-premises, AWS, and GCP environments.
+  title: Verify multicloud coverage and validate protection
+  description: Verify multicloud connector health, confirm CSPM recommendations and compliance standards are active, and validate CWPP plan activation across on-premises, AWS, and GCP environments.
   ms.date: 04/01/2026
   author: r-c-stewart
   ms.author: roberts
   ms.topic: unit
   ai-usage: ai-generated
-title: Verify multi-cloud coverage and validate protection
+title: Verify multicloud coverage and validate protection
 durationInMinutes: 6
 content: |
   [!include[](includes/7-verify-multicloud-coverage.md)]

learn-pr/wwl-sci/connect-hybrid-multicloud-environments-defender/includes/2-explore-multicloud-connectivity-model.md

@@ -38,7 +38,7 @@ The authentication flow works as follows. Defender for Cloud requests a token fr
 
 AWS performs audience, signature, thumbprint, and role-level checks before issuing credentials, ensuring only the specific Microsoft-managed application can assume the connector role.
 
-:::image type="content" source="../media/amazon-auth-sequence.png" alt-text="Sequence diagram of the AWS federated auth flow: Defender for Cloud exchanges a Microsoft Entra token with AWS STS for temporary credentials, then calls AWS APIs. No credentials are stored.":::
+:::image type="content" source="../media/amazon-authentication-sequence.png" alt-text="Sequence diagram of the AWS federated auth flow: Defender for Cloud exchanges a Microsoft Entra token with AWS STS for temporary credentials, then calls AWS APIs. No credentials are stored.":::
 
 This architecture means that even if an attacker gained access to the Azure environment, there are no stored AWS credentials to exfiltrate. The trust is used by the specific Microsoft-managed application, during a valid authentication transaction.