Review feedback.

Author: roygara

articles/storage/elastic-san/elastic-san-performance.md

@@ -77,7 +77,7 @@ The following example scenarios depict how your Elastic SAN handles performance
 
 In this scenario, no throttling occurs at either the VM or SAN level. The SAN itself has 135,000 IOPS, each volume is large enough to serve up to 64,000 IOPS, enough IOPS are available from the SAN, none of the VM's IOPS limits have been surpassed, and the total IOPS requested is 41,000. So the workloads all execute without any throttling.
 
-:::image type="content" source="media/elastic-san-performance/scenario_one.png" alt-text="Average scenario example diagram." lightbox="media/elastic-san-performance/scenario_one.png":::
+:::image type="content" source="media/elastic-san-performance/typical-workload.png" alt-text="Average scenario example diagram." lightbox="media/elastic-san-performance/typical-workload.png":::
 
 ### Single workload spike
 
@@ -93,7 +93,7 @@ In this scenario, no throttling occurs. Workload 3 spiked at 9am, requesting 64,
 
 Generally, this is the ideal configuration for a SAN sharing workloads. It's best to have enough performance to handle the normal operations of workloads, and occasional peaks.
 
-:::image type="content" source="media/elastic-san-performance/scenario_two.png" alt-text="Single workload spike example diagram." lightbox="media/elastic-san-performance/scenario_two.png":::
+:::image type="content" source="media/elastic-san-performance/one-workload-spike.png" alt-text="Single workload spike example diagram." lightbox="media/elastic-san-performance/one-workload-spike.png":::
 
 ### All workloads spike
 
@@ -110,7 +110,7 @@ It's important to know the behavior of a SAN in the worst case scenario, where e
 
 In this scenario, all the workloads hit their spike at almost the same time. At this point, the total IOPS required by all the workloads combined (64,000 + 45,000 + 40,000 + 5,000) is more than the IOPS provisioned at the SAN level (135,000). So the workloads are throttled. Throttling happens on a first-come, first-served basis, so whichever workloads request IOPS after the max capacity has been reached doesn't get more performance. In this case, workload 1 requested 40,000 IOPS after the other workloads, the SAN had already allocated most of its available IOPS, so only the remaining IOPS was provided.
 
-:::image type="content" source="media/elastic-san-performance/scenario_three.png" alt-text="All workloads spiking example diagram." lightbox="media/elastic-san-performance/scenario_three.png":::
+:::image type="content" source="media/elastic-san-performance/all-workload-spike.png" alt-text="All workloads spiking example diagram." lightbox="media/elastic-san-performance/all-workload-spike.png":::
 
 ## Next steps