removed orphaned images

Author: Michael Bender

articles/load-balancer/distribution-mode-concepts.md

@@ -5,7 +5,7 @@ author: mbender-ms
 ms.author: mbender
 ms.service: azure-load-balancer
 ms.topic: conceptual 
-ms.date: 06/26/2024
+ms.date: 09/25/2024
 ms.custom: template-concept 
 #Customer intent: As a administrator, I want to learn about the different distribution modes of Azure Load Balancer so that I can configure the distribution mode for my application.
 ---
@@ -35,11 +35,10 @@ The five-tuple consists of:
 * **Protocol type**
 
 The hash is used to route traffic to healthy backend instances within the backend pool. The algorithm provides stickiness only within a transport session. When the client starts a new session from the same source IP, the source port changes and causes the traffic to go to a different backend instance.
-In order to configure hash based distribution, you must select session persistence to be **None** in the Azure portal. This specifies that successive requests from the same client can be handled by any virtual machine.
 
-![Hash-based distribution](./media/load-balancer-overview/load-balancer-distribution.png)
+In order to configure hash based distribution, you must select session persistence to be **None** in the Azure portal. This specifies that successive requests from the same client can be handled by any virtual machine.
 
-*Figure: Default five-tuple hash based distribution*
+:::image type="content" source="media/load-balancer-overview/load-balancer-distribution.png" alt-text="Diagram illustrating the default five-tuple hash based distribution mode with virtual machines.":::
 
 
 ## Session persistence 

articles/load-balancer/load-balancer-floating-ip.md

@@ -30,7 +30,7 @@ In the diagrams, you see how IP address mapping works before and after enabling
 
 You configure Floating IP on a Load Balancer rule via the Azure portal, REST API, CLI, PowerShell, or other client. In addition to the rule configuration, you must also configure your virtual machine's Guest OS in order to use Floating IP.
 
-:::image type="content" source="media/load-balancer-multivip-overview/load-balancer-multivip-dsr.png" alt-text="Diagram of load balancer traffic for multiple frontend IPs with floating IP.":::
+:::image type="content" source="media/load-balancer-floating-ip/load-balancer-multivip-dsr.png" alt-text="Diagram of load balancer traffic for multiple frontend IPs with floating IP.":::
 
 For this scenario, every VM in the backend pool has three network interfaces:
 

articles/load-balancer/load-balancer-standard-virtual-machine-scale-sets.md

@@ -32,7 +32,7 @@ When Virtual Machine Scale Sets with [public IPs per instance](/azure/virtual-ma
 
 To create an outbound rule for a backend pool that's already referenced by a load-balancing rule, select **No** under **Create implicit outbound rules** in the Azure portal when the inbound load-balancing rule is created.
 
-  :::image type="content" source="./media/vm-scale-sets/load-balancer-and-vm-scale-sets.png" alt-text="Screenshot that shows load-balancing rule creation." border="true":::
+  :::image type="content" source="./media/load-balancer-standard-virtual-machine-scale-sets/load-balancer-and-vm-scale-sets.png" alt-text="Screenshot that shows load-balancing rule creation." border="true":::
 
 Use the following methods to deploy a Virtual Machine Scale Sets with an existing instance of Load Balancer: