Update articles/virtual-machine-scale-sets/virtual-machine-scale-sets-use-availability-zones.md

Co-authored-by: Julia Shimanskiy <[email protected]>

Author: fitzgeraldsteele

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-use-availability-zones.md

@@ -27,7 +27,7 @@ Virtual Machine Scale Sets supports 3 zonal deployment models:
 
 ### Zone redundant or zone spanning 
 
-A zone redundant or zone spanning scale set will spread instances across all selected zones `"zones": ["1","2","3"]`. By default the scale set will perform a best effort approach to evenly spread instances across selected zones, however you can specify that you want strict zone balance by specifying `"zoneBalance": "true"` in your deployment. Each VM and its disks are zonal, so they will be pinned to a specific zone. Instances between zones are connected by high-performance network with low latency. In the event of a zonal outage or connectivity issue, connectivity to instances within the affected zone may be compromised, while instances in other availability zones should be unaffected. You may add capacity to the scale set during a zonal outage, and the scale set will add additonal instances to the unaffected zones. When the zone is restored, you many need to scale down your scale set to the original capacity. A best practice would be to configure autoscale rules based on CPU or memory usage. The autoscale rules would allow the scale set to respond to a loss of the VM instances in that one zone by scaling out new instances in the remaining operational zones.
+A zone redundant or zone spanning scale set will spread instances across all selected zones, `"zones": ["1","2","3"]`. By default, the scale set will perform a best effort approach to evenly spread instances across selected zones. However, you can specify that you want strict zone balance by setting `"zoneBalance": "true"` in your deployment. Each VM and its disks are zonal, so they will be pinned to a specific zone. Instances between zones are connected by high-performance network with low latency. In the event of a zonal outage or connectivity issue, connectivity to instances within the affected zone may be compromised, while instances in other availability zones should be unaffected. You may add capacity to the scale set during a zonal outage, and the scale set will add additional instances to the unaffected zones. When the zone is restored, you many need to scale down your scale set to the original capacity. A best practice would be to configure [autoscale](virtual-machine-scale-sets-autoscale-overview.md) rules based on CPU or memory usage. The autoscale rules would allow the scale set to respond to a loss of the VM instances in that one zone by scaling out new instances in the remaining operational zones.
 
 Spreading instances across availability zones meets the 99.99% SLA for instances spread across availability zones, and is recommended for most workloads in Azure.