Update articles/azure-arc/resource-bridge/troubleshoot-resource-bridge.md

Co-authored-by: JH <[email protected]>

Author: alt-key

articles/azure-arc/resource-bridge/troubleshoot-resource-bridge.md

@@ -218,7 +218,7 @@ To install Azure Arc resource bridge on an Azure Stack HCI cluster, `az arcappli
 
 ### errorCode: CreateConfigKvaCustomerError, errorResponse: error getting the vsphere sdk
 
-For errors with errorCode `CreateConfigKvaCustomerError` and errorResponse `error getting the vsphere sdk`, these errors occur when your deployment machine is trying to establish a TCP connection to your vCenter address but encounters a problem. You receive this errorCode and errorResponse if your vCenter address is incorrect (403 or 404 error) or there is a network/proxy/firewall configuration blocking it (connection attempt failed). If you enter your vCenter address as a hostname and receive the error `no such host`, then your deployment machine is not able to resolve the vCenter hostname via the client DNS. You may receive an error if the deployment machine is able to resolve the vCenter hostname but the deployment machine can't reach the IP address it received from DNS. Continuing along this flow, you may receive an error if the endpoint returned by DNS is not your vCenter address or the traffic was intercepted by proxy. Finally, you may get an error if your deployment machine is able to communicate with your vCenter address but the username or password is incorrect.
+For errors with errorCode `CreateConfigKvaCustomerError` and errorResponse `error getting the vsphere sdk`, these errors occur when your deployment machine is trying to establish a TCP connection to your vCenter address but encounters a problem. You receive this errorCode and errorResponse if your vCenter address is incorrect (403 or 404 error) or if there's a network/proxy/firewall configuration blocking it (connection attempt failed). If you enter your vCenter address as a hostname and receive the error `no such host`, then your deployment machine isn't able to resolve the vCenter hostname via the client DNS. You may receive an error if the deployment machine is able to resolve the vCenter hostname but the deployment machine can't reach the IP address it received from DNS. Continuing along this flow, you may receive an error if the endpoint returned by DNS isn't your vCenter address, or if the traffic was intercepted by proxy. Finally, you may get an error if your deployment machine is able to communicate with your vCenter address, but the username or password is incorrect.
 
 ### vSphere SDK client - Connection attempt failed