Overall text review

Author: RebeccaTamachiro

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

@@ -10,7 +10,7 @@ import { Details, Render } from "~/components";
 
 Internal DNS views are logical groupings of [internal DNS zones](/dns/internal-dns/internal-zones/). As explained in the [architecture overview](/dns/internal-dns/#architecture-overview), DNS views are referenced by [Gateway resolver policies](/cloudflare-one/policies/gateway/resolver-policies/) to define how a specific query should be resolved.
 
-Refer to the sections below for details on how to manage your DNS views, or consider the [get started](/dns/internal-dns/#architecture-overview) for the complete workflow.
+Refer to the sections below for details on how to manage your DNS views, or consider the [get started](/dns/internal-dns/#architecture-overview) for a complete workflow.
 
 ## Configuration conditions
 
@@ -28,7 +28,7 @@ Use the [Delete Internal DNS View](/api/resources/dns/subresources/settings/subr
 
 DNS views can be deleted even if they still have internal zones linked to them. The internal DNS zones will continue to exist but will be unlinked once the view is deleted.
 
-It is also possible to delete a DNS view that is being referenced by a Gateway resolver policy. In this case, queries matching the policy will return `SERVFAIL`.
+It is also possible to delete a DNS view that is being referenced by a Gateway resolver policy. In this case, queries matching the policy will return SERVFAIL.
 
 ## Other actions
 

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

@@ -62,7 +62,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 zones.
+Since the resolver policy will require a [DNS 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.
 
@@ -91,11 +91,11 @@ Besides selecting an internal DNS view when setting up your resolver policies, y
 
 </TabItem> <TabItem label="API">
 
-Use the API endpoints under [Zero Trust > Gateway > Rules](/api/resources/zero_trust/subresources/gateway/subresources/rules/) to set up resolver policies. Use the rule settings object to define `resolve_dns_internally`, specifying `view_id` and `fallback` option. The fallback options behave as follows:
+Use the API endpoints under [Zero Trust > Gateway > Rules](/api/resources/zero_trust/subresources/gateway/subresources/rules/) to set up resolver policies. For guidance about selectors, operators, and values, refer to [Gateway](/cloudflare-one/policies/gateway/resolver-policies/#selectors).
+
+Use the rule settings object to define `resolve_dns_internally`, specifying `view_id` and `fallback` option. The fallback options behave as follows:
 
 - `none`: Gateway DNS resolver returns the response as-is to the client.
 - `public_dns`: In case the response from the internal zone is REFUSED, NXDOMAIN, or a response with a CNAME type, Gateway DNS resolver sends the query to Cloudflare 1.1.1.1 public resolver and tries to resolve the query via public DNS.
 
-For guidance about selectors, operators, and values, refer to [Gateway](/cloudflare-one/policies/gateway/resolver-policies/#selectors).
-
 </TabItem> </Tabs>

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

@@ -51,8 +51,8 @@ flowchart LR
 
         B --Query--> Y
         X --Query + View ID--> Z
-        A --Connectivity--> B
-				A --Connectivity--> X
+        A --Query--> B
+				A --Query--> X
 				C --Query--> Y
 ```
 

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

@@ -23,7 +23,7 @@ When setting up internal zones, observe the following conditions:
 - Use other API endpoints, such as [`/batch`](/api/resources/dns/subresources/records/methods/batch/), to manage DNS records. Refer to [Batch record changes](/dns/manage-dns-records/how-to/batch-record-changes/#use-the-api) for details.
 3. Repeat this process for each internal zone you wish to add.
 
-Since the resolver policy configuration will require a view, you must link the internal zones to at least one view to be able to use them when routing requests to Internal DNS. For a full procedure overview, refer to [get started](/dns/internal-dns/get-started/).
+Since the resolver policy configuration will require a DNS view, you must link the internal zones to at least one view to be able to use them when routing requests to Internal DNS. For a full procedure overview, refer to [get started](/dns/internal-dns/get-started/).
 
 
 ## Other actions

src/content/partials/dns/internal-reference-zone-api.mdx

@@ -12,7 +12,7 @@ https://api.cloudflare.com/client/v4/zones/8a904aeb565c42cfa207d98f6edea2f3/dns_
 --header "Content-Type: application/json" \
 --data '{
     "internal_dns": {
-        "reference_zone_id": "8e64c6fb4b514f3faf64de81efc11e51D"
+        "reference_zone_id": "8e64c6fb4b514f3faf64de81efc11e51"
     }
   }'
 ```