Fix broken links and point from get-started to dedicated pages

Author: RebeccaTamachiro

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

@@ -8,7 +8,7 @@ sidebar:
 
 import { Details, Render } from "~/components";
 
-Internal DNS views are logical groupings of [internal DNS zones](/dns/internal-dns/how-to/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.
+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.
 

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

@@ -40,7 +40,7 @@ Although there are some steps that can be achieved on the dashboard, currently t
 
 ## 1. Set up your internal DNS zone
 
-1. Use the [Create Zone](/api/resources/zones/) endpoint to create an internal zone. Specify your account ID and set the `type` to `internal`.
+1. Use the [Create Zone](/api/resources/zones/) endpoint to create an [internal zone](/dns/internal-dns/internal-zones/). Specify your account ID and set the `type` to `internal`.
 
 <Details header="Internal zone configuration conditions">
 <Render file="internal-zones-conditions" />
@@ -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, 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 DNS.
 
 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,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/how-to/internal-zones/) and [views](/dns/internal-dns/how-to/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 according to context, such as its source IP.
 
 <Render file="internal-dns-beta-note" />
 

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/how-to/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/) 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
 

src/content/partials/dns/internal-dns-view-conditions.mdx

@@ -3,7 +3,7 @@
 
 ---
 
-- DNS views can be empty, with no [internal zones](/dns/internal-dns/how-to/internal-zones/) linked to them.
+- DNS views can be empty, with no [internal zones](/dns/internal-dns/internal-zones/) linked to them.
 - A DNS view cannot contain public DNS zones [^1].
 - Each internal DNS zone name must be unique within a given DNS view.
 

src/content/partials/dns/internal-zones-conditions.mdx

@@ -5,6 +5,6 @@
 
 - Internal zones can contain the same [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) that Cloudflare supports for public zones.
 - An internal zone can have the same name as a public zone in the same account.
-- Each internal zone can be linked to multiple [views](/dns/internal-dns/how-to/dns-views/).
+- Each internal zone can be linked to multiple [views](/dns/internal-dns/dns-views/).
 - There can be several internal zones with the same name in one account. However, two internal zones with the same name cannot be linked to the same view.
 - Internal zones are not subject to any top-level domain (TLD) restrictions. This means that an internal zone can be created if its TLD is not registered publicly (for example, `xyz.local`), if it is created on the TLD itself (`local`), or even if on the root (`.`).