Text review and more context around the role of NS records

Author: RebeccaTamachiro

src/content/docs/dns/manage-dns-records/troubleshooting/cname-domain-verification.mdx

@@ -9,10 +9,15 @@ head:
 
 ---
 
-When configuring services from external providers - such as email services, for example - it is possible that they require you to verify your domain by placing a CNAME record at your zone.
-(for example: `<value>._domainkey.example.com` CNAME `<hostname>.<service provider domain>`)
+import { Example } from "~/components";
 
-Consider the following sections if this is not working correctly for you.
+When configuring services from external providers - such as email services, for example - it is possible that they require you to verify your domain by placing a CNAME record at your zone, similar to the following:
+
+```
+<value>._domainkey.example.com CNAME <hostname>.<service provider domain>
+```
+
+Consider the sections below if this is not working correctly for you.
 
 ## Causes
 
@@ -21,15 +26,15 @@ You may find issues if you have one of the following:
 * The CNAME record you created for domain verification is set to [**Proxied**](/dns/proxy-status/).
 * The CNAME record is correctly set to DNS only (not proxied) but, in your [zone settings](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings), [**CNAME flattening for all CNAME records**](/dns/cname-flattening/set-up-cname-flattening/#for-all-cname-records) is enabled.
 * The CNAME record is correctly set to DNS only (not proxied) but CNAME flattening is [enabled for that record specifically](/dns/cname-flattening/set-up-cname-flattening/#per-record).
-* A [NS record](https://www.cloudflare.com/learning/dns/dns-records/dns-ns-record/) exists for the subdomain
+* An [NS record](https://www.cloudflare.com/learning/dns/dns-records/dns-ns-record/) exists, causing a different DNS provider to be authoritative for the subdomain.
 
 ## Solution
 
 Make sure that:
 
 * In your zone DNS settings: [**CNAME flattening for all CNAME records**](/dns/cname-flattening/) is disabled.
 * On the DNS records table: you have filled in the CNAME record fields correctly, proxy status is set to **DNS only**, and **Flatten** is disabled.
-* Review the NS configuration, and either:
-  * make sure that your record is configured as expected with the service provider that the NS record points towards
-  * remove the NS record so that the DNS resolution this record is resolved to the target you've configured on Cloudflare. (but be careful as this may affect other records!)
+* You have the correct NS configuration, and either:
+  * Make sure that the CNAME record is set as expected with the DNS provider that the NS record points to.
+  * Review your configuration for other DNS records that may be affected by the NS record. Once you are aware of any consequences or have made any necessary adjustments, remove the NS record so that the CNAME is resolved to the target you configured on Cloudflare.