Apply suggestions from code review

Co-authored-by: Maddy <[email protected]>

Author: RebeccaTamachiro

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

@@ -39,7 +39,7 @@ It is also possible to delete a DNS view that is being referenced by a Gateway r
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
 2. Go to **Internal DNS** > **Views**.
 3. Find the view you want to delete.
 4. Select the three dots in the corresponding row and choose *Delete*.

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

@@ -109,7 +109,7 @@ Besides selecting an internal DNS view when setting up your resolver policies, y
 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **Resolver policies**.
 2. Select **Add a policy** and enter a name and description.
 3. Create an expression for the traffic you wish to route. For guidance about selectors, operators, and values, refer to [Gateway](/cloudflare-one/policies/gateway/resolver-policies/#selectors).
-4. Select **Use Internal DNS**. In the dropdown, choose the view that queries matching the expression should be sent to.
+4. Select **Use Internal DNS**. Choose the view that queries matching the expression should be sent to.
 5. (Optional) Adjust the option to **fallback through public DNS** according to your use case.
 - Off: Gateway DNS resolver returns the response as-is to the client.
 - On: 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.

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

@@ -24,7 +24,7 @@ A wildcard record (`*.example.local`) in the matching internal zone will take pr
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
 2. Go to **Internal DNS** and select a zone.
 3. Within the selected zone, go to **Reference zone**.
 4. Select **Add reference zone**. If your zone already has a reference zone set up, you must first remove it. As explained in the [configuration conditions](#configuration-conditions), each internal zone can only reference one other zone at a time.

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

@@ -5,7 +5,7 @@ params:
 
 import { Details, Render } from "~/components";
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
 2. Go to **Internal DNS** > **Views**.
 3. Select **Create a view**.
 4. Give your view a descriptive name.
@@ -17,5 +17,5 @@ import { Details, Render } from "~/components";
 	)
 }
 
-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
+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

@@ -5,7 +5,7 @@ params:
 
 import { Details, Render } from "~/components";
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account.
+1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
 2. Go to **Internal DNS** and select **Create an internal zone**.
 3. Give your internal zone a name.