[SSL] dvc-conflicting-records partial and details on custom certs (#25871)

* Create dvc-conflicting-records partial and add to CF4SaaS

* Add instructions on how to delete custom certificates

Author: RebeccaTamachiro

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/delegated-dcv.mdx

@@ -33,6 +33,8 @@ Once this is complete, Cloudflare will place two TXT DCV records - one for `exam
 
 If desired, you could also manually fetch the DCV tokens and share them with your customers.
 
+<Render file="dcv-conflicting-records" product="ssl" />
+
 ## Moved domains
 
 If you [move your SaaS zone to another account](/fundamentals/manage-domains/move-domain/), you will need to update the `CNAME` record with a new hostname value.

src/content/docs/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv.mdx

@@ -8,7 +8,7 @@ head:
     content: Delegated DCV — Domain Control Validation — SSL/TLS
 ---
 
-import { Example, FeatureTable } from "~/components";
+import { Example, FeatureTable, Render } from "~/components";
 
 Delegated DCV allows zones with [partial DNS setups](/dns/zone-setups/partial-setup/) - meaning authoritative DNS is not provided by Cloudflare - to delegate the DCV process to Cloudflare.
 
@@ -72,15 +72,7 @@ _acme-challenge.sub.example.com CNAME sub.example.com.<COPIED_VALIDATION_URL>.
 
 </Example>
 
-:::caution[Remove previous TXT records]
-
-Existing TXT records for `_acme-challenge` will conflict with the delegated DCV CNAME record. Make sure to check and remove records such as the following:
-
-```txt
-_acme-challenge.example.com TXT <CERTIFICATE_VALIDATION_VALUE>
-```
-
-:::
+<Render file="dcv-conflicting-records" product="ssl" />
 
 Once the `CNAME` records are in place, Cloudflare will add TXT DCV tokens for every hostname on the Advanced certificate that has a DCV delegation record in place, as long as the zone is [active](/dns/zone-setups/reference/domain-status/) on Cloudflare.
 

src/content/docs/ssl/edge-certificates/custom-certificates/uploading.mdx

@@ -179,9 +179,9 @@ To update a certificate in the dashboard:
 
 <DashButton url="/?to=/:account/:zone/ssl-tls/edge-certificates" />
 
-2. In **Edge Certificates**, locate a custom certificate and click on it to expand.
+2. In **Edge Certificates**, locate a custom certificate and select it to expand.
 
-3. Select the wrench icon and select **Replace SSL certificate and key**.
+3. Select the wrench button and choose **Replace SSL certificate and key**.
 
 4. Follow the same steps as [upload a new certificate](#upload-a-custom-certificate).
 
@@ -196,3 +196,15 @@ To update a certificate using the API, send a [`PATCH`](/api/resources/custom_ce
 To update the **Private Key Restriction** setting of a certificate, delete and re-add the certificate.
 
 :::
+
+---
+
+## Delete a custom certificate
+
+1. In the Cloudflare dashboard, go to the SSL/TLS **Edge Certificates** page.
+
+<DashButton url="/?to=/:account/:zone/ssl-tls/edge-certificates" />
+
+2. In **Edge Certificates**, locate a custom certificate and select it to expand.
+3. Select the cross button.
+4. Select **Confirm** to delete the certificate.

src/content/partials/ssl/dcv-conflicting-records.mdx

@@ -0,0 +1,14 @@
+---
+{}
+
+---
+
+:::caution[Remove previous TXT records]
+
+Existing TXT records for `_acme-challenge` will conflict with the delegated DCV CNAME record. Make sure to check and remove records such as the following:
+
+```txt
+_acme-challenge.example.com TXT <CERTIFICATE_VALIDATION_VALUE>
+```
+
+:::