error edit

Author: allyford

articles/aks/support-policies.md

@@ -133,7 +133,7 @@ If you do not need your AKS workloads to run continuously, you can [stop the AKS
 
 Manually de-allocating all cluster nodes via the IaaS APIs/CLI/portal is not a supported way to stop an AKS cluster or nodepool. The cluster will be considered out of support and will be stopped by AKS after 30 days. The clusters will then be subject to the same 12 month preservation policy as a correctly stopped cluster.
 
-AKS will deallocate CCP for clusters with all non-stopped nodes in the "Not Ready" state will also be stopped by AKS after 30 days. To reallocate CCP, reconcile the cluster back to its current state using [az aks update](https://learn.microsoft.com/en-us/cli/azure/aks?view=azure-cli-latest#az-aks-update-examples:~:text=Reconcile%20the%20cluster%20back%20to%20its%20current%20state.). 
+AKS will deallocate CCP for clusters with all non-stopped nodes in the "Not Ready" state after 30 days. To reallocate CCP, reconcile the cluster back to its current state using [az aks update](https://learn.microsoft.com/en-us/cli/azure/aks?view=azure-cli-latest#az-aks-update-examples:~:text=Reconcile%20the%20cluster%20back%20to%20its%20current%20state.). 
 
 AKS reserves the right to archive control planes that have been configured out of support guidelines for extended periods equal to and beyond 30 days. AKS maintains backups of cluster etcd metadata and can readily reallocate the cluster. This reallocation can be initiated by any PUT operation bringing the cluster back into support, such as an upgrade or scale to active agent nodes.