Use specific header for more emphasis and better linking

Author: RebeccaTamachiro

src/content/docs/dns/foundation-dns/advanced-nameservers.mdx

@@ -14,6 +14,7 @@ Consider the sections below for details about advanced nameservers, and refer to
 
 :::note
 <Render file="ns-advanced-vs-custom" />
+Also, [some behaviors are different](/dns/foundation-dns/setup/#differences-from-standard-nameservers) when compared to standard nameservers.
 :::
 
 ## Anycast network groups

src/content/docs/dns/foundation-dns/setup.mdx

@@ -17,27 +17,26 @@ Before opting in for advanced nameservers, consider the following:
 
 - <Render file="ns-advanced-vs-custom" />
 
-- Some behaviors are different from standard Cloudflare nameservers:
-    - Wildcard records: if moving from standard Cloudflare nameservers to Foundation DNS advanced nameservers, make sure to explicitly create records for subdomains currently covered by wildcard records (`*.example.com`).
-    - Subdomain delegation: once a subdomain is delegated via NS records, Cloudflare will not serve any other records (such as A, TXT, or CNAME) on  that subdomain from the parent zone, even if those records exist.
-
-		<Details header="Example">
-
-		<Example>
-
-		DNS management for **example.com**
-
-		| **Type** | **Name** | **Content**               |
-		| -------- | -------- | ------------------------- |
-		| NS     | www      | ns1.externalhost.com     |
-		| NS     | www      | ns2.externalhost.com  |
-		| TXT    | www      | "5bb16e6b5a444eedb48ace40c471bcc9" |
-		| A     | www      | `192.0.2.1` |
-		</Example>
-
-		In this example, the TXT record and the A record for `www.example.com` will not be served.
-
-		</Details>
+### Differences from standard nameservers
+
+Some behaviors are different from standard Cloudflare nameservers:
+- Wildcard records: if moving from standard Cloudflare nameservers to Foundation DNS advanced nameservers, make sure to explicitly create records for subdomains currently covered by wildcard records (`*.example.com`).
+- Subdomain delegation: once a subdomain is delegated via NS records, Cloudflare will not serve any other records (such as A, TXT, or CNAME) on  that subdomain from the parent zone, even if those records exist.
+
+<Details header="Example">
+
+<Example>
+DNS management for **example.com**
+| **Type** | **Name** | **Content**               |
+| -------- | -------- | ------------------------- |
+| NS     | www      | ns1.externalhost.com     |
+| NS     | www      | ns2.externalhost.com  |
+| TXT    | www      | "5bb16e6b5a444eedb48ace40c471bcc9" |
+| A     | www      | `192.0.2.1` |
+</Example>
+
+In this example, the TXT record and the A record for `www.example.com` will not be served.
+</Details>
 
 ## Enable on a zone