Separate Gateway and resolver policies to reflect plan difference

Author: RebeccaTamachiro

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

@@ -15,7 +15,7 @@ Although there are some steps that can be achieved on the dashboard, currently t
 
 <Render file="internal-dns-beta-note" />
 
-- Make sure you have an Enterprise account with access to [Cloudflare Gateway](/cloudflare-one/policies/gateway/) and [Internal DNS](/dns/internal-dns/).
+- Make sure you have an Enterprise account with access to [Gateway resolver policies](/cloudflare-one/policies/gateway/resolver-policies/) and [Internal DNS](/dns/internal-dns/).
 - If you are not familiar with how to use Cloudflare API, refer to [Fundamentals](/fundamentals/api/get-started/).
 - If you will be using an API token for authentication, make sure you have the following permissions:
 

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

@@ -10,7 +10,7 @@ import { Example, Render } from "~/components";
 
 Internal DNS zones are groupings of internal DNS records. While [public DNS records](/dns/manage-dns-records/) contain information about resources that you want to make available to the public Internet, internal DNS records allow you to manage resources that should only be available within your private network.
 
-Internal DNS zones do not get assigned Cloudflare nameservers and can only be queried via [Cloudflare Gateway](/cloudflare-one/policies/gateway/) when linked to a [DNS view](/dns/internal-dns/dns-views/). The Gateway configuration must exist within the same Cloudflare account where the internal zone exists.
+Internal DNS zones do not get assigned Cloudflare nameservers and can only be queried via [Cloudflare Gateway](/cloudflare-one/policies/gateway/resolver-policies/) when linked to a [DNS view](/dns/internal-dns/dns-views/). The Gateway configuration must exist within the same Cloudflare account where the internal zone exists.
 
 ## Configuration conditions