Update docs/toolhive/guides-ui/network-isolation.mdx

Co-authored-by: Dan Barr <[email protected]>

Author: yrobla

docs/toolhive/guides-ui/network-isolation.mdx

@@ -84,7 +84,8 @@ The configuration pictured below allows the MCP server to access
 To allow an MCP server to access other workloads on the same network, you need
 to configure network isolation to include the appropriate hostnames and ports.
 This is commonly needed when your MCP server needs to communicate with
-databases, APIs, or other services that are not publicly accessible.
+databases, APIs, or other services that are running on your local host during
+development.
 
 For example, in Docker environments, you can add `host.docker.internal` to
 access services on the host: