Fixes

Author: roygara

includes/managed-disks-ultra-disks-GA-scope-and-limitations.md

@@ -11,11 +11,14 @@ ms.custom: include file
 ---
 For now, ultra disks have additional limitations, they are as follows:
 
-The only infrastructure redundancy options currently available to ultra disks are availability zones, VMs using any other redundancy options cannot attach an ultra disk.  though ultra disks are not offered in every availability zone of these regions:
+The only infrastructure redundancy options currently available to ultra disks are availability zones. VMs using any other redundancy options cannot attach an ultra disk.
 
-The following table outlines the available regions and their corresponding availability options:
+The following table outlines the regions ultra disks are available in, as well as their corresponding availability options:
 
-|Regions  |No infrastructure Redundancy  |Availability zones  |
+> [!NOTE]
+> Ultra disks are not offered in every availability zone within these regions
+
+|Regions  |No infrastructure redundancy  |Availability zones  |
 |---------|---------|---------|
 |West US     |Yes         |No         |
 |West US 2    |No         |Yes         |

includes/virtual-machines-disks-getting-started-ultra-ssd.md

@@ -58,7 +58,7 @@ Now that you know which zone to deploy to, follow the deployment steps in this a
 
 ### VMs with no redundancy options
 
-Ultra disks deployed in West US must be deployed without any redundancy options, for now. However, not every disk size that supports ultra disks may be in this region. To determine which ones in West US support ultra disks, you can use either of the following code snipptes. Make sure to replace the `vmSize` and `subscription` values first:
+Ultra disks deployed in West US must be deployed without any redundancy options, for now. However, not every disk size that supports ultra disks may be in this region. To determine which ones in West US support ultra disks, you can use either of the following code snippets. Make sure to replace the `vmSize` and `subscription` values first:
 
 ```azurecli
 $subscription = "<yourSubID>"
@@ -200,7 +200,7 @@ az vm create --subscription $subscription -n $vmname -g $rgname --image Win2016D
 
 ### Enable ultra disk compatibility on an existing VM
 
-If your VM meets the requirements outlined in [GA scope and limitations](#ga-scope-and-limitations) and is in the [appropriate zone for your account](#determine-vm-size-and-region-availability) then you can enable ultra disk compatibility on your VM.
+If your VM meets the requirements outlined in [GA scope and limitations](#ga-scope-and-limitations) and is in the [appropriate zone for your account](#determine-vm-size-and-region-availability), then you can enable ultra disk compatibility on your VM.
 
 To enable ultra disk compatibility, you must stop the VM. After you stop the VM, you may enable compatibility, attach an ultra disk, then restart the VM:
 
@@ -280,7 +280,7 @@ New-AzVm `
 
 ### Enable ultra disk compatibility on an existing VM
 
-If your VM meets the requirements outlined in [GA scope and limitations](#ga-scope-and-limitations) and is in the [appropriate zone for your account](#determine-vm-size-and-region-availability) then you can enable ultra disk compatibility on your VM.
+If your VM meets the requirements outlined in [GA scope and limitations](#ga-scope-and-limitations) and is in the [appropriate zone for your account](#determine-vm-size-and-region-availability), then you can enable ultra disk compatibility on your VM.
 
 To enable ultra disk compatibility, you must stop the VM. After you stop the VM, you may enable compatibility, attach an ultra disk, then restart the VM:
 

includes/virtual-machines-disks-shared.md

@@ -89,6 +89,7 @@ Ultra disks have the unique capability of allowing you to set your performance b
 |DiskMBpsReadWrite     |The total throughput (MB/s) allowed across all VMs mounting the shared disk with write access.         |
 |DiskIOPSReadOnly*     |The total number of IOPS allowed across all VMs mounting the shared disk as ReadOnly.         |
 |DiskMBpsReadOnly*     |The total throughput (MB/s) allowed across all VMs mounting the shared disk as ReadOnly.         |
+
 \* Applies to shared ultra disks only
 
 The following formulas explain how the performance attributes can be set, since they are user modifiable:
@@ -107,7 +108,7 @@ The following examples depict a few scenarios that show how the throttling can w
 
 #### Two nodes cluster using cluster shared volumes
 
-The following is an example of a 2-node WSFC using clustered shared volumes. With this configuration, both VMs have simultatenous write-access to the disk which results in the ReadWrite throttle being split across the two VMs and the ReadOnly throttle not being used.
+The following is an example of a 2-node WSFC using clustered shared volumes. With this configuration, both VMs have simultaneous write-access to the disk, which results in the ReadWrite throttle being split across the two VMs and the ReadOnly throttle not being used.
 
 :::image type="complex" source="media/virtual-machines-disks-shared-disks/ultra-two-node-example.png" alt-text="CSV two node ultra example":::
 

includes/virtual-machines-enable-shared-disk.md

@@ -88,7 +88,7 @@ az disk update -g rg1 -n clidisk --disk-iops-read-write 3000 --disk-mbps-read-wr
 az disk show -g rg1 -n clidisk
 ```
 
-#### ARM
+#### Azure Resource Manager
 
 To deploy a managed disk with the shared disk feature enabled, use the property `maxShares` and define a value greater than 1. This makes the disk shareable across multiple VMs.