Review team fixes

mattmcinnes · mattmcinnes · commit adb0043b9b74 · 2024-05-10T06:53:52.000-07:00
diff --git a/articles/virtual-machines/enable-nvme-faqs.yml b/articles/virtual-machines/enable-nvme-faqs.yml
@@ -61,7 +61,7 @@ sections:
           How can I launch a VM with the NVMe interface?
         answer: |
           NVMe can be enabled during VM creation using various methods such as: Azure portal, CLI, PowerShell, and ARM templates. To create an NVMe VM, you must first enable the NVMe option on a VM and select the NVMe controller disk type for the VM. Note that the NVMe diskcontrollertype can be enabled during creation or updated to NVMe when the VM is stopped and deallocated, provided that the VM size supports NVMe.
-          ### Azure portal View
+          ### Azure portal view
 
           1. Add Disk Controller Filter. To find the NVMe eligible sizes, select **See All Sizes**, select the **Disk Controller** filter, and then select **NVMe**:
 
@@ -75,7 +75,7 @@ sections:
 
               :::image type="content" source="./media/enable-nvme/azure-portal-3.png" alt-text="Screenshot of instructions to review and verify features enablement.":::
 
-  - name: Azure Storage Performance with NVMe Disks
+  - name: Azure storage performance with NVMe disks
     questions:
       - question: |
           What types of workloads benefit from NVMe disks?
diff --git a/articles/virtual-machines/enable-nvme-remote-faqs.yml b/articles/virtual-machines/enable-nvme-remote-faqs.yml
@@ -70,14 +70,14 @@ sections:
           To tag an image that supports NVMe, follow the four steps below: 
           1. Upload NVMe-supported vhd to your storage account. AzCopy is a fast way, but you can also use the portal to upload.
             - AzCopy Reference: 
-                [https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-v10]
+                [https://docs.microsoft.com/azure/storage/common/storage-use-azcopy-v10]
             ```
             `azcopy copy <local path to your vhd> <container in your storage account>`
             ```
           2. Create your image gallery either using powershell/portal/cli:
-            [https://docs.microsoft.com/en-us/azure/virtual-machines/create-gallery]
+            [https://docs.microsoft.com/azure/virtual-machines/create-gallery]
           3. Create the image definition:
-            [https://docs.microsoft.com/en-us/azure/virtual-machines/image-version]
+            [https://docs.microsoft.com/azure/virtual-machines/image-version]
             **Please make sure to include --feature DiskControllerTypes=SCSI,NVMe**
             
             CLI Example:
@@ -86,7 +86,7 @@ sections:
             ```
 
           4. Create the image version under the NVMe-tagged gallery with the NVMe-supported vhd: 
-            [https://docs.microsoft.com/en-us/azure/virtual-machines/image-version]
+            [https://docs.microsoft.com/azure/virtual-machines/image-version]
             
             CLI Example:
             ```
@@ -114,14 +114,21 @@ sections:
       - question: |
           How can I identify remote NVMe disks on a Linux VM?
         answer: |
-          - Get nvme-cli package using the command =” sudo apt install nvme-cli” 
-          - Run NVMe list command =” sudo nvme list “to fetch NVMe disk details:  
+          1. Get nvme-cli package 
+            ```
+            `sudo apt install nvme-cli`
+            ```
+          2. Run NVMe list command to fetch NVMe disk details:
+
+            ```
+            `sudo nvme list`
+            ``` 
                          
              :::image type="content" source="./media/enable-nvme/nvme-faq-4.png" alt-text="Screenshot of instructions to identify NVMe disks on Linux VM.":::
 
             :::image type="content" source="./media/enable-nvme/nvme-faq-5.png" alt-text="Screenshot of instructions to choose namespace ID in Linux portal.":::
             
-            Here's how the data shows in response to Azure PowerShell commands
+            Here's how the data shows 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 Azure PowerShell command.":::
       - question: |
diff --git a/articles/virtual-machines/enable-nvme-temp-faqs.yml b/articles/virtual-machines/enable-nvme-temp-faqs.yml
@@ -62,19 +62,19 @@ sections:
           ### GUI
           >[!TIP]
           > Note: The GUI example below is meant for illustrative purposes. It is recommended that scripts be created to automate this workflow for production deployments.
-          - Press the **Windows key + R** to open the Run dialog box. Type **diskmgmt.msc** and press **Enter**.
+          1. Press the **Windows key + R** to open the Run dialog box. Type **diskmgmt.msc** and press **Enter**.
           :::image type="content" source="./media/enable-nvme/nvme-temp-init-1.png" alt-text="Screenshot of the Run dialog box opening diskmgmt.msc.":::
-          - Select partition style (MBR or GPT) and the disks to be initialized and click on **OK** button.
+          2. Select partition style (MBR or GPT) and the disks to be initialized and click on **OK** button.
           :::image type="content" source="./media/enable-nvme/nvme-temp-init-2.png" alt-text="Screenshot of the Disk Management Initialize Disk dialog box.":::          
-          - Right click on the disk to be partitioned and select **New Simple Volume** menu item.
+          3. Right click on the disk to be partitioned and select **New Simple Volume** menu item.
           :::image type="content" source="./media/enable-nvme/nvme-temp-init-3.png" alt-text="Screenshot of the menu for selecting new volume types.":::
-          - Follow the **New Simple Volume Wizard** in the next few steps to specify items such as Volume size, Drive letter, File system, Volume label, etc. by clicking on the **Next** button to advance through the wizard. 
+          4. Follow the **New Simple Volume Wizard** in the next few steps to specify items such as Volume size, Drive letter, File system, Volume label, etc. by clicking on the **Next** button to advance through the wizard. 
           :::image type="content" source="./media/enable-nvme/nvme-temp-init-4.png" alt-text="Screenshot of specifying the volume size in the New Simple Volume Wizard.":::
           :::image type="content" source="./media/enable-nvme/nvme-temp-init-5.png" alt-text="Screenshot of specifying the drive letter in the New Simple Volume Wizard.":::
           :::image type="content" source="./media/enable-nvme/nvme-temp-init-6.png" alt-text="Screenshot of specifying how to format the partition in the New Simple Volume Wizard.":::
-          - Review your settings and click the **Finish** button to complete the partition and format.
+          5. Review your settings and click the **Finish** button to complete the partition and format.
           :::image type="content" source="./media/enable-nvme/nvme-temp-init-7.png" alt-text="Screenshot of completing the New Simple Volume Wizard.":::
-          - The formatted and initialized NVMe disks will show in the Windows Disk Management utility similar to how the “New Volume (E:)” does in this example.
+          6. The formatted and initialized NVMe disks will show in the Windows Disk Management utility similar to how the “New Volume (E:)” does in this example.
           :::image type="content" source="./media/enable-nvme/nvme-temp-init-8.png" alt-text="Screenshot of Disk Management utility showing the New Volume (E:).":::
           
           ### PowerShell Script – Initialize, format, and assign drive letters
@@ -288,13 +288,13 @@ sections:
           ### GUI
           >[!TIP]
           > Note: The GUI example below is meant for illustrative purposes. It is recommended that scripts be created to automate this workflow for production deployments.be created to automate this workflow for production deployments.
-          - Press the **Windows key + R** to open the Run dialog box. Type **sysdm.cpl** and press **Enter**.
+          1. Press the **Windows key + R** to open the Run dialog box. Type **sysdm.cpl** and press **Enter**.
           :::image type="content" source="./media/enable-nvme/nvme-temp-pagefile-1.png" alt-text="Screenshot of the Run dialog box opening sysdm.cpl.":::
-          - Click on the **Advanced** tab and then click on the **Settings** button under the **Performance** section.
+          2. Click on the **Advanced** tab and then click on the **Settings** button under the **Performance** section.
           :::image type="content" source="./media/enable-nvme/nvme-temp-pagefile-2.png" alt-text="Screenshot of the Performance Settings button highlighted on the Advanced tab of System Properties.":::
-          - In the Performance Options window, click on the **Advanced** tab and then click on the **Change** button under the **Virtual memory** section.
+          3. In the Performance Options window, click on the **Advanced** tab and then click on the **Change** button under the **Virtual memory** section.
           :::image type="content" source="./media/enable-nvme/nvme-temp-pagefile-3.png" alt-text="Screenshot of the Advanced tab of the Performance Options.":::
-          - Uncheck the option that says **“Automatically manage paging file size for all drives”**. If there’s a paging file set to your OS disk, select your OS disk and click on the **No paging file** radio button, and then click on the **Set** button. Select your local temp NVMe drive and click on the **System managed size** radio button, and then click on the **Set** button. Click on **OK** to close all windows.
+          4. Uncheck the option that says **“Automatically manage paging file size for all drives”**. If there’s a paging file set to your OS disk, select your OS disk and click on the **No paging file** radio button, and then click on the **Set** button. Select your local temp NVMe drive and click on the **System managed size** radio button, and then click on the **Set** button. Click on **OK** to close all windows.
           :::image type="content" source="./media/enable-nvme/nvme-temp-pagefile-4.png" alt-text="Screenshot of Virtual Memory dialog box.":::
           
           >[!TIP]
@@ -324,35 +324,35 @@ sections:
       - question: |
           How can I move the Linux swap file from OS disk to a temp NVMe disk?
         answer: |
-          - Select NVMe disk used for swap space
-          ```
-          root@D2adsv6:/ # lsblk -p
-          NAME              MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
-          /dev/nvme1n1      259:0    0   30G  0 disk
-          ├─/dev/nvme1n1p1  259:1    0 29.9G  0 part /
-          └─/dev/nvme1n1p15 259:3    0  106M  0 part /boot/efi
-          /dev/nvme0n1      259:4    0   75G  0 disk
-          ```
-          - Create swap space on the disk
-          ```
-          root@D2adsv6:/ # mkswap /dev/nvme0n1
-          Setting up swapspace version 1, size = 75 GiB (80530632704 bytes)
-          no label, UUID=064bdcfb-86ae-49f3-bf9d-b956493e2a1d
-          ```
-          - Enable the swap space
-          ```
-          root@D2adsv6:/ # swapon /dev/nvme0n1
-          ```
-          - Check the swap space being set up properly
-          ```
-          root@D2adsv6:/ # swapon -s
-          Filename                                Type            Size    Used    Priority
-          /dev/nvme0n1                            partition       78643196        0       -2
-          ```
-          - Append the swap space to /etc/fstab to make it persistent across reboots
-          ```
-          root@D2adsv6:/ # echo '/dev/nvme0n1 swap swap defaults 0 0' >> /etc/fstab 
-          ```
+          1. Select NVMe disk used for swap space
+            ```
+            root@D2adsv6:/ # lsblk -p
+                NAME              MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
+                /dev/nvme1n1      259:0    0   30G  0 disk
+                ├─/dev/nvme1n1p1  259:1    0 29.9G  0 part /
+                └─/dev/nvme1n1p15 259:3    0  106M  0 part /boot/efi
+                /dev/nvme0n1      259:4    0   75G  0 disk
+            ```
+          2. Create swap space on the disk
+            ```
+            root@D2adsv6:/ # mkswap /dev/nvme0n1
+            Setting up swapspace version 1, size = 75 GiB (80530632704 bytes)
+            no label, UUID=064bdcfb-86ae-49f3-bf9d-b956493e2a1d
+            ```
+          3. Enable the swap space
+            ```
+            root@D2adsv6:/ # swapon /dev/nvme0n1
+            ```
+          4. Check the swap space being set up properly
+            ```
+            root@D2adsv6:/ # swapon -s
+            Filename                                Type            Size    Used    Priority
+            /dev/nvme0n1                            partition       78643196        0       -2
+            ```
+          5. Append the swap space to /etc/fstab to make it persistent across reboots
+            ```
+            root@D2adsv6:/ # echo '/dev/nvme0n1 swap swap defaults 0 0' >> /etc/fstab 
+            ```
       - question: |
           What considerations do I need to be aware of for Maintenance Events, VM Redeploys, and VM Reboots?
         answer: |
