Move conditions into partials and replace in get-started

Author: RebeccaTamachiro

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

@@ -6,7 +6,7 @@ sidebar:
   label: Views
 ---
 
-import { Details } from "~/components";
+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.
 
@@ -16,9 +16,7 @@ Refer to the sections below for details on how to manage your DNS views, or cons
 
 When setting up DNS views, observe the following conditions:
 
-- DNS views can be empty, with no [internal zones](/dns/internal-dns/how-to/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.
+<Render file="internal-dns-view-conditions" />
 
 ## Create a view
 
@@ -36,6 +34,4 @@ It is also possible to delete a DNS view that is being referenced by a Gateway r
 
 - [Update a DNS view](/api/resources/dns/subresources/settings/subresources/views/methods/edit/) (`PATCH`)
 - [Get view details](/api/resources/dns/subresources/settings/subresources/views/methods/get/) (`GET`)
-- [List DNS views](/api/resources/dns/subresources/settings/subresources/views/methods/list/) (`GET`)
-
-[^1]: DNS zones that contain public DNS records and are accessible by public resolvers.
+- [List DNS views](/api/resources/dns/subresources/settings/subresources/views/methods/list/) (`GET`)

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

@@ -43,7 +43,7 @@ Although there are some steps that can be achieved on the dashboard, currently t
 1. Use the [Create Zone](/api/resources/zones/) endpoint to create an internal zone. Specify your account ID and set the `type` to `internal`.
 
 <Details header="Internal zone configuration conditions">
-TBD > add partial with requirements from Setup page
+<Render file="internal-zones-conditions" />
 </Details>
 
 2. Add DNS records to your internal zone using your preferred option:
@@ -66,8 +66,9 @@ TBD > add full API call example using IDs mentioned above
 Since the resolver policy will require a view, 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.
-<Details header="View configuration conditions">
-TBD > add partial with requirements from Setup page
+
+<Details header="DNS view configuration conditions">
+<Render file="internal-dns-view-conditions" />
 </Details>
 
 ## 3. Configure Gateway policies

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

@@ -6,7 +6,7 @@ sidebar:
   label: Internal zones
 ---
 
-import { Example } from "~/components";
+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.
 
@@ -16,11 +16,7 @@ Internal DNS zones do not get assigned Cloudflare nameservers and can only be qu
 
 When setting up internal zones, observe the following conditions:
 
-- 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/).
-- 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 (`.`).
+<Render file="internal-zones-conditions" />
 
 ## Create an internal zone
 

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

@@ -0,0 +1,10 @@
+---
+{}
+
+---
+
+- DNS views can be empty, with no [internal zones](/dns/internal-dns/how-to/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.
+
+[^1]: DNS zones that contain public DNS records and are accessible by public resolvers.

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

@@ -0,0 +1,10 @@
+---
+{}
+
+---
+
+- 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/).
+- 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 (`.`).