Merge pull request #1266 from fermyon/tpmccallum-patch-2

Private endpoints in Spin 2.5

content/spin/v2/http-outbound.md

@@ -197,7 +197,9 @@ Both of these work only from HTTP components. That is, if you want to make an in
 
 To make an HTTP request to another component in your application, use the special `<component-id>.spin.internal` host name. For example, an outbound HTTP request to `authz.spin.internal` will be handled by the `authz` component.
 
-In this way of doing self-requests, the request is passed in memory without ever leaving the Spin host process. This is extremely fast, as the two components are wired almost directly together, but may reduce deployment flexibility depending on the nature of the microservices. Also, components that are the target of service chaining requests may see URLs in both routed and chained forms: therefore, if they parse the URL (for example, extracting a resource identifier from the path), they must ensure both forms are correctly handled.
+In this way of doing self-requests, the request is passed in memory without ever leaving the Spin host process. This is extremely fast, as the two components are wired almost directly together, but may reduce deployment flexibility depending on the nature of the microservices. Also, public components that are the target of service chaining requests may see URLs in both routed and chained forms: therefore, if they parse the URL (for example, extracting a resource identifier from the path), they must ensure both forms are correctly handled.
+
+> Service chaining is the only way to call [private endpoints](./http-trigger#private-endpoints).
 
 You must still grant permission by including the relevant `spin.internal` hosts in `allowed_outbound_hosts`: