Skip to content

Commit 921b5b6

Browse files
authored
Update tutorial-migrate-physical-virtual-machines.md
Corrected typo (drop down)
1 parent 634b17f commit 921b5b6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/migrate/tutorial-migrate-physical-virtual-machines.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -207,7 +207,7 @@ Now, select machines for migration.
207207
208208
8. In **Target settings**, select the subscription, and target region to which you'll migrate, and specify the resource group in which the Azure VMs will reside after migration.
209209
9. In **Virtual Network**, select the Azure VNet/subnet to which the Azure VMs will be joined after migration.
210-
10. In **Cache storage account**, keep the default option to use the cache storage account that is automatically created for the project. Use the drop down if you'd like to specify a different storage account to use as the cache storage account for replication. <br/>
210+
10. In **Cache storage account**, keep the default option to use the cache storage account that is automatically created for the project. Use the dropdown if you'd like to specify a different storage account to use as the cache storage account for replication. <br/>
211211
>[!NOTE]
212212
> - If you selected private endpoint as the connectivity method for the Azure Migrate project, grant the Recovery Services vault access to the cache storage account. [**Learn more**](migrate-servers-to-azure-using-private-link.md#grant-access-permissions-to-the-recovery-services-vault)
213213
> - To replicate using ExpressRoute with private peering, create a private endpoint for the cache storage account. [**Learn more**](migrate-servers-to-azure-using-private-link.md#create-a-private-endpoint-for-the-storage-account-1)

0 commit comments

Comments
 (0)