Updated alt image texts

Author: jjaygbay

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

@@ -71,7 +71,7 @@ For details about configuring and managing the quorum, see [Failover Clustering
     1. Select your primary replica and open **Availability Group** **Properties**.
 
 
-          :::image type="content" source="media/sql-server-hybrid-benefit/sql-always-on-1.png" alt-text="Always On Availability Group properties" border="false":::
+          :::image type="content" source="media/sql-server-hybrid-benefit/sql-always-on-1.png" alt-text="Diagram showing Always On Availability Group properties." border="false":::
 
      1. Change **Availability Mode** to **Asynchronous commit** only for the replica to be migrated.
      1. Change **Failover Mode** to **Manual** for every member of the availability group.
@@ -89,26 +89,26 @@ For details about configuring and managing the quorum, see [Failover Clustering
       1. Click **Go** and the migration will initiate. 
 1. Once the migration has been completed, access the migrated replica and verify connectivity with the rest of the members in the availability group.
 1. In SQL Server Management Studio, open the **Availability Group Dashboard** and verify that the replica appears as **Online**. 
-      :::image type="content" source="media/sql-server-hybrid-benefit/sql-always-on-2.png" alt-text="Always On Availability Group Dashboard." border="false":::
+      :::image type="content" source="media/sql-server-hybrid-benefit/sql-always-on-2.png" alt-text="Diagram showing Always On Availability Group Dashboard." border="false":::
 
    1. **Data Loss** status in the **Failover Readiness** column is expected since the replica has been out-of-sync with the primary during the migration. 
 1. Edit the **Availability Group** **Properties** again and set **Availability Mode** back to **Synchronous commit**.
       1. The secondary replica will start to synchronize back all the changes made to the primary replica during the migration. Wait until it appears in Synchronized state. 
 1. From the **Availability Group Dashboard** in SSMS click on **Start Failover Wizard**.
 1. Select the migrated replica and click **Next**.
 
-    :::image type="content" source="media/sql-server-hybrid-benefit/sql-always-on-3.png" alt-text="New primary replica selection for failover." border="false":::
+    :::image type="content" source="media/sql-server-hybrid-benefit/sql-always-on-3.png" alt-text="Diagram showing new primary replica selection for always on." border="false":::
 
 1. Connect to the replica in the next screen with your DB admin credentials.
-    :::image type="content" source="media/sql-server-hybrid-benefit/sql-alwayson-4.png" alt-text="New primary replica admin credentials connection." border="false":::
+    :::image type="content" source="media/sql-server-hybrid-benefit/sql-always-on-4.png" alt-text="Diagram showing new primary replica admin credentials connection." border="false":::
 
 1. Review the changes and click **Finish** to start the failover operation.
 
-    :::image type="content" source="media/sql-server-hybrid-benefit/sql-always-on-5.png" alt-text="Availability Group failover operation review." border="false":::
+    :::image type="content" source="media/sql-server-hybrid-benefit/sql-always-on-5.png" alt-text="Diagram showing Availability Group always on operation review." border="false":::
 
 
 1. Monitor the progress of the failover in the next screen, and click **Close** when the operation is finished.
-    :::image type="content" source="media/sql-server-hybrid-benefit/sql-always-on-6.png" alt-text="Failover successfully finished." border="false"::: 
+    :::image type="content" source="media/sql-server-hybrid-benefit/sql-always-on-6.png" alt-text="Diagram showing that always on SQL server cluster successfully finished." border="false"::: 
 
 
 1. Refresh the **Object Explorer** view in SQL Server Management Studio (SSMS), and verify that the migrated instance is now the primary replica.
@@ -118,10 +118,10 @@ For details about configuring and managing the quorum, see [Failover Clustering
     > Migrate one replica at a time and verify that all changes are synchronized back to the replica after each migration. Do not migrate all the replicas at the same time using **HCX Bulk Migration**. 
 1. After the migration of all the replicas is completed, access your Always-On availability group with **SQL Server Management Studio**.
     1. Open the Dashboard and verify there is no data loss in any of the replicas and that all are in a     **Synchronized** state.
-          :::image type="content" source="media/sql-server-hybrid-benefit/sql-always-on-7.png" alt-text="Availability Group Dashboard with new primary replica and all migrated secondary replicas in synchronized state." border="false":::
+          :::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="Set Failover back to Automatic for all replicas." border="false":::
+       :::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":::
 
 ## Next steps 
 

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

@@ -75,11 +75,11 @@ For illustration purposes, in this document we're using a two-node cluster with
 1. Access the first node of the cluster and open **Failover Cluster Manager**.
     1. Verify that the second node is in **Offline** state and that all clustered services and storage are under the control of the first node.
 
-         :::image type="content" source="media/sql-server-hybrid-benefit/sql-failover-1.png" alt-text="Windows Server Failover Cluster Manager cluster storage verification." border="false":::
+         :::image type="content" source="media/sql-server-hybrid-benefit/sql-failover-1.png" alt-text="Diagram showing Windows Server Failover Cluster Manager cluster storage verification." border="false":::
 
     1. Shut down the cluster.
 
-        :::image type="content" source="media/sql-server-hybrid-benefit/failover-2.png" alt-text="Shut down your cluster using Windows Server Failover Cluster Manager." border="false":::
+        :::image type="content" source="media/sql-server-hybrid-benefit/sql-failover-2.png" alt-text="Diagram showing a shut down cluster using Windows Server Failover Cluster Manager." border="false":::
 
      1. Check that all cluster services are successfully stopped without errors.
 1. Shut down first node of the cluster.
@@ -111,17 +111,17 @@ For illustration purposes, in this document we're using a two-node cluster with
 1. Access the first node VM with **VMware Remote Console**.
        1. Verify virtual machine network configuration and ensure it can reach on-premises and Azure resources. 
        1. Open **Failover Cluster Manager** and verify cluster services.
-       :::image type="content" source="media/sql-server-hybrid-benefit/failover-3.png" alt-text="Cluster summary in Failover Cluster Manager." border="false":::
+       :::image type="content" source="media/sql-server-hybrid-benefit/sql-failover-3.png" alt-text="Diagram showing a cluster summary in Failover Cluster Manager." border="false":::
 
 1. Power on the second node virtual machine.
 1. Access the second node VM from the **VMware Remote Console**.
    1. Verify that Windows Server can reach the storage.
    1. In the **Failover Cluster Manager** review that the second node appears as **Online** status.
-    :::image type="content" source="media/sql-server-hybrid-benefit/failover-4.png"  alt-text="Cluster node status in Failover Cluster Manager." border="false":::
+    :::image type="content" source="media/sql-server-hybrid-benefit/sql-failover-4.png"  alt-text="Diagram showing a cluster node status in Failover Cluster Manager." border="false":::
 
 1. Using the **SQL Server Management Studio** connect to the SQL Server cluster resource network name. Check the database is online and accessible.
 
-:::image type="content" source="media/sql-server-hybrid-benefit/fail-over-5.png" alt-text="SQL Server Management Studio connection verification to the migrated cluster instance database." border="false":::
+:::image type="content" source="media/sql-server-hybrid-benefit/sql-failover-5.png" alt-text="Diagram showing a verification of SQL Server Management Studio connection  to the migrated cluster instance database." border="false":::
 
 Finally, check the connectivity to SQL from other systems and applications in your infrastructure and verify that all applications using the database(s) can still access them. 
 

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

@@ -66,7 +66,7 @@ The table below indicates the estimated downtime for each Microsoft SQL Server t
 
 
 
-    :::image type="content" source="media/sql-server-hybrid-benefit/sql-standalone-1.png" alt-text="SQL Server Management Studio connection to the migrated database." border="false":::  
+    :::image type="content" source="media/sql-server-hybrid-benefit/sql-standalone-1.png" alt-text="Diagram showing a SQL Server Management Studio connection to the migrated database." border="false":::  
 
 ## Next steps