[v17] docs: update cloud networking on proxy service

docs/pages/reference/networking.mdx

@@ -36,21 +36,9 @@ following use cases:
 </TabItem>
 <TabItem scope={["cloud", "team"]} label="Cloud-Hosted">
 
-All Teleport services (e.g., the Application Service and Database Service) have
-an optional `public_addr` property that you can modify in each service's
-configuration file. The public address can take an IP or a DNS name. It can also
-be a list of values:
-
-```yaml
-public_addr: ["service-one.example.com", "service-two.example.com"]
-```
+On Teleport Enterprise (Cloud) the Teleport Agent services always
+connect using reverse tunnels so there is no need to set a public address for an agent.
 
-Specifying a public address for a Teleport agent may be useful in the
-following use cases:
-
-- You have multiple identical services behind a load balancer.
-- You want Teleport to issue an SSH certificate for the service with additional
-  principals, e.g., host names.
 </TabItem>
 </Tabs>