[Rules] Removing the page rules article rewrite-host-headers (#20323)

* [Rules] Update _redirects

SPM-1670

* Delete src/content/docs/rules/page-rules/how-to/override-url-or-ip-address.mdx

SPM-1670

* Update route-production-traffic.mdx

* Update cache-keys.mdx

* Update cloudflare-pages-origin.mdx

* Update settings.mdx

* Update index.mdx

* Update _redirects

* Delete src/content/docs/rules/page-rules/how-to/rewrite-host-headers.mdx

* Update limit-external-connections-application.mdx

* Update settings.mdx

Author: ngayerie

public/_redirects

@@ -1036,6 +1036,8 @@
 /rules/url-forwarding/single-redirects/examples/ /rules/url-forwarding/examples/ 301
 /rules/url-forwarding/dynamic-redirects/parameters/ /rules/url-forwarding/single-redirects/settings/ 301
 /rules/transform/manage/ /rules/transform/ 301
+/rules/page-rules/how-to/rewrite-host-headers/ /rules/origin-rules/examples/change-uri-path-and-host-header/ 301
+/rules/page-rules/how-to/override-url-or-ip-address/ /rules/origin-rules/features/ 301
 
 # ruleset engine
 /ruleset-engine/rules-language/fields/standard-fields/ /ruleset-engine/rules-language/fields/reference/ 301

src/content/docs/cache/how-to/cache-keys.mdx

@@ -120,7 +120,7 @@ Additionally, you cannot include the following headers:
 Host determines which host header to include in the Cache Key.
 
 * If `Use original host` (`resolved: false` in the API), Cloudflare includes the `Host` header in the HTTP request sent to the origin.
-* If `Resolved host` (`resolved: true` in the API), Cloudflare includes the `Host` header that was resolved to get the `origin IP` for the request. The `Host` header may be different from the header actually sent if the [Cloudflare Resolve Override](/rules/page-rules/how-to/override-url-or-ip-address/) feature is used.
+* If `Resolved host` (`resolved: true` in the API), Cloudflare includes the `Host` header that was resolved to get the `origin IP` for the request. The `Host` header may be different from the header actually sent if it has been changed with an [Origin Rule](/rules/origin-rules/features/#dns-record).
 
 ### Cookie
 

src/content/docs/load-balancing/pools/cloudflare-pages-origin.mdx

@@ -209,7 +209,7 @@ Now that you have set up your load balancer and verified everything is working c
 
 1. Confirm that your production hostname has the correct [priority order](/load-balancing/load-balancers/dns-records/#priority-order) of DNS records and is covered by an [SSL/TLS certificate](/load-balancing/load-balancers/dns-records/#ssltls-coverage).
 
-   If you have an Enterprise account, also evaluate your application for any excluded paths. For example, you might not want the load balancer to distribute requests directed at your `/admin` path. For any exceptions, set up an [Origin rule](/rules/origin-rules/features/#dns-record) or [Page rule](/rules/page-rules/how-to/override-url-or-ip-address/).
+   If you have an Enterprise account, also evaluate your application for any excluded paths. For example, you might not want the load balancer to distribute requests directed at your `/admin` path. For any exceptions, set up an [Origin rule](/rules/origin-rules/features/#dns-record).
 
 2. Configure your load balancer to receive production traffic by editing the **Hostname** of your existing load balancer.