Merge pull request #218288 from mattmcinnes/patch-23

Update resize-vm.md

Author: prmerger-automator[bot]

articles/virtual-machines/resize-vm.md

@@ -5,7 +5,7 @@ author: cynthn
 ms.service: virtual-machines
 ms.workload: infrastructure
 ms.topic: how-to
-ms.date: 09/13/2021
+ms.date: 11/14/2021
 ms.author: cynthn 
 ms.custom: devx-track-azurepowershell
 
@@ -16,7 +16,7 @@ ms.custom: devx-track-azurepowershell
 
 This article shows you how to move a VM to a different [VM size](sizes.md).
 
-After you create a virtual machine (VM), you can scale the VM up or down by changing the VM size. In some cases, you must deallocate the VM first. This can happen if the new size is not available on the hardware cluster that is currently hosting the VM.
+After you create a virtual machine (VM), you can scale the VM up or down by changing the VM size. In some cases, you must deallocate the VM first. This can happen if the new size isn't available on the hardware cluster that is currently hosting the VM.
 
 If your VM uses Premium Storage, make sure that you choose an **s** version of the size to get Premium Storage support. For example, choose Standard_E4**s**_v3 instead of Standard_E4_v3.
 
@@ -30,7 +30,7 @@ If your VM uses Premium Storage, make sure that you choose an **s** version of t
 1. Pick a new size from the list of available sizes and then select **Resize**.
 
 
-If the virtual machine is currently running, changing its size will cause it to be restarted. 
+If the virtual machine is currently running, changing its size will cause it to restart. 
 
 If your VM is still running and you don't see the size you want in the list, stopping the virtual machine may reveal more sizes.
 
@@ -61,9 +61,9 @@ To resize a VM, you need the latest [Azure CLI](/cli/azure/install-az-cli2) inst
     --size Standard_DS3_v2
     ```
    
-    The VM restarts during this process. After the restart, your existing OS and data disks are remapped. Anything on the temporary disk is lost.
+    The VM restarts during this process. After the restart, your existing OS and data disks are kept. Anything on the temporary disk is lost.
 
-3. If the desired VM size is not listed, you need to first deallocate the VM with [az vm deallocate](/cli/azure/vm). This process allows the VM to then be resized to any size available that the region supports and then started. The following steps deallocate, resize, and then start the VM named `myVM` in the resource group named `myResourceGroup`:
+3. If the desired VM size isn't listed, you need to first deallocate the VM with [az vm deallocate](/cli/azure/vm). This process allows the VM to then be resized to any size available that the region supports and then started. The following steps deallocate, resize, and then start the VM named `myVM` in the resource group named `myResourceGroup`:
    
     ```azurecli-interactive
     # Variables will make this easier. Replace the values with your own.
@@ -105,15 +105,15 @@ List the VM sizes that are available in the region where the VM is hosted.
 Get-AzVMSize -ResourceGroupName $resourceGroup -VMName $vmName 
 ```
 
-If the size you want is listed, run the following commands to resize the VM. If the desired size is not listed, go on to step 3.
+If the size you want is listed, run the following commands to resize the VM. If the desired size isn't listed, go on to step 3.
 
 ```azurepowershell-interactive
 $vm = Get-AzVM -ResourceGroupName $resourceGroup -VMName $vmName
 $vm.HardwareProfile.VmSize = "<newVMsize>"
 Update-AzVM -VM $vm -ResourceGroupName $resourceGroup
 ```
 
-If the size you want is not listed, run the following commands to deallocate the VM, resize it, and restart the VM. Replace **\<newVMsize>** with the size you want.
+If the size you want isn't listed, run the following commands to deallocate the VM, resize it, and restart the VM. Replace **\<newVMsize>** with the size you want.
 
 ```azurepowershell-interactive
 Stop-AzVM -ResourceGroupName $resourceGroup -Name $vmName -Force
@@ -131,7 +131,7 @@ Start-AzVM -ResourceGroupName $resourceGroup -Name $vmName
 
 **Use PowerShell to resize a VM in an availability set**
 
-If the new size for a VM in an availability set is not available on the hardware cluster currently hosting the VM, then all VMs in the availability set will need to be deallocated to resize the VM. You also might need to update the size of other VMs in the availability set after one VM has been resized. To resize a VM in an availability set, perform the following steps.
+If the new size for a VM in an availability set isn't available on the hardware cluster currently hosting the VM, then all VMs in the availability set will need to be deallocated to resize the VM. You also might need to update the size of other VMs in the availability set after one VM has been resized. To resize a VM in an availability set, perform the following steps.
 
 ```azurepowershell-interactive
 $resourceGroup = "myResourceGroup"
@@ -146,7 +146,7 @@ Get-AzVMSize `
 -VMName $vmName 
 ```
 
-If the desired size is listed, run the following commands to resize the VM. If it is not listed, go to the next section.
+If the desired size is listed, run the following commands to resize the VM. If it isn't listed, go to the next section.
 
 ```azurepowershell-interactive
 $vm = Get-AzVM `
@@ -158,7 +158,7 @@ Update-AzVM `
 -ResourceGroupName $resourceGroup
 ```
 
-If the size you want is not listed, continue with the following steps to deallocate all VMs in the availability set, resize VMs, and restart them.
+If the size you want isn't listed, continue with the following steps to deallocate all VMs in the availability set, resize VMs, and restart them.
 
 Stop all VMs in the availability set.
 
@@ -193,11 +193,11 @@ The only combinations allowed for resizing are:
 - VM (with local temp disk) -> VM (with local temp disk); and
 - VM (with no local temp disk) -> VM (with no local temp disk).
 
-If interested in a work around, please see [How do I migrate from a VM size with local temp disk to a VM size with no local temp disk?](azure-vms-no-temp-disk.yml#how-do-i-migrate-from-a-vm-size-with-local-temp-disk-to-a-vm-size-with-no-local-temp-disk---)
+If interested in a work-around, see [How do I migrate from a VM size with local temp disk to a VM size with no local temp disk?](azure-vms-no-temp-disk.yml#how-do-i-migrate-from-a-vm-size-with-local-temp-disk-to-a-vm-size-with-no-local-temp-disk---)
 
 
 
 
 ## Next steps
 
-For additional scalability, run multiple VM instances and scale out. For more information, see [Automatically scale machines in a Virtual Machine Scale Set](../virtual-machine-scale-sets/tutorial-autoscale-powershell.md).
+For more scalability, run multiple VM instances and scale out. For more information, see [Automatically scale machines in a Virtual Machine Scale Set](../virtual-machine-scale-sets/tutorial-autoscale-powershell.md).