Update troubleshooting steps for Node Not Ready issues

Author: genlin

support/azure/azure-kubernetes/availability-performance/node-not-ready-then-recovers.md

@@ -9,7 +9,7 @@ ms.custom: sap:Node/node pool availability and performance
 ---
 # Troubleshoot Node Not Ready failures that are followed by recoveries
 
-This article provides a guide to troubleshoot and resolve "Node Not Ready" issues in Azure Kubernetes Service (AKS) clusters. When a node enters a "Not Ready" state, it can disrupt the application's functionality and cause it to stop responding. Typically, the node recovers automatically after a short period. However, to prevent recurring issues and maintain a stable environment, it's important to understand the underlying causes to be able to implement effective resolutions. 
+This article provides a guide to troubleshoot and resolve Node Not Ready" issues in Azure Kubernetes Service (AKS) clusters. When a node enters a "NotReady" state, it can disrupt the application's functionality and cause it to stop responding. Typically, the node recovers automatically after a short period. However, to prevent recurring issues and maintain a stable environment, it's important to understand the underlying causes to be able to implement effective resolutions.  
 
 ## Cause
 
@@ -22,20 +22,16 @@ There are several scenarios that could cause a "Not Ready" state to occur:
   - [Azure status](https://status.azure.com/)
   - Azure notifications (for any recent outages or maintenance periods)
 
-## Examples:
-Error: NodeNotReady  
-
-- This error indicates that the node is not ready. To resolve this, check the node's status using the command: kubectl describe node <node-name>.
-
 ## Resolution
 
-Check the API server availability by running the `kubectl get apiservices` command. Make sure that the readiness probe is correctly configured in the deployment YAML file.
+To resolve this issue, follow these steps:
 
-For further steps, see [Basic troubleshooting of Node Not Ready failures](node-not-ready-basic-troubleshooting.md).
+1. Run `kubectl describe node <node-name>` to review detail information about the node's status. Look for any error messages or warnings that might indicate the root cause of the issue.
+2. Check the API server availability by running the `kubectl get apiservices` command. Make sure that the readiness probe is correctly configured in the deployment YAML file.
+3. Verify the node network configuration to make sure that there are no connectivity issues.
+4. Check the node resource usage, such as CPU, memory, and disk, to identify potential constraints. For more informations see [Monitor your Kubernetes cluster performance with Container insights](/azure/azure-monitor/containers/container-insights-analyze#view-performance-directly-from-a-cluster)
 
-## Additional Troubleshooting Steps:
- - Verify the node's network configuration to ensure there are no connectivity issues.
- - Check the node's resource usage (CPU, memory, disk) to identify any resource constraints. For more informations see [Monitor your Kubernetes cluster performance with Container insights](https://learn.microsoft.com/en-us/azure/azure-monitor/containers/container-insights-analyze#view-performance-directly-from-a-cluster)
+For further steps, see [Basic troubleshooting of Node Not Ready failures](node-not-ready-basic-troubleshooting.md).
 
 ## Prevention