minor edits

Author: habibaum

articles/migrate/hydration-process.md

@@ -22,7 +22,7 @@ Azure Migrate will create the network interface, a new virtual network, subnet,
 
 After the virtual machine is created, Azure Migrate will invoke the [Custom Script Extension](/azure/virtual-machines/extensions/custom-script-windows) on the temporary VM using the Azure Virtual Machine REST API. The Custom Script Extension utility will execute a preparation script containing the required configuration for Azure readiness on the on-premises VM disks attached to the temporary Azure VM. The preparation script is downloaded from an Azure Migrate owned storage account. The network security group rules of the virtual network will be configured to permit the temporary Azure VM to access the Azure Migrate storage account for invoking the script.
 
- :::image type="content" source="./media/concepts-prepare-vmware-agentless-migration/migration-steps.png" alt-text="Image of VMware agentless migration steps." lightbox="./media/oncepts-prepare-vmware-agentless-migration/migration-steps.png":::.
+ :::image type="content" source="./media/concepts-prepare-vmware-agentless-migration/migration-steps.png" alt-text="Image of VMware agentless migration steps." lightbox="./media/concepts-prepare-vmware-agentless-migration/migration-steps.png":::.
 
 >[!NOTE]
 >Hydration VM disks do not support Customer Managed Key (CMK). Platform Managed Key (PMK) is the default option.