Fix typos and improve clarity in documentation

Incorporate content team comments

Author: charleswool

support/azure/azure-kubernetes/extensions/troubleshoot-network-isolated-cluster.md

@@ -19,17 +19,17 @@ This article discusses how to troubleshoot the [network isolated cluster][networ
 
 ## Network isolated cluster support
 
-The network isolated cluster follows a similar support model to other [AKS add-ons](/azure/aks/integrations). There are two options available for the private ACR with network isolated clusters. If you are bringing your own ACR, note that you are reponsible to ensure ACR and associated resources including ACR cache rule, private endpoint, and private DNS zone are properly configured.
+The network isolated cluster follows a similar support model to other [AKS add-ons](/azure/aks/integrations). There are two options available for the private ACR with network isolated clusters. If you're bringing your own ACR, then you're responsible for properly configuring your ACR and associated resources.
 
 ## Known issues
 
 ### Cluster image pull failed
 Network isolated clusters leverage ACR cache rules for image pulls, when there is an image pull fail error due to network isolation:
-- If you are using BYO ACR, check your private ACR resources, including the cache rule and private endpoints to verify they are configured as recommended by the documentation guidance. You can also try to connect the ACR from node.
-- If you are using AKS Managed ACR, only MCR images are supported by default. Thus, if the image pull failure is on images from other registries, then you need go to the private ACR to create additional cache rule for those images. If the image pull failure is on MCR images, please proceed to check if the associated ACR and private endpoint resource named with keyword `bootstrap` exists. If doesn't exist, please reconcile the cluster.
+- If you're using BYO ACR, check your private ACR resources, including the cache rule and private endpoints to verify they're configured using recommendations outlined in the documentation.
+- If you're using AKS Managed ACR, only MCR images are supported by default. If the image pull failure is on images from other registries, then you need go to the private ACR to create additional cache rule for those images. If the image pull failure is on MCR images, please proceed to check if the associated ACR and private endpoint resource named with keyword `bootstrap` exists. If doesn't exist, please reconcile the cluster.
 
 ### Cluster image pull fails after updating the existed cluster to network isolated cluster or updating the private ACR resource ID
-This is a by designed behavior, you need to reimage the node to update the kubelet configuration in cse following the update actions mentioned.
+This is an intended behavior, you need to reimage the node to update the kubelet configuration in CSE (Container Service Extension) following the update actions mentioned.
 
 ### ACR or associated cache rule, private endpoint and private DNS zone are deleted by accident
 If the cache rule is deleted from the managed ACR by accident, the mitigation is to delete the ACR and then reconcile the cluster. If the ACR itself or private endpoint or private DNS zone is deleted by accident, the mitigation is just to reconcile the cluster.