Address comments from PCX review

Author: RebeccaTamachiro

src/content/docs/ssl/client-certificates/create-a-client-certificate.mdx

@@ -33,9 +33,9 @@ To create a client certificate on the Cloudflare dashboard:
 Client certificates created on the dashboard are issued by a [Cloudflare-managed CA](/ssl/client-certificates/#how-it-works). If you need to use certificates issued by another CA, use the API to [bring your own CA](/ssl/client-certificates/byo-ca/) instead.
 :::
 
-4. Select a value for **Certificate Validity**, and choose **Create**.
-5. Make sure to copy the certificate and private key as they will no longer be displayed after creation.
-6. Select **OK** to confirm.
+3. Select a value for **Certificate Validity**, and choose **Create**.
+4. Make sure to copy the certificate and private key as they will no longer be displayed after creation.
+5. Select **OK** to confirm.
 
 ## Next steps
 

src/content/docs/ssl/edge-certificates/additional-options/always-use-https.mdx

@@ -36,7 +36,7 @@ If only some parts of your application can support HTTPS traffic, do not enable
 
 To enable **Always Use HTTPS** in the dashboard:
 
-1. In the Cloudflare dashboard, go to the **SSL/TLS Overview** page for the respective application.
+1. In the Cloudflare dashboard, go to the **SSL/TLS Overview** page.
 
    <DashButton url="/?to=/:account/:zone/ssl-tls" />
 

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

@@ -9,7 +9,7 @@ description: Learn how renewal and expiration work when using Cloudflare Custom
 
 ---
 
-import { GlossaryTooltip } from "~/components"
+import { GlossaryTooltip, DashButton } from "~/components"
 
 ## Renew custom certificates
 
@@ -44,6 +44,9 @@ For example if you have a custom certificate made of an ECSDA and a RSA certific
 
 If you no longer want to use your custom certificate but still want your website or application to be covered with SSL/TLS, you can do the following:
 
-1. Go to the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page.
+1. In the Cloudflare dashboard, go to the **Edge Certificates** page.
+
+   <DashButton url="/?to=/:account/:zone/ssl-tls/edge-certificates" />
+
 2. Make sure there is already an active [universal](/ssl/edge-certificates/universal-ssl/) or [advanced](/ssl/edge-certificates/advanced-certificate-manager/) certificate covering the same hostnames.
 3. Delete your custom certificate.

src/content/docs/ssl/reference/compliance-and-vulnerabilities.mdx

@@ -5,6 +5,8 @@ title: PCI compliance and vulnerabilities mitigation
 
 ---
 
+import { DashButton } from "~/components";
+
 Both [TLS 1.0 and TLS 1.1](/ssl/reference/protocols/) are insufficient for protecting information due to known vulnerabilities. Specifically for Cloudflare customers, the primary impact of PCI is that TLS 1.0 and TLS 1.1 are insufficient to secure payment card related traffic.
 
 PCI standards recommend using TLS 1.2 or higher. Refer to [Compliance standards](/ssl/edge-certificates/additional-options/cipher-suites/compliance-status/) for a list of recommended cipher suites.
@@ -15,13 +17,11 @@ Cloudflare also [implements mitigations against known vulnerabilities](#known-vu
 
 To configure your Cloudflare domain to only allow connections using TLS 1.2 or newer protocols:
 
-1. Log in to the Cloudflare dashboard.
-
-2. Select your Cloudflare account and website or application.
+1. In the Cloudflare dashboard, go to the **Edge Certificates** page.
 
-3. Go to the [**Edge Certificates**](https://dash.cloudflare.com/?to=/:account/:zone/ssl-tls/edge-certificates) page.
+   <DashButton url="/?to=/:account/:zone/ssl-tls/edge-certificates" />
 
-4. For **Minimum TLS Version**, select **TLS 1.2** or higher.
+2. For **Minimum TLS Version**, select **TLS 1.2** or higher.
 
 Refer to [Minimum TLS version](/ssl/edge-certificates/additional-options/minimum-tls/) for more information about this setting and other setup options.