Refine wording for node pools advice

Author: genlin

support/azure/azure-kubernetes/create-upgrade-delete/error-code-subnetisfull.md

@@ -54,7 +54,7 @@ To avoid `SubnetIsFull` issues in Azure Kubernetes Service (AKS), follow best pr
 - Use Larger Subnet CIDR: If possible, use a larger subnet CIDR to provide more IP addresses. This strategy helps to accommodate more nodes and pods without running into IP exhaustion issues.
 - Monitor IP Usage: To identify potential issues before they become critical, regularly monitor the IP address usage within your subnets. Tools such as Azure Monitor can help track IP address consumption.
 - Optimize IP Allocation: Make sure that IP addresses are allocated efficiently. Avoid reserving IP addresses unnecessarily. To free up space, release any unused IP addresses.
-- Use multiple node pools: Consider using multiple node pools with different subnets to distribute the IP address load. This strategy can help mitigate the risk of running out of IP addresses in a single subnet.   
+- Use multiple node pools: Consider using node pools that have different subnets to distribute the IP address load. This strategy can help mitigate the risk of running out of IP addresses in a single subnet.   
 
 ## More information