Acrolinx fixes.

Author: roygara

includes/virtual-machines-common-convert-disks-considerations.md

@@ -8,12 +8,12 @@ ms.author: cynthn
 
 * The migration will restart the VM, so schedule the migration of your VMs during a pre-existing maintenance window. 
 
-* The migration is not reversible. 
+* The migration isn't reversible. 
 
-* Be aware that any users with the [Virtual Machine Contributor](../articles/role-based-access-control/built-in-roles.md#virtual-machine-contributor) role will not be able to change the VM size (as they could pre-migration). This is because VMs with managed disks require the user to have the Microsoft.Compute/disks/write permission on the OS disks.
+* Any users with the [Virtual Machine Contributor](../articles/role-based-access-control/built-in-roles.md#virtual-machine-contributor) role won't be able to change the VM size (as they could pre-migration). This is because VMs with managed disks require the user to have the Microsoft.Compute/disks/write permission on the OS disks.
 
 * Be sure to test the migration. Migrate a test virtual machine before you perform the migration in production.
 
-* During the migration, you deallocate the VM. The VM receives a new IP address when it is started after the migration. If needed, you can [assign a static IP address](../articles/virtual-network/ip-services/public-ip-addresses.md) to the VM.
+* During the migration, you deallocate the VM. The VM receives a new IP address when it's started after the migration. If needed, you can [assign a static IP address](../articles/virtual-network/ip-services/public-ip-addresses.md) to the VM.
 
 * Review the minimum version of the Azure VM agent required to support the migration process. For information on how to check and update your agent version, see [Minimum version support for VM agents in Azure](https://support.microsoft.com/help/4049215/extensions-and-virtual-machine-agent-minimum-version-support)