[Several] Updates 1xxx links

src/content/docs/analytics/account-and-zone-analytics/threat-types.mdx

@@ -8,7 +8,7 @@ Cloudflare classifies the threats that it blocks or challenges. To help you unde
 
 ## Bad browser
 
-The source of the request was not legitimate or the request itself was malicious. Users would receive a [1010 error page](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/#error-1010-the-owner-of-this-website-has-banned-your-access-based-on-your-browsers-signature) in their browser.
+The source of the request was not legitimate or the request itself was malicious. Users would receive a [1010 error page](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1010/) in their browser.
 
 Cloudflare's [Browser Integrity Check](/waf/tools/browser-integrity-check/) looks for common HTTP headers abused most commonly by spammers and denies them access to your page. It will also challenge visitors that do not have a user agent or a non standard user agent (also commonly used by bots, crawlers, or visitors).
 

src/content/docs/dns/troubleshooting/dns-issues.mdx

@@ -11,7 +11,7 @@ In web browsers such as Safari or Chrome, there are several commonly observable
 * `This webpage is not available`
 * `err_name_not_resolved`
 * `Can't find the server`
-* [`Error 1001 DNS resolution error`](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/#error-1001-dns-resolution-error)
+* [`Error 1001 DNS resolution error`](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1001/)
 
 ## Common causes and resolutions
 

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

@@ -81,7 +81,7 @@ To support the [use cases](#use-cases) mentioned above, and assuming you only ha
 
 The endpoint pointing to [Cloudflare Pages](/pages/) must have **host header** filled in with the project domain (`<project>.pages.dev`) for it to resolve correctly. You can find a reference table for correct setup in Step 8 below.
 
-Failing to add the host header will result in [response code mismatch error](/load-balancing/troubleshooting/common-error-codes/#response-code-mismatch-error) for the monitor, and [Error 1000: DNS points to prohibited IP](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/#error-1000-dns-points-to-prohibited-ip) for visitors (if the load balancer is enabled despite the unhealthy monitor status).
+Failing to add the host header will result in [response code mismatch error](/load-balancing/troubleshooting/common-error-codes/#response-code-mismatch-error) for the monitor, and [Error 1000: DNS points to prohibited IP](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1000/) for visitors (if the load balancer is enabled despite the unhealthy monitor status).
 :::
 
 1. Go to **Traffic** > **Load Balancing**.

src/content/docs/rules/custom-errors/example-rules.mdx

@@ -123,7 +123,7 @@ This `PUT` request, corresponding to the [Update a zone entry point ruleset](/ap
 
 ### Custom HTML response for Cloudflare 1020 errors
 
-This example configures a custom HTML error response for [Cloudflare error 1020](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/#error-1020-access-denied) (Access Denied).
+This example configures a custom HTML error response for [Cloudflare error 1020](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1020/) (Access Denied).
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 

src/content/docs/ssl/reference/certificate-and-hostname-priority.mdx

@@ -77,7 +77,7 @@ If a hostname resource record is not proxied (gray-clouded) for a zone on Cloudf
 
 Customer1 uses Cloudflare as authoritative DNS for the zone `shop.example.com`. Customer2 is a SaaS provider that creates and successfully [verifies the new custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/) `shop.example.com`. Afterward, traffic starts routing over Customer2's zone:
 
-* If Customer1 wants to regain control of their zone, Customer1 contacts Customer2 and requests them to delete the custom hostname record. Customer1 should make sure to have their record target updated to something other than the SaaS provider target, otherwise Customer1 would get a [`1014` error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/#error-1014-cname-cross-user-banned).
+* If Customer1 wants to regain control of their zone, Customer1 contacts Customer2 and requests them to delete the custom hostname record. Customer1 should make sure to have their record target updated to something other than the SaaS provider target, otherwise Customer1 would get a [`1014` error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014/).
 * If Customer1 already has a proxied record for `www.example.com` when Customer2 creates and verifies a new custom hostname `www.example.com`, [Orange-to-Orange](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) applies.
 * If Customer1 already has a proxied record for `www.example.com` in a legacy custom hostname setup (with another SaaS provider, Customer3) and Customer2 creates and verifies a new wildcard custom hostname for `*.example.com`, legacy custom hostname on Customer3 platform takes precedence due to exact hostname match.
 

src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error.mdx

@@ -166,7 +166,7 @@ This error typically happens with a `PUT` request when multiple clients are atte
 
 ### Cloudflare-specific information
 
-Cloudflare will return a 409 response for a [Error 1001: DNS Resolution Error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/#error-1001-dns-resolution-error).
+Cloudflare will return a 409 response for a [Error 1001: DNS Resolution Error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1001/).
 
 ## 410 Gone
 

src/content/docs/waf/reference/migration-guides/firewall-rules-to-custom-rules.mdx

@@ -43,7 +43,7 @@ Custom block response configurations will not be returned by the Firewall Rules
 
 ### Different error page for blocked requests
 
-Requests blocked by a firewall rule with a _Block_ action would get a Cloudflare [1020 error code](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/#error-1020-access-denied) response. Cloudflare users could customize this error page for a zone in **Error Pages** > **1000 class errors**.
+Requests blocked by a firewall rule with a _Block_ action would get a Cloudflare [1020 error code](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1020/) response. Cloudflare users could customize this error page for a zone in **Error Pages** > **1000 class errors**.
 
 Requests blocked by a WAF custom rule will get a different response: the WAF block response. To customize the default block response, you can either:
 

src/content/docs/workers/platform/known-issues.mdx

@@ -52,7 +52,7 @@ return await fetch(request);
 
 ## Fetch API in CNAME setup
 
-When you make a subrequest using [`fetch()`](/workers/runtime-apis/fetch/) from a Worker, the Cloudflare DNS resolver is used. When a zone has a [Partial (CNAME) setup](/dns/zone-setups/partial-setup/), all hostnames that the Worker needs to be able to resolve require a dedicated DNS entry in Cloudflare's DNS setup. Otherwise the Fetch API call will fail with status code [530 (1016)](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/#error-1016-origin-dns-error).
+When you make a subrequest using [`fetch()`](/workers/runtime-apis/fetch/) from a Worker, the Cloudflare DNS resolver is used. When a zone has a [Partial (CNAME) setup](/dns/zone-setups/partial-setup/), all hostnames that the Worker needs to be able to resolve require a dedicated DNS entry in Cloudflare's DNS setup. Otherwise the Fetch API call will fail with status code [530 (1016)](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1016/).
 
 Setup with missing DNS records in Cloudflare DNS