edit pass: nvme-articles

ShawnJackson · ShawnJackson · commit 94fa5fcd6631 · 2024-06-28T13:31:31.000-05:00
diff --git a/articles/virtual-machines/enable-nvme-faqs.yml b/articles/virtual-machines/enable-nvme-faqs.yml
@@ -27,7 +27,7 @@ sections:
       - question: |
           How do Azure Boost and NVMe improve the performance of the VMs that Azure offers?
         answer: |
-          Azure Boost is a Microsoft-designed system that offloads server virtualization processes traditionally performed by the hypervisor and host operating system (OS) onto purpose-built software and hardware. Offloading these processes enables faster storage and networking performance for Azure VM customers.
+          Azure Boost is a Microsoft-designed system that offloads server virtualization processes traditionally performed by the hypervisor and host OS onto purpose-built software and hardware. Offloading these processes enables faster storage and networking performance for Azure VM customers.
           
           One of the primary advantages of Azure Boost is its ability to enhance the throughput of Azure managed disks and local storage. This enhancement is enabled by offloading the storage processing tasks to hardware that's dedicated for Azure Boost.
           
diff --git a/articles/virtual-machines/enable-nvme-interface.md b/articles/virtual-machines/enable-nvme-interface.md
@@ -13,13 +13,13 @@ ms.custom: template-how-to-pattern
 > [!NOTE]
 > This article references CentOS, a Linux distribution that's nearing the end of support. Consider your use and plan accordingly. For more information, see the [guidance for CentOS end of support](~/articles/virtual-machines/workloads/centos/centos-end-of-life.md).
 
-The following lists provide up-to-date information on which operating system (OS) images are tagged as supported for remote NVM Express (NVMe).
+The following lists provide up-to-date information on which OS images are tagged as supported for remote NVM Express (NVMe).
 
 For specifics about which virtual machine (VM) generations support which storage types, check the [documentation about VM sizes in Azure](/azure/virtual-machines/sizes).
 
 For more information about enabling the NVMe interface on virtual machines created in Azure, review the [FAQ for remote NVMe disks](/azure/virtual-machines/enable-nvme-remote-faqs).
 
-## Linux
+## Supported Linux OS images
 
 | Distribution                         | Image                                                            |
 |--------------------------------------|------------------------------------------------------------------|
@@ -46,7 +46,7 @@ For more information about enabling the NVMe interface on virtual machines creat
 |     SLES 15.4                        |   SUSE:sles-15-sp4:gen2:latest                                   |
 |     SLES 15.5                        |   SUSE:sles-15-sp5:gen2:latest                                   |
 
-## Windows
+## Supported Windows OS images
 
 - [Azure portal - Plan ID: 2019-datacenter-core-smalldisk](https://portal.azure.com/#create/Microsoft.smalldiskWindowsServer2019DatacenterServerCore)
 - [Azure portal - Plan ID: 2019-datacenter-core-smalldisk-g2](https://portal.azure.com/#create/Microsoft.smalldiskWindowsServer2019DatacenterServerCore2019-datacenter-core-smalldisk-g2)
diff --git a/articles/virtual-machines/enable-nvme-remote-faqs.yml b/articles/virtual-machines/enable-nvme-remote-faqs.yml
@@ -22,7 +22,7 @@ sections:
           To enable the NVMe interface on your VM, you must meet the following prerequisites:
 
           - Choose a VM family that supports NVMe. Only Ebsv5 and Ebdsv5 VM sizes are equipped with NVMe in the Intel v5 generation VMs.
-          - [Select the operating system (OS) image](/azure/virtual-machines/enable-nvme-interface) that's tagged with NVMe support. After you select a supported **VM family and OS image** value, you're prompted to select the NVMe disk controller type.
+          - [Select the operating system image](/azure/virtual-machines/enable-nvme-interface) that's tagged with NVMe support. After you select a supported **VM family and OS image** value, you're prompted to select the NVMe disk controller type.
 
             :::image type="content" source="./media/enable-nvme/nvme-faq-1.png" alt-text="Screenshot of a prompt to select a disk controller type.":::
 
@@ -49,7 +49,7 @@ sections:
           To resize the VM, use the following command to run an [Azure PowerShell script](https://github.com/Azure/SAP-on-Azure-Scripts-and-Utilities/tree/main/NVMe-Preflight-Check) that sets the destination `discontrollertype` value of the VM as NVMe: 
                    
           ```PowerShell
-          `azure-nvme-VM-update.ps1 [-subscription_id] <String> [-resource_group_name] <String> [-vm_name] <String> [[-disk_controller_change_to] <String>] [-vm_size_change_to] <String> [[-start_vm_after_update] <Boolean>] [[-write_logfile] <Boolean>]`
+          azure-nvme-VM-update.ps1 [-subscription_id] <String> [-resource_group_name] <String> [-vm_name] <String> [[-disk_controller_change_to] <String>] [-vm_size_change_to] <String> [[-start_vm_after_update] <Boolean>] [[-write_logfile] <Boolean>]
           ```
       - question: |
           How can I check if an image is tagged as NVMe? 
@@ -67,7 +67,7 @@ sections:
           1. Upload an NVMe-supported virtual hard disk (VHD) to your storage account. [AzCopy](https://docs.microsoft.com/azure/storage/common/storage-use-azcopy-v10) is a fast way, but you can also use the portal to upload.
             
              ```
-             `azcopy copy <local path to your VHD> <container in your storage account>`
+             azcopy copy <local path to your VHD> <container in your storage account>
              ```
 
           2. [Create an image gallery](https://docs.microsoft.com/azure/virtual-machines/create-gallery) by using Azure PowerShell, the portal, or the Azure CLI.
@@ -77,15 +77,15 @@ sections:
              Here's an Azure CLI example:
             
              ```
-             `az sig image-definition create --resource-group <resourceGroupName> --gallery-name <galleryName> --gallery-image-definition <imageName> --publisher <publisher> --offer <offerName> --sku <skuName> --os-type <osType> --os-state <osState> --feature DiskControllerTypes=SCSI,NVMe`
+             az sig image-definition create --resource-group <resourceGroupName> --gallery-name <galleryName> --gallery-image-definition <imageName> --publisher <publisher> --offer <offerName> --sku <skuName> --os-type <osType> --os-state <osState> --feature DiskControllerTypes=SCSI,NVMe
              ```
 
           4. [Create the image version](https://docs.microsoft.com/azure/virtual-machines/image-version) under the NVMe-tagged gallery with the NVMe-supported VHD.
             
              Here's an Azure CLI example:
             
              ```
-             `az sig image-version create --resource-group <resourceGroupName> --gallery-name <galleryName> --gallery-image-definition <imageName> --gallery-image-version <version> --target-regions <region1> <region2> --replica-count <replicaCount> --os-vhd-uri <NVMe-supported vhd uri> --os-vhd-storage-account <storageAccount>`
+             az sig image-version create --resource-group <resourceGroupName> --gallery-name <galleryName> --gallery-image-definition <imageName> --gallery-image-version <version> --target-regions <region1> <region2> --replica-count <replicaCount> --os-vhd-uri <NVMe-supported vhd uri> --os-vhd-storage-account <storageAccount>
              ```  
       - question: |
           How do I configure an ARM template for VM creation?
@@ -111,12 +111,12 @@ sections:
           1. Get the `nvme-cli` package: 
             
              ```
-             `sudo apt install nvme-cli`
+             sudo apt install nvme-cli
              ```
           2. Run the NVMe `list` command to fetch NVMe disk details:
 
              ```
-             `sudo nvme list`
+             sudo nvme list
              ``` 
                          
              :::image type="content" source="./media/enable-nvme/nvme-faq-4.png" alt-text="Screenshot of instructions to identify NVMe disks on a Linux virtual machine.":::
@@ -129,7 +129,7 @@ sections:
       - question: |
           How can I identify NVMe disks on a Windows VM?  
         answer: |
-          Open PowerShell and use the following command: 
+          Open Azure PowerShell and use the following command: 
           
           ```
           wmic diskdrive get model,scsilogicalunit
diff --git a/articles/virtual-machines/enable-nvme-temp-faqs.yml b/articles/virtual-machines/enable-nvme-temp-faqs.yml
@@ -20,7 +20,7 @@ sections:
           To enable the temporary NVMe (temp NVMe) interface on your VM, you must meet the following prerequisites:
           
           - Choose a VM family that supports NVMe (such as v6 VMs). 
-          - Select the operating system (OS) image that's tagged with NVMe support.
+          - Select the operating system image that's tagged with NVMe support.
           - Make sure that you're using a Generation 2 VM, because NVMe supports only Generation 2 images.          
       - question: |
           How are temp NVMe disks in my Dl/D/E_v6 VMs different from remote NVMe disks?
@@ -33,19 +33,19 @@ sections:
       - question: |
           What changes should I prepare for when configuring my VMs with temp NVMe disks?
         answer: |
-          - Disks should be initialized and formatted after the VM starts up. After user-initiated stops, deallocatations, or planned maintenance and Azure-initiated automatic recovery events, the VMs start up with only raw temp NVMe disks. No temp NVMe disks are visible to applications until after they're initialized and formatted. 
+          - Disks should be initialized and formatted after the VM starts up. After user-initiated stops, deallocations, or planned maintenance and Azure-initiated automatic recovery events, the VMs start up with only raw temp NVMe disks. No temp NVMe disks are visible to applications until after they're initialized and formatted. 
           - You can span separate NVMe drives into one as needed after the VM starts up.
           - A Windows pagefile is placed on persistent OS disks (unless you're using the ephemeral OS feature), but you can move it to temp NVMe disks as needed after the VM starts up.
           - The ephemeral OS feature, if you use it, converts one or several NVMe disks (depending on the VM and image size) into a slower SCSI/VHD-based disk, similar to how it was on v5 and older VMs. For the larger VM sizes, the remaining drives stay as raw unformatted NVMe.
-          - The [list of resource SKUs in the REST API](https://learn.microsoft.com/en-us/rest/api/compute/resource-skus/list?tabs=HTTP) exposes several capabilities of virtual machines. The next iteration of VM sizes uses the faster and more efficient NVMe protocol for local storage, instead of the SCSI protocol that earlier virtual machine sizes use.
+          - The [list of resource SKUs in the REST API](https://learn.microsoft.com/en-us/rest/api/compute/resource-skus/list?tabs=HTTP) exposes several capabilities of virtual machines. The next iteration of VM sizes uses the faster and more efficient NVMe protocol for local storage, instead of the SCSI protocol that earlier VM sizes use.
           
             For Azure virtual machines, SCSI-based local storage is a temporary resource disk, and the `MaxResourceVolumeMB` value specifies the size of this disk. In contrast, the `NVMeDiskSizeInMiB` value specifies the size of NVMe-based local storage. 
       - question: |
           How can I encrypt my temp NVMe disks?
         answer: |
           Temp NVMe disks support the feature of data encryption at rest. A unique data encryption key (DEK) encrypts the data for each temp NVMe disk assigned to the VM. A key encryption key (KEK) helps protect the DEK. When you delete a VM, the data on its temp NVMe disk is cryptographically erased. 
       - question: |
-          How can I resize a v5 or older VM with temp disk to v6?
+          How can I resize a v5 or older VM with a temp disk to v6?
         answer: |
           See the [FAQ for Azure VM sizes with no local temporary disk](/azure/virtual-machines/azure-vms-no-temp-disk#how-do-i-migrate-from-a-vm-size-with-local-temp-disk-to-a-vm-size-with-no-local-temp-disk---).
       - question: |
@@ -96,9 +96,9 @@ sections:
           
              :::image type="content" source="./media/enable-nvme/nvme-temp-init-7.png" alt-text="Screenshot of completing the New Simple Volume Wizard.":::
           
-          6. Confirm that the formatted and initialized NVMe disks appear in the Windows Disk Management utility, similar to how **New Volume (E:)** appears in this example.
+          6. Confirm that the formatted and initialized NVMe disks appear in the Windows Disk Management tool, similar to how **New Volume (E:)** appears in this example.
           
-             :::image type="content" source="./media/enable-nvme/nvme-temp-init-8.png" alt-text="Screenshot of the Disk Management utility showing a new volume.":::
+             :::image type="content" source="./media/enable-nvme/nvme-temp-init-8.png" alt-text="Screenshot of the Disk Management tool showing a new volume.":::
           
           ### Azure PowerShell script
           
@@ -405,6 +405,6 @@ sections:
         answer: |
           Temp NVMe disks attached to V6 VMs are ephemeral, similar to temp drives on other VM series. This means that you lose all data on the VM after redeployment or during a maintenance event. For more information on maintenance events and downtime, see [Understand VM reboots: Maintenance vs. downtime](https://learn.microsoft.com/en-us/azure/virtual-machines/understand-vm-reboots).
           
-          If the VM moved to new hardware, these drives unmount, and new unmounted disks are presented to the operating system when it comes back up. If the VM didn't change hardware, the temp NVME disks might still be present. The preceding script for mounting the drives checks for unmounted drives before it tries to mount. 
+          If the VM moved to new hardware, these drives unmount, and new unmounted disks are presented to the operating system when it comes back up. If the VM didn't change hardware, the temp NVMe disks might still be present. The preceding script for mounting the drives checks for unmounted drives before it tries to mount. 
           
           It's a best practice to run the mounting script automatically every time the VM starts and delay any other startup scripts that need the drives until after the mounting script finishes running.
