Merge pull request #124824 from joasa123/patch-3

Minor fixes as per ABRS KM project review.

Author: Court72

articles/migrate/migrate-servers-to-azure-using-private-link.md

@@ -235,7 +235,7 @@ With discovery completed, you can begin replication of Hyper-V VMs to Azure.
     > You can update replication settings any time before replication starts, **Manage** > **Replicating machines**. Settings can't be changed after replication starts. 
 
     Next, follow the instructions to [perform migrations](tutorial-migrate-hyper-v.md#migrate-vms). 
-]
+
 ### Grant access permissions to the Recovery Services vault
 
 You must grant the permissions to the Recovery Services vault for authenticated access to the cache/replication storage account.

articles/migrate/vmware/prepare-for-agentless-migration.md

@@ -16,7 +16,7 @@ ms.custom: vmware-scenario-422, engagement-fy23, linux-related-content
 
 This article provides an overview of the changes performed when you [migrate VMware VMs to Azure via the agentless migration](./tutorial-migrate-vmware.md) method using the Migration and modernization tool.
 
-Before you migrate your on-premises VM to Azure, you may require a few changes to make the VM ready for Azure. These changes are important to ensure that the migrated VM can boot successfully in Azure and connectivity to the Azure VM can be established-.
+Before you migrate your on-premises VM to Azure, you may require a few changes to make the VM ready for Azure. These changes are important to ensure that the migrated VM can boot successfully in Azure and connectivity to the Azure VM can be established.
 Azure Migrate automatically handles these configuration changes for the following operating system versions for both Linux and Windows. This process is called *Hydration*.
 
 **Operating system versions supported for hydration**