Update availability-zones.md

Author: itechedit

articles/aks/availability-zones.md

@@ -1,5 +1,5 @@
 ---
-title: Use Availability Zones in Azure Kubernetes Service (AKS)
+title: Use availability zones in Azure Kubernetes Service (AKS)
 description: Learn how to create a cluster that distributes nodes across availability zones in Azure Kubernetes Service (AKS)
 services: container-service
 author: mlearned
@@ -11,7 +11,7 @@ ms.date: 06/24/2019
 ms.author: mlearned
 ---
 
-# Create an Azure Kubernetes Service (AKS) cluster that uses Availability Zones
+# Create an Azure Kubernetes Service (AKS) cluster that uses availability zones
 
 An Azure Kubernetes Service (AKS) cluster distributes resources such as the nodes and storage across logical sections of the underlying Azure compute infrastructure. This deployment model makes sure that the nodes run across separate update and fault domains in a single Azure datacenter. AKS clusters deployed with this default behavior provide a high level of availability to protect against a hardware failure or planned maintenance event.
 
@@ -55,11 +55,11 @@ Volumes that use Azure managed disks are currently not zonal resources. Pods res
 
 If you must run stateful workloads, use taints and tolerations in your pod specs to tell the Kubernetes scheduler to create pods in the same zone as your disks. Alternatively, use network-based storage such as Azure Files that can attach to pods as they're scheduled between zones.
 
-## Overview of Availability Zones for AKS clusters
+## Overview of availability zones for AKS clusters
 
-Availability Zones is a high-availability offering that protects your applications and data from datacenter failures. Zones are unique physical locations within an Azure region. Each zone is made up of one or more datacenters equipped with independent power, cooling, and networking. To ensure resiliency, there’s a minimum of three separate zones in all enabled regions. The physical separation of Availability Zones within a region protects applications and data from datacenter failures. Zone-redundant services replicate your applications and data across Availability Zones to protect from single-points-of-failure.
+Availability zones is a high-availability offering that protects your applications and data from datacenter failures. Zones are unique physical locations within an Azure region. Each zone is made up of one or more datacenters equipped with independent power, cooling, and networking. To ensure resiliency, there’s a minimum of three separate zones in all enabled regions. The physical separation of availability zones within a region protects applications and data from datacenter failures. Zone-redundant services replicate your applications and data across availability zones to protect from single-points-of-failure.
 
-For more information, see [What are Availability Zones in Azure?][az-overview].
+For more information, see [What are availability zones in Azure?][az-overview].
 
 AKS clusters that are deployed using availability zones can distribute nodes across multiple zones within a single region. For example, a cluster in the *East US 2* region can create nodes in all three availability zones in *East US 2*. This distribution of AKS cluster resources improves cluster availability as they're resilient to failure of a specific zone.
 
@@ -147,13 +147,13 @@ Name:       aks-nodepool1-28993262-vmss000004
             failure-domain.beta.kubernetes.io/zone=eastus2-2
 ```
 
-As you can see, we have now two additional nodes in zones 1 and 2. You can now deploy an application consisting of 3 replicas, we will use NGINX as example:
+As you can see, we now have two additional nodes in zones 1 and 2. You can deploy an application consisting of three replicas. We will use NGINX as example:
 
 ```console
 kubectl run nginx --image=nginx --replicas=3
 ```
 
-If you verify that nodes where your pods are running, you will see that the pods are running on the pods corresponding to three different Availability Zones. For example with the command `kubectl describe pod | grep -e "^Name:" -e "^Node:"` you would get an output similar to this:
+If you verify that nodes where your pods are running, you will see that the pods are running on the pods corresponding to three different availability zones. For example with the command `kubectl describe pod | grep -e "^Name:" -e "^Node:"` you would get an output similar to this:
 
 ```console
 Name:         nginx-6db489d4b7-ktdwg
@@ -164,7 +164,7 @@ Name:         nginx-6db489d4b7-xz6wj
 Node:         aks-nodepool1-28993262-vmss000004/10.240.0.8
 ```
 
-As you can see from the previous output, the first pod is running on node 0, which is located in the Availability Zone `eastus2-1`. The second pod is running on node 2, which corresponds to `eastus2-3`, and the third one in node 4, in `eastus2-2`. As you can see, without any additional configuration Kubernetes is spreading the pods correctly across all three Availability Zones.
+As you can see from the previous output, the first pod is running on node 0, which is located in the availability zone `eastus2-1`. The second pod is running on node 2, which corresponds to `eastus2-3`, and the third one in node 4, in `eastus2-2`. Without any additional configuration, Kubernetes is spreading the pods correctly across all three availability zones.
 
 ## Next steps