Add more context

Author: maxvp

src/content/docs/cloudflare-one/policies/gateway/resolver-policies.mdx

@@ -10,7 +10,7 @@ head:
     content: Resolver policies
 ---
 
-import { Render } from "~/components";
+import { Render, Badge } from "~/components";
 
 :::note
 Only available on Enterprise plans.
@@ -42,11 +42,11 @@ Gateway will route user traffic to your configured DNS resolver based on the mat
 
 You may use resolver policies if you require access to non-publicly routed domains, such as private network services or internal resources. You may also use resolver policies if you need to access a protected DNS service or want to simplify DNS management for multiple locations.
 
-### Internal DNS
+### Internal DNS <Badge text="Beta" variant="caution" size="small" />
 
-[Cloudflare Internal DNS](/dns/internal-dns/) allows you to manage DNS records for internal resources restricted to a private network. DNS zones configured in Internal DNS can only be queried by the Gateway resolver. With resolver policies, you can specifically determine how Gateway resolves internal DNS queries.
+[Cloudflare Internal DNS](/dns/internal-dns/) allows you to manage DNS records for internal resources on a private network. DNS zones configured in Internal DNS can only be queried by the Gateway resolver. With resolver policies, you can determine how Gateway resolves these internal DNS queries.
 
-To get started with resolving internal DNS records with resolver policies, refer to [Get started](/dns/internal-dns/get-started/).
+To get started with resolving internal DNS queries with resolver policies, refer to [Get started](/dns/internal-dns/get-started/).
 
 ### Local Domain Fallback