Overall review and link to iDNS from docs landing page

Author: RebeccaTamachiro

src/content/docs/dns/index.mdx

@@ -17,6 +17,8 @@ Leverage Cloudflare's global network to deliver excellent performance and reliab
 
 Cloudflare DNS is a fast, resilient and easy-to-manage authoritative DNS service. It delivers excellent performance and reliability to your domain while also protecting your business from [DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/) and [route leaks and hijacking](https://www.cloudflare.com/learning/security/glossary/bgp-hijacking/). To know where to begin, refer to [Get started](/dns/get-started/).
 
+Enterprise customers can also use Cloudflare DNS for their private network with [Intenal DNS (Beta)](/dns/internal-dns/)
+
 ***
 
 ## Features

src/content/docs/dns/internal-dns/index.mdx

@@ -21,7 +21,7 @@ Simplify private network management with Cloudflare DNS for your internal resour
 
 <Plan type="enterprise" />
 
-Manage DNS records that should only be accessible within your private network. Internal DNS [zones](/dns/internal-dns/internal-zones/) and [views](/dns/internal-dns/dns-views/) pair up with [Gateway resolver policies](/cloudflare-one/policies/gateway/resolver-policies/) so that you can control how a DNS query should be responded to according to the query context, such as query source IP.
+Manage DNS records that should only be accessible within your private network. Internal DNS [zones](/dns/internal-dns/internal-zones/) and [views](/dns/internal-dns/dns-views/) pair up with [Gateway resolver policies](/cloudflare-one/policies/gateway/resolver-policies/) so that you can control how a DNS query should be responded to according to query context, such as query source IP.
 
 <Render file="internal-dns-beta-note" />
 

src/content/docs/dns/internal-dns/internal-zones/internal-dns-records.mdx

@@ -16,7 +16,7 @@ Refer to [Manage DNS records](/dns/manage-dns-records/how-to/create-dns-records/
 
 ## CNAME flattening in Internal DNS
 
-With CNAME flattening, Cloudflare finds the final target content that a CNAME points to and then returns this content instead of a CNAME record. With Internal DNS, CNAME flattening is applied by default and cannot be turned off.
+With [CNAME flattening](/dns/cname-flattening/), Cloudflare finds the final target content that a CNAME points to and then returns this content instead of a CNAME record. With Internal DNS, CNAME flattening is applied by default and cannot be turned off.
 
 Cloudflare will try to flatten the CNAME record considering both the specified [DNS view](/dns/internal-dns/dns-views/) and any existing [reference zones](/dns/internal-dns/internal-zones/reference-zones/). If the reference zone then has another CNAME, the record will again be considered from the perspective of the original view.
 

src/content/docs/dns/internal-dns/internal-zones/reference-zones.mdx

@@ -10,7 +10,7 @@ import { Example, Render, Tabs, TabItem } from "~/components";
 <Render file="internal-reference-zone-intro"/>
 
 :::note
-A wildcard record (`*.example.local`) in the matching internal zone will take precedence over an exact match in a referenced zone.
+A wildcard record (`*.example.local`) in the matching internal zone will take precedence over an exact match in a reference zone.
 :::
 
 ## Configuration conditions