minor edits

Author: habibaum

articles/migrate/azure-migrate-unsupported-regions.md

@@ -23,20 +23,20 @@ Azure provides multiple methods to facilitate seamless migration to a new region
 
 ### Agentless migration for VMware (recommended)
 
-- Migrate VMware VMs without using an agent by utilizing the Migration and Modernization tool. See, [Azure Migrate documentation](vmware/tutorial-migrate-vmware.md).
+- VMware Virtual Machiness without using an agent by utilizing the Migration and Modernization tool. See, [Azure Migrate documentation](vmware/tutorial-migrate-vmware.md).
 - When using Azure Migrate’s replication wizard for the first time, specify the *new region* as the target region for migration.
 - Create the storage account used for replication in the new region.
 - For private endpoint configurations, manually create and configure the storage account in the new region with a Private Endpoint and associate it with the migration project.
 
 ### Agent-based migration
 
-- **VMware**: Migrate VMware vSphere VMs using the agent-based Migration and Modernization tool. See, [Azure Migrate documentation](vmware/tutorial-migrate-vmware-agent.md).
-- **Hyper-V**: Migrate Hyper-V VMs to Azure using the Migration and Modernization tool. See, [Azure Migrate documentation](tutorial-migrate-hyper-v.md).
+- **VMware**: Migrate VMware vSphere Virtual Machines using the agent-based Migration and Modernization tool. See, [Azure Migrate documentation](vmware/tutorial-migrate-vmware-agent.md).
+- **Hyper-V**: Migrate Hyper-V Virtual Machines to Azure using the Migration and Modernization tool. See, [Azure Migrate documentation](tutorial-migrate-hyper-v.md).
 - **Physical machines**: Migrate physical servers to Azure using the Migration and Modernization tool. See, [Azure Migrate documentation](tutorial-migrate-physical-virtual-machines.md).
 
 ## Known issues
 
-This section outlines known issues related to migrating virtual machines (VMs) to a new region using Azure’s agentless and agent-based migration methods. The information is provided to assist users in troubleshooting errors that may occur during these processes.
+This section outlines known issues related to migrating virtual machines to a new region using Azure’s agentless and agent-based migration methods. The information is provided to assist users in troubleshooting errors that may occur during these processes.
 
 **Agentless Migration**
 
@@ -48,11 +48,11 @@ Provided location - isn't available for resource type:
 
 This error happens because the deployment scripts functionality might not be available when the region launches. However, retrying the replication process after a short interval should fix the issue.
 
-**SQL VM registration error** 
+**SQL Virtual Machine registration error** 
 
-When migrating a VM with SQL Server, if you select the option to register with the SQL VM resource provider, you encounter the following error:
+When migrating a Virtual Machine with SQL Server, if you select the option to register with the SQL Virtual Machine resource provider, you encounter the following error:
 
-The virtual machine couldn't be registered with the SQL VM Resource Provider. Azure error message: 'No registered resource provider found for location '' and API version '2017-03-01-preview' for type 'Locations/registerSqlVmCandidate'. The supported api-versions are '2017-03-01-preview, 2021-11-01-preview, 2022-02-01-preview, 2022-02-01, 2022-07-01-preview, 2022-08-01-preview, 2023-01-01-preview, 2023-10-01'. The supported locations are 'australiacentral, australiacentral2, australiaeast, australiasoutheast, brazilsouth, canadacentral, canadaeast, centralindia, centralus, eastasia, eastus, eastus2, francecentral, francesouth, germanywestcentral, israelcentral, italynorth, japaneast, japanwest, jioindiawest, koreacentral, koreasouth, mexicocentral, northcentralus, northeurope, norwayeast, polandcentral, qatarcentral, southafricanorth, southcentralus, southindia, southeastasia, spaincentral, swedencentral, switzerlandnorth, uaecentral, uaenorth, uksouth, ukwest, westcentralus, westeurope, westindia, westus, westus2, westus3'.
+The virtual machine couldn't be registered with the SQL Virtual Machine Resource Provider. Azure error message: 'No registered resource provider found for location '' and API version '2017-03-01-preview' for type 'Locations/registerSqlVmCandidate'. The supported api-versions are '2017-03-01-preview, 2021-11-01-preview, 2022-02-01-preview, 2022-02-01, 2022-07-01-preview, 2022-08-01-preview, 2023-01-01-preview, 2023-10-01'. The supported locations are 'australiacentral, australiacentral2, australiaeast, australiasoutheast, brazilsouth, canadacentral, canadaeast, centralindia, centralus, eastasia, eastus, eastus2, francecentral, francesouth, germanywestcentral, israelcentral, italynorth, japaneast, japanwest, jioindiawest, koreacentral, koreasouth, mexicocentral, northcentralus, northeurope, norwayeast, polandcentral, qatarcentral, southafricanorth, southcentralus, southindia, southeastasia, spaincentral, swedencentral, switzerlandnorth, uaecentral, uaenorth, uksouth, ukwest, westcentralus, westeurope, westindia, westus, westus2, westus3'.
 
 > [!NOTE]
-> Despite this error, the VM migration succeeds. However, users must know that the VM won't be registered with the SQL VM Resource Provider in the specified region.
+> Despite this error, the Virtual Machine migration succeeds. However, users must know that the Virtual Machine won't be registered with the SQL Virtual Machine Resource Provider in the specified region.