Update scale-cluster.md

Updated to "If the resource needs of your applications change, your cluster performance may be impacted due to low capacity on CPU, memory, PID space, or disk sizes. To address these changes, you can manually scale your AKS cluster to run a different number of nodes. " in line 11

Author: rzhang628

articles/aks/scale-cluster.md

@@ -8,7 +8,7 @@ ms.date: 06/29/2022
 
 # Scale the node count in an Azure Kubernetes Service (AKS) cluster
 
-If the resource needs of your applications change, for example, your cluster performance may be impacted due to low capacity on CPU, memnory, PID space or disk sizes, you can manually scale an AKS cluster to run a different number of nodes. When you scale down, nodes are carefully [cordoned and drained][kubernetes-drain] to minimize disruption to running applications. When you scale up, AKS waits until nodes are marked **Ready** by the Kubernetes cluster before pods are scheduled on them.
+If the resource needs of your applications change, your cluster performance may be impacted due to low capacity on CPU, memory, PID space, or disk sizes. To address these changes, you can manually scale your AKS cluster to run a different number of nodes. When you scale down, nodes are carefully [cordoned and drained][kubernetes-drain] to minimize disruption to running applications. When you scale up, AKS waits until nodes are marked **Ready** by the Kubernetes cluster before pods are scheduled on them.
 
 ## Scale the cluster nodes
 
@@ -165,4 +165,4 @@ In this article, you manually scaled an AKS cluster to increase or decrease the
 [set-azakscluster]: /powershell/module/az.aks/set-azakscluster
 [cluster-autoscaler]: cluster-autoscaler.md
 [az-aks-nodepool-scale]: /cli/azure/aks/nodepool#az_aks_nodepool_scale
-[update-azaksnodepool]: /powershell/module/az.aks/update-azaksnodepool
+[update-azaksnodepool]: /powershell/module/az.aks/update-azaksnodepool