fix blocking issues

ceperezb · ceperezb · commit 79d4027ec0c0 · 2026-02-10T20:35:19.000-05:00
diff --git a/learn-pr/wwl-sci/design-solutions-secure-applications/includes/4-evaluate-application-threats-threat-modeling.md b/learn-pr/wwl-sci/design-solutions-secure-applications/includes/4-evaluate-application-threats-threat-modeling.md
@@ -86,7 +86,7 @@ The [Microsoft Threat Modeling Tool](/azure/security/develop/threat-modeling-too
 
 The tool is designed for use by both security specialists and developers. It produces threat models that serve as versioned artifacts stored alongside architecture documentation in source control.
 
-## Integrating threat modeling into development workflows
+## Integrate threat modeling into development workflows
 
 As an architect, you should design a process that scales threat modeling across the organization without creating bottlenecks:
 
diff --git a/learn-pr/wwl-sci/design-solutions-secure-applications/includes/6-secure-access-workload-identities.md b/learn-pr/wwl-sci/design-solutions-secure-applications/includes/6-secure-access-workload-identities.md
@@ -44,7 +44,7 @@ Common federation scenarios include:
 
 When designing federation, configure federated credential subjects narrowly. For GitHub Actions, restrict the subject to a specific repository, branch, or environment rather than allowing any workflow in an organization to authenticate.
 
-## Securing workload identities
+## Secure workload identities
 
 Assigning identities to workloads isn't sufficient. You need to secure those identities with the same rigor you apply to human accounts. Microsoft Entra Workload ID provides several capabilities for this purpose:
 
