First pass following PM review: adjust wording

Author: RebeccaTamachiro

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

@@ -11,10 +11,10 @@ Besides using [Gateway analytics](/cloudflare-one/insights/analytics/gateway/) f
 
 For detailed metrics, use the [GraphQL API](/analytics/graphql-api/). Refer to the GraphQL Analytics API documentation for guidance on how to [get started](/analytics/graphql-api/getting-started/).
 
-The [schemas](/analytics/graphql-api/getting-started/querying-basics/) added to cover Internal DNS are the following:
+The [fields](/analytics/graphql-api/getting-started/querying-basics/) added to cover Internal DNS are the following:
 
 - `InternalDNSFallbackStrategy`: The fallback strategy applied to the internal DNS response. Empty if no fallback strategy was applied.
-- `InternalDNSRCode`: The return code sent back by the internal DNS service.
+- `InternalDNSRCode`: The response code sent back by the internal DNS service.
 - `InternalDNSViewID`: The view identifier that was sent to the internal DNS service.
 - `InternalDNSZoneID`: The internal zone identifier returned by the internal DNS service.
 

src/content/docs/dns/internal-dns/get-started.mdx

@@ -61,7 +61,7 @@ Although there are some steps that can be achieved on the dashboard, currently t
 
 ## 2. Link your internal zone to a view
 
-Since the resolver policy will require a [view](/dns/internal-dns/dns-views/), you must have at least one view to be able to route requests to Internal DNS.
+Since the resolver policy will require a [view](/dns/internal-dns/dns-views/), you must have at least one view to be able to route requests to internal zones.
 
 1. Use the [Create Internal DNS View](/api/resources/dns/subresources/settings/subresources/views/methods/create/) endpoint. For each view you create, list all the internal zones that should be grouped under that view.
 

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

@@ -21,13 +21,13 @@ 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 according to context, such as its 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 the query context, such as its source IP.
 
 <Render file="internal-dns-beta-note" />
 
 ## Architecture overview
 
-Internal DNS queries can only be resolved via Cloudflare Gateway, which acts as an interface between the client and Internal DNS views.
+Internal DNS queries can only be resolved via the Cloudflare Gateway resolver, which acts as an interface between the DNS client and Internal DNS zones.
 
 To connect to Cloudflare, you can use [WARP](/cloudflare-one/connections/connect-devices/warp/), any of the DNS endpoints supported with [DNS locations](/cloudflare-one/connections/connect-devices/agentless/dns/locations/), or [Magic WAN on-ramps](/magic-wan/on-ramps/).