Clarify document.

Author: Paul D.Smith

articles/operator-nexus/troubleshoot-dns-issues.md

@@ -12,14 +12,16 @@ ms.date: 12/10/2024
 
 # Troubleshoot Nexus DNS Issues
 
-NNF (Nexus Network Fabric) NNF provides a bridge between some new name for Nexus Far Edge resources and Azure, accessing Azure resources via their domain names. However a DNS (Domain Name System) error in NNF can mean that Azure resources can't be contacted which impacts deployment or management of some new name for Nexus Far Edge resources.
+NNF (Nexus Network Fabric) NNF provides a bridge between Nexus resources hosted by a Kubernetes
+cluster running on Azure VMs (Virtual Machines) and Azure, accessing Azure resources via their
+domain names. However a DNS (Domain Name System) error in NNF can mean that Azure resources
+can't be contacted which impacts deployment or management of Nexus resources.
 
 ## Diagnosis
 
-* Deployment or management of remote Nexus resources fails with "DeploymentFailed", often because of a failure to access an ACR (Azure Container Registry) or similar Azure resource. Errors observed include but aren't limited to:
- * "...could not login to OCI registry..."
- * "GatewayTimeout".
-* Azure portal shows no errors being generated for the Azure resources that are unreachable; there are no errors because the failing operations aren't actually accessing the resources at all.
+* Deployment or management of remote Nexus resources fails with "DeploymentFailed".
+* Geneva logging shows 500 and/or 503 HTTP errors and failure to access Azure resources such as VM images hosted in ACRs (Azure Container Registry).
+* Azure portal shows no errors being generated for the Azure resources that are unreachable; there are no errors because the failing operations aren't reaching the Azure resources at all.
 
 ## Mitigation steps