Overall review and add conditions to view creation partial

Author: RebeccaTamachiro

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

@@ -81,7 +81,9 @@ Since the resolver policy will require a [DNS view](/dns/internal-dns/dns-views/
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-<Render file="internal-dns-view-create-dash"/>
+<Render file="internal-dns-view-create-dash" params={{
+	conditional: "get-started-detail"}}
+/>
 
 </TabItem> <TabItem label="API">
 
@@ -122,4 +124,6 @@ Use the rule settings object to define `resolve_dns_internally`, specifying `vie
 - `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.
 
-</TabItem> </Tabs>
+</TabItem> </Tabs>
+
+Once you add the Gateway resolver policy, it will be listed in the respective internal view under **Resolver policies referencing this view**.

src/content/partials/dns/internal-dns-view-create-dash.mdx

@@ -1,11 +1,21 @@
 ---
-{}
-
+params:
+  - conditional?
 ---
 
+import { Details, Render } from "~/components";
+
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account.
 2. Go to **Internal DNS** > **Views**.
 3. Select **Create a view**.
 4. Give your view a descriptive name.
+
+{ props.conditional === "get-started-detail" && (
+<Details header="DNS view configuration conditions">
+<Render file="internal-dns-view-conditions" />
+</Details>
+	)
+}
+
 5. Select **Manage zones** to add zones to your view. Select the internal zones that should be used to resolve queries sent by Gateway resolver to this view
 6. Choose **Save** to confirm.

src/content/partials/dns/internal-zone-create-dash.mdx

@@ -18,7 +18,7 @@ import { Details, Render } from "~/components";
 
 4. Add DNS records to your internal zone using your preferred option:
 - [Import](/dns/manage-dns-records/how-to/import-and-export/) a formatted BIND file.
-- Select **Add a record** > **Create** under the selected record type and **Save record** after filling in the required fields. Refer to [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) for details.
+- Select **Add a record** and choose **Create** under the record type you want to add. Refer to [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) for details.
 5. Repeat this process for each internal zone you wish to add.
 
 :::note

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

@@ -5,6 +5,8 @@
 
 - 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/dns-views/).
+- Each internal zone can be linked to multiple [views](/dns/internal-dns/dns-views/)[^20].
 - 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 (`.`).
+- 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 (`.`).
+
+[^20]: Logical groupings of internal DNS zones that are referenced by Gateway resolver policies to define how a specific query should be resolved.