Update migrate-to-trusted-launch-virtual-machines-using-azure-migrate.md

Author: Dhananjayanr98

articles/migrate/migrate-to-trusted-launch-virtual-machines-using-azure-migrate.md

@@ -1,6 +1,6 @@
 ---
 title: Migrate Generation 2 Virtual Machines to Azure Trusted Launch Virtual Machines using Azure Migrate
-description: Use Azure Migrate to migrate on prem Generation 2 Virtual Machines to Azure Trusted Launch Virtual Machines
+description: Use Azure Migrate to migrate on premises Generation 2 Virtual Machines to Azure Trusted Launch Virtual Machines
 author: dhananjayanr
 ms.author: dhananjayanr
 ms.topic: how-to
@@ -11,7 +11,7 @@ ms.custom: engagement-fy26
 # Customer intent: "As an IT administrator, I want to migrate servers to Azure Trusted Launch Virtual Machines so that I can ensure enhanced security for my Virtual Machines."
 ---
 
-# Migrate Generation 2 Virtual Machines to Azure Trusted Launch Virtual Machines using Azure Migrate
+# Migrate generation 2 virtual machines to Azure trusted launch virtual machines using Azure Migrate
 
 Azure Migrate now supports migrating Generation 2 virtual machines to Azure Virtual Machines with Trusted Launch. Trusted Launch uses UEFI-based Secure Boot and a virtual Trusted Platform Module (vTPM) to establish a trusted boot chain. This helps ensure that only approved and signed components are loaded during startup, reducing the risk of bootkits, rootkits, and other low-level malware.
 
@@ -24,11 +24,11 @@ Azure Migrate supports all Operating systems that are supported for Trusted Laun
 >Trusted Launch is a security feature for Generation 2 Virtual Machines. Generation 1 Virtual Machines use BIOS and MBR, and they do not support Secure Boot or vTPM by design. As a result, Generation 1 Virtual Machines cannot use Trusted Launch and Azure migrate does not support migrating Gen 1 Virtual Machines to Trusted Launch virtual Machines
 
 ## Secure boot
-At the root of Trusted Launch is Secure Boot. Secure Boot is implemented in platform firmware and protects virtual machines from malware such as bootkits and rootkits.Secure Boot ensures that only signed operating systems and drivers can start. It establishes a trusted boot chain for the virtual machine. When Secure Boot is enabled, all operating system boot components—including the boot loader, kernel, and kernel drivers—must be signed by trusted publishers. Both Windows and supported Linux distributions support Secure Boot. If Secure Boot can't verify a trusted signature, the virtual machine fails to boot.
+At the root of Trusted Launch is Secure Boot. Secure Boot is implemented in platform firmware and protects virtual machines from malware such as bootkits and rootkits. Secure Boot ensures that only signed operating systems and drivers can start. It establishes a trusted boot chain for the virtual machine. When Secure Boot is enabled, all operating system boot components—including the boot loader, kernel, and kernel drivers—must be signed by trusted publishers. Both Windows and supported Linux distributions support Secure Boot. If Secure Boot can't verify a trusted signature, the virtual machine fails to boot.
 
 >[!Note]
 >Secure Boot is configured as part of the Trusted Launch settings on the target Virtual Machine and isn’t inherited from the source Virtual Machine. Even if Secure Boot was enabled on the source Virtual Machine, it isn’t automatically enabled on the migrated Trusted Launch Virtual Machine. You must explicitly enable Secure Boot in the Trusted Launch configuration during migration.
 
-## How to migrate to trusted launch Virtual Machines using azure migrate:
+## How to migrate to trusted launch virtual machines using Azure Migrate
 This guide explains how to migrate your workloads to Trusted Launch Virtual Machines using Azure Migrate. For more information, See [How to migrate to trusted launch virtual machines using Azure Migrate](tutorial-migrate-vmware.md).