Merge pull request #306616 from johndowns/reliability-conceptual-diagrams

Reliability Hub - Update diagrams for conceptual articles

Author: JamesJBarnett

articles/reliability/concept-business-continuity-high-availability-disaster-recovery.md

@@ -270,7 +270,7 @@ Due to the rarity and severity of disaster events, DR planning brings different
 
 - **Recovery Time Objective (RTO)** is the maximum duration of acceptable downtime in the event of a disaster, where "downtime" is defined by your specification. RTO is also measured in units of time, like "eight hours of downtime."
 
-:::image type="content" source="media/disaster-recovery-rpo-rto.png" alt-text="Screenshot of RTO and RPO durations in hours." border="false":::
+:::image type="content" source="media/concept-business-continuity-high-availability-disaster-recovery/disaster-recovery-timeline.svg" alt-text="Diagram that shows the timeline of an example disaster, with RTO and RPO durations measured in hours." border="false":::
 
 Each component or flow in the workload might have individual RPO and RTO values. Examine disaster-scenario risks and potential recovery strategies when deciding on the requirements. The process of specifying an RPO and RTO effectively creates DR requirements for your workload as a result of your unique business concerns (costs, impact, data loss, etc.).
 

articles/reliability/concept-shared-responsibility.md

@@ -24,7 +24,7 @@ The shared responsibility model for reliability is composed of three levels:
 - [Resilience-enhancing capabilities](#resilience-enhancing-capabilities) Azure offers a suite of built-in features and services that enhance resiliency, such as using availability zones, deploying across multiple regions, and implementing backup strategies. While Azure provides these capabilities, it's your responsibility to evaluate and configure them to align with your specific requirements. Requirements can include reliability, cost, performance, and compliance with regulatory standards.
 - [Applications](#applications). To make effective use of the other levels, your application and workload must be designed for resiliency.
 
-:::image type="content" source="media/shared-responsibility-model.jpg" alt-text="Diagram showing shared responsibility model for reliability: Core platform reliability, resilience-enhancing capabilities, and applications." border="false":::
+:::image type="content" source="media/concept-shared-responsibility/shared-responsibility-model.svg" alt-text="Diagram showing shared responsibility model for reliability: Core platform reliability, resilience-enhancing capabilities, and applications." border="false":::
 
 Microsoft is solely responsible for core platform reliability. Microsoft is also responsible for providing resilience-enhancing capabilities that you can use. You're responsible for selecting and using the appropriate components.