Move SSL recommendations into prep and revamp other steps

Author: RebeccaTamachiro

src/content/docs/dns/zone-setups/partial-setup/setup.mdx

@@ -9,7 +9,7 @@ head:
 
 ---
 
-import { Details, Render, GlossaryTooltip } from "~/components";
+import { Details, Render, GlossaryTooltip, Steps } from "~/components";
 
 <Render file="partial-setup-definition" />
 
@@ -21,25 +21,29 @@ A partial setup is only available to customers on a Business or Enterprise plan.
 
 ## Before you begin
 
+<Steps>
 1. Create a Cloudflare account and add your domain.
 2. Choose **Business** or **Enterprise** as your plan.
 3. If you are onboarding a new domain to Cloudflare, ignore the instructions to change your nameservers.
+4. (Recommended) Plan for SSL/TLS certificates:
 
-### (Optional) Plan for SSL/TLS certificates
+    If you are only using [Universal SSL](/ssl/edge-certificates/universal-ssl/) prior to converting your zone, a certificate will be provisioned for your subdomains only after each of the respective DNS records ([step 3](#3-add-dns-records) below) are [proxied](/dns/manage-dns-records/reference/proxied-dns-records/). Refer to [Enable Universal SSL](/ssl/edge-certificates/universal-ssl/enable-universal-ssl/#partial-dns-setup) for details.
 
-If you are only using [Universal SSL](/ssl/edge-certificates/universal-ssl/) prior to converting your zone, a certificate will be provisioned for your subdomains only after each of the respective DNS records are [proxied](/dns/manage-dns-records/reference/proxied-dns-records/). Refer to [Enable universal SSL](/ssl/edge-certificates/universal-ssl/enable-universal-ssl/#partial-dns-setup) for details.
+    If your domain is sensitive to downtime, instead of using Universal SSL, consider using an [advanced certificate](/ssl/edge-certificates/advanced-certificate-manager/) with [delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/#setup).
+</Steps>
 
-If your domain is sensitive to downtime, instead of using Universal SSL, consider using an [advanced certificate](/ssl/edge-certificates/advanced-certificate-manager/) with [delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/#setup).
+## 1. Convert your zone and review DNS records
 
-## Add your domain to Cloudflare
+<Steps>
+1. On the **Overview** page, select **Convert to CNAME DNS Setup**.
+2. Select **Convert** to confirm.
+3. Save the information from the **Verification TXT Record**. If you lose the information, you can also access it by going to **DNS** > **Records** > **Verification TXT Record**.
+4. Make sure that you have all the DNS records for subdomains that you want to proxy through Cloudflare.
+</Steps>
 
-4. On the **Overview** page, select **Convert to CNAME DNS Setup**.
-5. Select **Convert** to confirm.
-6. Save the information from the **Verification TXT Record**. If you lose the information, you can also access it by going to **DNS** > **Records** > **Verification TXT Record**.
+## 2. Verify ownership for your domain
 
-## Verify ownership for your domain
-
-Once you [add your domain to Cloudflare](#add-your-domain-to-cloudflare), add the **Verification TXT Record** at your authoritative DNS provider. Cloudflare will verify the TXT record and send a confirmation email. This can take up to a few hours.
+Add the **Verification TXT Record** at your authoritative DNS provider. Cloudflare will verify the TXT record and send a confirmation email. This can take up to a few hours.
 
 <Details header="Example verification record">
 A verification record for `example.com` might be:
@@ -57,24 +61,22 @@ After creating the record, you can use this [Dig Web Interface link](https://dig
 
 That record must remain in place for as long as your domain is active on the partial setup on Cloudflare.
 
-## Add DNS records
+## 3. Add DNS records
 
-1. In Cloudflare, [add an `A`, `AAAA`, or `CNAME` record](/dns/manage-dns-records/how-to/create-dns-records/).
-2. At your authoritative DNS provider:
-   1. Remove any existing `A`, `AAAA`, or `CNAME` records on the hostname you want to proxy to Cloudflare.
-   2. Add a `CNAME` record for `{your-hostname}.cdn.cloudflare.net`.
+<Steps>
+1. At your authoritative DNS provider:
+   1. Create `CNAME` records pointing to `{your-hostname}.cdn.cloudflare.net` for every hostname you wish to proxy through Cloudflare.
 
-       <details>
-       <summary>
-       Example CNAME record at authoritative DNS provider
-       </summary>
+    <Details header="Example CNAME record at authoritative DNS provider">
 
-      The `CNAME` record for `www.example.com` would be:
+    The `CNAME` record for `www.example.com` would be:
 
-      ```txt
-      www.example.com CNAME www.example.com.cdn.cloudflare.net
-      ```
+    ```txt
+    www.example.com CNAME www.example.com.cdn.cloudflare.net
+    ```
+    </Details>
 
-       </details>
+    2. Remove any previously existing `A`, `AAAA`, or `CNAME` records referencing the hostnames you want to proxy through Cloudflare. For these hostnames, leave only the records pointing to `{your-hostname}.cdn.cloudflare.net`.
 
-   3. Repeat this process for each subdomain proxied to Cloudflare.
+2. Repeat this process for each subdomain that should be proxied to Cloudflare.
+</Steps>