edit pass: nvme-articles

ShawnJackson · ShawnJackson · commit c2520ba37083 · 2024-06-28T11:08:56.000-05:00
diff --git a/articles/virtual-machines/enable-nvme-remote-faqs.yml b/articles/virtual-machines/enable-nvme-remote-faqs.yml
@@ -17,18 +17,18 @@ sections:
       - question: |
           What are the prerequisites to enable the remote NVMe interface on my VM?
         answer: |
-          You can use `DiskControllerType` during virtual machine (VM) configuration to select your preferred controller type as NVM Express (NVMe) or Small Computer System Interface (SCSI). If you don't specify a `DiskControllerType` value, the platform automatically chooses the default controller based on the VM size configuration. If the VM size is configured for SCSI as the default and supports NVMe, the VM will use SCSI unless you update the `DiskControllerType` value to NVMe.
+          You can use `DiskControllerType` during virtual machine (VM) configuration to select your preferred controller type as NVM Express (NVMe) or Small Computer System Interface (SCSI). If you don't specify a `DiskControllerType` value, the platform automatically chooses the default controller based on the VM size configuration. If the VM size is configured for SCSI as the default and supports NVMe, the VM uses SCSI unless you update the `DiskControllerType` value to NVMe.
           
           To enable the NVMe interface on your VM, you must meet the following prerequisites:
 
-           - Choose a VM family that supports NVMe. It's important to note that only Ebsv5 and Ebdsv5 VM sizes are equipped with NVMe in the Intel v5 generation VMs. Be sure to select either one of the series, Ebsv5 or Ebdsv5.
-           - [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.
+          - 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 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.":::
+            :::image type="content" source="./media/enable-nvme/nvme-faq-1.png" alt-text="Screenshot of a prompt to select a disk controller type.":::
 
-           - Opt in to NVMe by selecting the NVMe disk controller type in the Azure portal or in the Azure Resource Manager, Azure CLI, or Azure PowerShell template. For step-by-step instructions, refer to the [general NVMe FAQ](/azure/virtual-machines/enable-nvme-faqs).
-           - Make sure that you're using a Generation 2 VM, because NVMe supports only Generation 2 images.
-           - Choose one of the Azure regions where NVMe is enabled.      
+          - Opt in to NVMe by selecting the NVMe disk controller type in the Azure portal or in the Azure Resource Manager, Azure CLI, or Azure PowerShell template. For step-by-step instructions, refer to the [general NVMe FAQ](/azure/virtual-machines/enable-nvme-faqs).
+          - Make sure that you're using a Generation 2 VM, because NVMe supports only Generation 2 images.
+          - Choose one of the Azure regions where NVMe is enabled.      
       - question: |
           Can I encrypt my remote NVMe disks?
         answer: |
@@ -38,13 +38,13 @@ sections:
         answer: |
           You can use the following process to either:
           
-          - Resize a SCSI VM created using an untagged image to an NVMe-enabled VM of a different size without recreating the VM configurations and without tagging the image. 
-          - Resize a SCSI VM to an NVMe-enabled VM of a different size without re-creating the VM configurations.
+          - Resize a SCSI-based VM created using an untagged image to an NVMe-enabled VM of a different size without re-creating the VM configurations and without tagging the image. 
+          - Resize a SCSI-based VM to an NVMe-enabled VM of a different size without re-creating the VM configurations.
           
           The source VM can be either:
           
-          - An untagged OS image that supports NVMe
-          - An NVMe-tagged OS image
+          - An untagged OS image that supports NVMe.
+          - An NVMe-tagged OS image.
           
           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: 
                    
@@ -74,23 +74,23 @@ sections:
           
           3. [Create an image definition](https://docs.microsoft.com/azure/virtual-machines/image-version]). Be sure to include `--feature DiskControllerTypes=SCSI,NVMe`.
             
-            Here's an Azure CLI example:
+             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:
+             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?
         answer: |
-          You can use the Azure Custom Script Extension in conjunction with Azure Resource Manager templates (ARM templates). This solution allows you to download and run scripts on Azure virtual machines and is compatible with both Windows and Linux. For detailed guidance, refer to the Azure Custom Script Extension documentation for [Windows](/azure/virtual-machines/extensions/custom-script-windows) and [Linux](/azure/virtual-machines/extensions/custom-script-linux). 
+          You can use the Azure Custom Script Extension in conjunction with Azure Resource Manager templates (ARM templates). This solution allows you to download and run scripts on Azure virtual machines and is compatible with both Windows and Linux. For detailed guidance, refer to the Azure Custom Script Extension documentation for [Windows](/azure/virtual-machines/extensions/custom-script-windows) and [Linux](/azure/virtual-machines/extensions/custom-script-linux).
       - question: |
           What happens if I want to use another VM family that doesn't support remote NVMe disks?
         answer: |
@@ -104,9 +104,7 @@ sections:
       - question: |
           Does Azure support live resizing on disks with NVMe VM sizes?
         answer: |
-          Live resizing of NVMe is supported on Azure Premium SSD v1 disks, Standard SSD disks, and Standard HDD disks. You can also add NVMe disks without restarting the VM. 
-          
-          Live resizing is also supported on Premium SSD v1, Standard SSD, and Standard HDD disks.
+          Live resizing of NVMe is supported on Azure Premium SSD v1 disks, Standard SSD disks, and Standard HDD disks. You can also add NVMe disks without restarting the VM.
       - question: |
           How can I identify remote NVMe disks on a Linux VM?
         answer: |
@@ -127,7 +125,7 @@ sections:
             
              Here's how the data appears in response to Azure PowerShell commands:
                      
-             :::image type="content" source="./media/enable-nvme/nvme-faq-6.png" alt-text="Screenshot of an example of response to an Azure PowerShell command.":::
+             :::image type="content" source="./media/enable-nvme/nvme-faq-6.png" alt-text="Screenshot of an example response to an Azure PowerShell command.":::
       - question: |
           How can I identify NVMe disks on a Windows VM?  
         answer: |
@@ -139,13 +137,13 @@ sections:
 
           :::image type="content" source="./media/enable-nvme/nvme-faq-7.png" alt-text="Screenshot of an example Powershell command to use NVMe on Windows.":::
         
-          The ASAP attached disks are presented in the guest with the model string `Virtual_Disk NVME Premium`. The SCSI logical unit will have the value for the portal-visible LUN ID incremented by 1.
+          The ASAP attached disks are presented in the guest with the model string `Virtual_Disk NVME Premium`. The SCSI logical unit has the value for the portal-visible LUN ID incremented by 1.
           
           Here's a snapshot of how NVMe disks appear in an NVMe-enabled Windows VM: 
 
           :::image type="content" source="./media/enable-nvme/nvme-faq-8.png" alt-text="Screenshot that shows an example of an Azure PowerShell command to identify the NVMe disk on a Windows VM.":::
 
-          The following snapshot shows a guest output for data disks attached at LUN 0 and LUN 4 (CRP). The LUN ID is equivalent to the namespace ID.
+          The following snapshot shows guest output for data disks attached at LUN 0 and LUN 4 (CRP). The LUN ID is equivalent to the namespace ID.
 
           :::image type="content" source="./media/enable-nvme/nvme-faq-9.png" alt-text="Screenshot that shows an example of how NVMe disks appear in an NVMe-enabled Windows VM.":::
 
