[Chore] Fix links and broken anchor and update Style guide

src/content/docs/dns/dns-firewall/faq.mdx

@@ -32,7 +32,7 @@ Yes. `SERVFAIL` is treated like any other negative answer for caching purposes.
 
 <Details header="Does DNS Firewall support EDNS Client Subnet (ECS)?">
 
-Yes. Often, DNS providers want to see a client's IP via <GlossaryTooltip term="EDNS Client Subnet (ECS)">EDNS Client Subnet (ECS)</GlossaryTooltip> ([RFC 7871](https://www.rfc-editor.org/rfc/inline-errata/rfc7871.html)) because they serve geographically specific DNS answers based on the client's IP. With EDNS Client Subnet enabled, the DNS Firewall will forward the client's IP subnet along with the DNS query to the upstream nameserver.
+Yes. Often, DNS providers want to see a client's IP via <GlossaryTooltip term="EDNS Client Subnet (ECS)">EDNS Client Subnet (ECS)</GlossaryTooltip> ([RFC 7871](https://www.rfc-editor.org/rfc/rfc7871.html)) because they serve geographically specific DNS answers based on the client's IP. With EDNS Client Subnet enabled, the DNS Firewall will forward the client's IP subnet along with the DNS query to the upstream nameserver.
 
 When EDNS is enabled, the DNS Firewall gives out the geographically correct answer in cache based on the client IP subnet. To do this, the DNS Firewall segments its cache. For example:
 

src/content/docs/dns/zone-setups/subdomain-setup/setup/index.mdx

@@ -50,7 +50,7 @@ The availability of different setups will depend on both the parent zone setup a
 
 :::caution[* Subdomain zones in partial setup are not delegated]
 
-Subdomains using a partial setup represent an exception in the sense that [delegation](#subdomain-delegation) does not apply in this context. As explained in the dedicated [Partial (CNAME) setup section](/dns/zone-setups/partial-setup/), this setup is intended to simply proxy individual subdomains through Cloudflare. For completeness, however, this is listed as an option in this table and the [how-to guide](/dns/zone-setups/subdomain-setup/setup/parent-on-partial/) has detailed explanation on how to achieve a subdomain zone using partial setup.
+Subdomains using a partial setup represent an exception in the sense that delegation does not apply in this context. As explained in the dedicated [Partial (CNAME) setup section](/dns/zone-setups/partial-setup/), this setup is intended to simply proxy individual subdomains through Cloudflare. For completeness, however, this is listed as an option in this table and the [how-to guide](/dns/zone-setups/subdomain-setup/setup/parent-on-partial/) has detailed explanation on how to achieve a subdomain zone using partial setup.
 :::
 
 This table assumes zones that are in an [active status](/dns/zone-setups/reference/domain-status/). For example, if you need to add the parent zone to Cloudflare when its child zone already exists in a partial setup, you can [convert the parent zone to partial](/dns/zone-setups/partial-setup/setup/#1-convert-your-zone-and-review-dns-records) while it is still in pending status.

src/content/docs/style-guide/formatting/external-references.mdx

@@ -13,7 +13,7 @@ For general websites, consider the following recommendations about the link text
 * Authoritative sources for documents such as RFCs can have their own specific format for references, such as the RFC number.
 
 :::note
-When linking to a Cloudflare blog post, sometimes we use only "blog post" for the link text. 
+When linking to a Cloudflare blog post, sometimes we use only "blog post" for the link text.
 :::
 
 ## Referencing RFCs
@@ -37,8 +37,8 @@ When linking to an RFC (or RFC section), consider using a link to the following
 To get the link:
 
 1. Go to [RFC Editor](https://www.rfc-editor.org/rfc-index.html) and search for the RFC number.
-2. Select HTML to open the HTML version.
-3. (optional) Navigate to a specific section, if necessary.
+2. Select **HTML** to open the HTML version. If available, do **not** use **HTML with inline errata** as this version should not be used as reference.
+3. (Optional) Go to a specific section, if necessary.
 4. Use the current URL as the link target in Developer Documentation.
 
 URL example:

src/content/glossary/dns.yaml

@@ -47,7 +47,7 @@ entries:
     general_definition: |-
       ECS is a DNS extension that enables recursive DNS resolvers to include client IP address information in their DNS queries.
 
-      Not all resolvers use ECS but, if they do, usually a part of the IP address is omitted. Sending ECS headers is generally intended to reduce latency and speed up content delivery in connection to [CDNs](/glossary/?term=cdn) and [load balancers](https://www.cloudflare.com/learning/performance/what-is-load-balancing/). The ECS mechanism is specified in [RFC 7871](https://www.rfc-editor.org/rfc/inline-errata/rfc7871.html).
+      Not all resolvers use ECS but, if they do, usually a part of the IP address is omitted. Sending ECS headers is generally intended to reduce latency and speed up content delivery in connection to [CDNs](/glossary/?term=cdn) and [load balancers](https://www.cloudflare.com/learning/performance/what-is-load-balancing/). The ECS mechanism is specified in [RFC 7871](https://www.rfc-editor.org/rfc/rfc7871.html).
     associated_products:
       - Load Balancing
       - Cloudflare One