fixed image alt texts

Author: jjaygbay

articles/azure-vmware/migrate-sql-server-always-on-cluster.md

@@ -121,7 +121,7 @@ For details about configuring and managing the quorum, see [Failover Clustering
           :::image type="content" source="media/sql-server-hybrid-benefit/sql-always-on-7.png" alt-text="Diagram showing availability Group Dashboard with new primary replica and all migrated secondary replicas in synchronized state." border="false":::
     1. Edit the **Properties** of the availability group and set **Failover Mode** to **Automatic** in all replicas.
 
-       :::image type="content" source="media/sql-server-hybrid-benefit/sql-alwayson-8.png" alt-text="Diagram showing a setting for failover back to Automatic for all replicas." border="false":::
+       :::image type="content" source="media/sql-server-hybrid-benefit/sql-always-on-8.png" alt-text="Diagram showing a setting for failover back to Automatic for all replicas." border="false":::
 
 ## Next steps 
 

articles/azure-vmware/migrate-sql-server-standalone-cluster.md

@@ -18,7 +18,7 @@ When migrating Microsoft SQL Server Standalone to Azure VMware Solution, VMware
 
 In both cases, consider the size and criticality of the database being migrated. For this how-to procedure, we have validated VMware the HCX vMotion. HCX Cold Migration is also valid, but it requires a longer downtime period. 
 
-:::image type="content" source="media/sql-server-hybrid-benefit/migrated-sql-stand-alone-cluster.png" alt-text="Diagram showing the architecture of standalone SQL server for  Azure VMware Solution." border="false"::: 
+:::image type="content" source="media/sql-server-hybrid-benefit/migrated-sql-standalone-cluster.png" alt-text="Diagram showing the architecture of standalone SQL server for  Azure VMware Solution." border="false"::: 
 
 ## Prerequisites