Merge pull request #728 from MicrosoftDocs/main

12/10/2024 PM Publish

articles/virtual-machines/disks-performance.md

@@ -3,7 +3,7 @@ title: Virtual machine and disk performance
 description: Learn more about how virtual machines and their attached disks work in combination for performance.
 author: roygara
 ms.author: rogarana
-ms.date: 05/31/2023
+ms.date: 10/28/2024
 ms.topic: conceptual
 ms.service: azure-disk-storage
 ---
@@ -14,7 +14,7 @@ ms.service: azure-disk-storage
 [!INCLUDE [VM and Disk Performance](./includes/virtual-machine-disk-performance.md)]
 
 ## Virtual machine uncached vs cached limits
-Virtual machines that are enabled for both premium storage and premium storage caching have two different storage bandwidth limits. Let's look at the Standard_D8s_v3 virtual machine as an example. Here is the documentation on the [Dsv3-series](dv3-dsv3-series.md) and the Standard_D8s_v3:
+Virtual machines that are enabled for both premium storage and premium storage caching have two different storage bandwidth limits. Let's look at the Standard_D8s_v3 virtual machine as an example. Here is the documentation on the [Dsv3-series](./sizes/general-purpose/dsv3-series.md) and the Standard_D8s_v3:
 
 [!INCLUDE [VM and Disk Performance](./includes/virtual-machine-disk-performance-2.md)]
 

articles/virtual-machines/linux/n-series-driver-setup.md

@@ -41,7 +41,7 @@ lspci | grep -i NVIDIA
 ```
 Output is similar to the following example (showing an NVIDIA Tesla K80 card):
 
-![lspci command output](./media/n-series-driver-setup/lspci.png)
+:::image type="content" source="./media/n-series-driver-setup/lspci.png" alt-text="Screenshot of example output showing an NVIDIA Tesla K80 card.":::
 
 lspci lists the PCIe devices on the VM, including the InfiniBand NIC and GPUs, if any. If lspci doesn't return successfully, you may need to install LIS on CentOS/RHEL.
 
@@ -160,7 +160,7 @@ To query the GPU device state, SSH to the VM and run the [nvidia-smi](https://de
 
 If the driver is installed, Nvidia SMI lists the **GPU-Util** as 0% until you run a GPU workload on the VM. Your driver version and GPU details may be different from the ones shown.
 
-![NVIDIA device status](./media/n-series-driver-setup/smi.png)
+:::image type="content" source="./media/n-series-driver-setup/smi.png" alt-text="Screenshot of NVIDIA device status.":::
 
 ## RDMA network connectivity
 
@@ -334,7 +334,7 @@ To query the GPU device state, SSH to the VM and run the [nvidia-smi](https://de
 
 If the driver is installed, Nvidia SMI will list the **GPU-Util** as 0% until you run a GPU workload on the VM. Your driver version and GPU details may be different from the ones shown.
 
-![Screenshot that shows the output when the GPU device state is queried.](./media/n-series-driver-setup/smi-nv.png)
+:::image type="content" source="./media/n-series-driver-setup/smi-nv.png" alt-text="Screenshot showing the output when the GPU device state is queried.":::
 
 
 ### X11 server

articles/virtual-machines/linux/run-command-managed.md

@@ -232,7 +232,7 @@ Remove-AzVMRunCommand -ResourceGroupName "myRG" -VMName "myVM" -RunCommandName "
 To deploy a new Run Command, execute a PUT on the VM directly and specify a unique name for the Run Command instance. 
 
 ```rest
-GET /subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.Compute/virtualMachines/<vmName>/runcommands?api-version=2019-12-01
+PUT /subscriptions/<subscriptionId>/resourceGroups/<resourceGroupName>/providers/Microsoft.Compute/virtualMachines/<vmName>/runcommands?api-version=2019-12-01
 ```
 
 ```json

articles/virtual-machines/windows/on-prem-to-azure.md

@@ -43,7 +43,7 @@ Based on your needs, you can choose from four types of storage options. To learn
 
 This section helps you to make the best decision on VM and disk types.
 
-If you are planning on migrating from unmanaged disks to managed disks, you should be aware that users with the [Virtual Machine Contributor](/azure/role-based-access-control/built-in-roles#virtual-machine-contributor) role will not be able to change the VM size (as they could pre-conversion). This is because VMs with managed disks require the user to have the Microsoft.Compute/disks/write permission on the OS disks.
+If you are planning on migrating from unmanaged disks to managed disks, you should be aware that users with the [Virtual Machine Contributor](/azure/role-based-access-control/built-in-roles#virtual-machine-contributor) role will not be able to change the VM size (as they could pre-conversion).
 
 ### Location