Merge pull request #259741 from Sharmistha-Rai/main

Corrected failover wording

Author: prmerger-automator[bot]

articles/site-recovery/vmware-azure-failback.md

@@ -26,7 +26,7 @@ This article describes how to fail back Azure VMs to an on-premises site, follow
 1. Make sure that Azure VMs are reprotected and replicating to the on-premises site.
     - A VM needs at least one recovery point in order to fail back.
     - If you fail back a recovery plan, then all machines in the plan should have at least one recovery point.
-2. In the vault > **Replicated items**, select the VM. Right-click the VM > **Unplanned Failover**.
+2. In the vault > **Replicated items**, select the VM. Right-click the VM > **Failover**.
 3. In **Confirm Failover**, verify the failover direction (from Azure).
 4. Select the recovery point that you want to use for the failover.
     - We recommend that you use the **Latest** recovery point. The app-consistent point is behind the latest point in time, and causes some data loss.

articles/site-recovery/vmware-physical-mobility-service-overview.md

@@ -232,6 +232,7 @@ See information about [upgrading the mobility services](upgrade-mobility-service
 
 - Ensure that all server configurations meet the criteria in the [Support matrix for disaster recovery of VMware VMs and physical servers to Azure](vmware-physical-azure-support-matrix.md).
 - [Locate the installer](#locate-installer-files) for the server's operating system.
+- Copy the installer corresponding to the source machine’s operating system and place it on your source machine in a local folder, such as C:\Program Files (x86)\Microsoft Azure Site Recovery.
 
 >[!IMPORTANT]
 > Don't use the UI installation method if you're replicating an Azure Infrastructure as a Service (IaaS) VM from one Azure region to another. Use the [command prompt](#install-the-mobility-service-using-command-prompt-classic) installation.