update and add image

Author: ceperezb

learn-pr/wwl-sci/design-solutions-align-cloud-adoption-framework-well-architected-framework/includes/6-introduction-well-architected-framework.md

@@ -22,6 +22,9 @@ The framework consists of five pillars:
 | **Operational Excellence** | Holistic observability and DevOps practices | Integrate security into deployment pipelines |
 | **Performance Efficiency** | Scalability and load testing | Ensure security controls don't become bottlenecks |
 
+:::image type="content" source="../media/waf-diagram-revised.png" alt-text="Diagram showing the five pillars of the Azure Well Architected framework." lightbox="../media/waf-diagram-revised.png":::
+
+
 ## Why security architects need the Well-Architected Framework
 
 Security isn't a standalone concern. Every architectural decision involves tradeoffs between pillars. For example, adding encryption at rest improves security but might affect performance. Implementing redundant security controls improves reliability but increases costs. The Well-Architected Framework helps you make these tradeoffs deliberately rather than accidentally.

learn-pr/wwl-sci/design-solutions-align-cloud-adoption-framework-well-architected-framework/includes/7-well-architected-framework-security-pillar.md

@@ -32,7 +32,7 @@ Cloud providers must be compliant with the same IT regulatory requirements as th
 
 **Shared Responsibility Model:** As computing environments move from customer-controlled datacenters to the cloud, the responsibility of security also shifts. Security of the operational environment is now a concern shared by both cloud providers and customers. Organizations can reduce focus on activities that aren't core business competencies by shifting these responsibilities to a cloud service like Azure. Depending on the specific technology choices, some security protections are built into the particular service, while addressing others remains the customer's responsibility. To ensure that proper security controls are provided, organizations must carefully evaluate the services and technology choices.
 
-![Diagram showing shared responsibility and key strategies.](../media/shared-resp-color.png)
+:::image type="content" source="../media/shared-responsibility-model.png" alt-text="Diagram showing shared responsibility and key strategies." lightbox="../media/shared-responsibility-model.png":::
 
 **Shared Responsibility and Key Strategies:**