Final updates in dash instructions

pedrosousa · pedrosousa · commit f3fdde46aaab · 2025-01-09T15:00:21.000Z
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/salesforce-commerce-cloud.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/salesforce-commerce-cloud.mdx
@@ -5,16 +5,21 @@ head:
   - tag: title
     content: Salesforce Commerce Cloud | Provider guides
 description: Learn how to configure your Enterprise zone with Salesforce Commerce Cloud.
-
 ---
 
-import { Details, Render } from "~/components"
+import { Details, Render } from "~/components";
 
-<Render file="provider-guide-intro" params={{ one: "Salesforce Commerce Cloud" }} />
+<Render
+	file="provider-guide-intro"
+	params={{ one: "Salesforce Commerce Cloud" }}
+/>
 
 ## Benefits
 
-<Render file="provider-guide-benefits" params={{ one: "Salesforce Commerce Cloud" }} />
+<Render
+	file="provider-guide-benefits"
+	params={{ one: "Salesforce Commerce Cloud" }}
+/>
 
 ## How it works
 
@@ -24,7 +29,7 @@ For additional detail about how traffic routes when O2O is enabled, refer to [Ho
 
 To enable O2O requires the following:
 
-1. Your SFCC environment must be configured as an "SFCC Proxy Zone". If you currently have an "SFCC Legacy Zone", you cannot enable O2O. More details on the different types of SFCC configurations can be found [here](https://help.salesforce.com/s/articleView?id=cc.b2c_ecdn_proxy_zone_faq.htm\&type=5).
+1. Your SFCC environment must be configured as an "SFCC Proxy Zone". If you currently have an "SFCC Legacy Zone", you cannot enable O2O. More details on the different types of SFCC configurations can be found [here](https://help.salesforce.com/s/articleView?id=cc.b2c_ecdn_proxy_zone_faq.htm&type=5).
 2. Your own Cloudflare zone on an Enterprise plan.
 
 If you meet the above requirements, O2O can then be enabled per hostname. To enable O2O for a specific hostname within your Cloudflare zone, [create](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records) a Proxied `CNAME` DNS record with a target of the `CNAME` provided by SFCC Business Manager, which is the dashboard used by SFCC customers to configure their storefront environment.
@@ -41,7 +46,6 @@ The `CNAME` provided by SFCC Business Manager will resemble `commcloud.prod-abcd
 
 For O2O to be configured properly, make sure your Proxied DNS record targets your SFCC CNAME **directly**. Do not indirectly target the SFCC CNAME by targeting another Proxied DNS record in your Cloudflare zone which targets the SFCC CNAME.
 
-
 <Details header="Correct configuration">
 
 For example, if the hostnames routing traffic to SFCC are `www.example.com` and `preview.example.com`, the following is a **correct** configuration in your Cloudflare zone:
@@ -51,10 +55,8 @@ For example, if the hostnames routing traffic to SFCC are `www.example.com` and
 | `CNAME` | `www.example.com`     | `commcloud.prod-abcd-example-com.cc-ecdn.net` | Proxied      |
 | `CNAME` | `preview.example.com` | `commcloud.prod-abcd-example-com.cc-ecdn.net` | Proxied      |
 
-
 </Details>
 
-
 <Details header="Incorrect configuration">
 
 And, the following is an **incorrect** configuration because `preview.example.com` indirectly targets the SFCC CNAME via the `www.example.com` Proxied DNS record, which means O2O will not be properly enabled for hostname `preview.example.com`:
@@ -64,7 +66,6 @@ And, the following is an **incorrect** configuration because `preview.example.co
 | `CNAME` | `www.example.com`     | `commcloud.prod-abcd-example-com.cc-ecdn.net` | Proxied      |
 | `CNAME` | `preview.example.com` | `www.example.com`                             | Proxied      |
 
-
 </Details>
 
 ## Product compatibility
@@ -73,7 +74,10 @@ And, the following is an **incorrect** configuration because `preview.example.co
 
 ## Additional support
 
-<Render file="provider-guide-help" params={{ one: "Salesforce Commerce Cloud" }} />
+<Render
+	file="provider-guide-help"
+	params={{ one: "Salesforce Commerce Cloud" }}
+/>
 
 ### Resolving SSL errors using Cloudflare Managed Certificates
 
@@ -84,25 +88,25 @@ If you do have a `CAA` record, verify that it permits SSL certificates to be iss
 ### Best practice Zone-level configuration
 
 1. Set **Minimum TLS version** to **TLS 1.2**
-   1. Navigate to **SSL/TLS > Edge Certificates**, scroll down the page to find **Minimum TLS Version**, and set it to *TLS 1.2*. This setting applies to every Proxied DNS record in your Zone.
+   1. Navigate to **SSL/TLS > Edge Certificates**, scroll down the page to find **Minimum TLS Version**, and set it to _TLS 1.2_. This setting applies to every Proxied DNS record in your Zone.
 2. Match the **Security Level** set in **SFCC Business Manager**
-   1. *Option 1: Zone-level* - Navigate to **Security > Settings**, find **Security Level** and set **Security Level** to match what is configured in **SFCC Business Manager**. This setting applies to every Proxied DNS record in your Cloudflare zone.
-   2. *Option 2: Per Proxied DNS record* - If the **Security Level** differs between the Proxied DNS records targeting your SFCC environment and other Proxied DNS records in your Cloudflare zone, use a **Configuration Rule** to set the **Security Level** specifically for the Proxied DNS records targeting your SFCC environment. For example:
-      1. Create a new **Configuration Rule** by navigating to **Rules > Configuration Rules** and click **Create rule**:
+   1. _Option 1: Zone-level_ - Navigate to **Security > Settings**, find **Security Level** and set **Security Level** to match what is configured in **SFCC Business Manager**. This setting applies to every Proxied DNS record in your Cloudflare zone.
+   2. _Option 2: Per Proxied DNS record_ - If the **Security Level** differs between the Proxied DNS records targeting your SFCC environment and other Proxied DNS records in your Cloudflare zone, use a **Configuration Rule** to set the **Security Level** specifically for the Proxied DNS records targeting your SFCC environment. For example:
+      1. Create a new **Configuration Rule** by navigating to **Rules** > **Overview** and selecting **Create rule** next to **Configuration Rules**:
          1. **Rule name:** `Match Security Level on SFCC hostnames`
-         2. **Field:** *Hostname*
-         3. **Operator:** *is in* (this will match against multiple hostnames specified in the **Value** field)
+         2. **Field:** _Hostname_
+         3. **Operator:** _is in_ (this will match against multiple hostnames specified in the **Value** field)
          4. **Value:** `www.example.com` `dev.example.com`
          5. Scroll down to **Security Level** and click **+ Add**
-            1. **Select Security Level:** *Medium* (this should match the **Security Level** set in **SFCC Business Manager**)
+            1. **Select Security Level:** _Medium_ (this should match the **Security Level** set in **SFCC Business Manager**)
          6. Scroll to the bottom of the page and click **Deploy**
 3. Disable **Browser Integrity Check**
-   1. *Option 1: Zone-level* - Navigate to **Security > Settings**, find **Browser Integrity Check** and toggle it off to disable it. This setting applies to every Proxied DNS record in your Cloudflare zone.
-   2. *Option 2: Per Proxied DNS record* - If you want to keep **Browser Integrity Check** enabled for other Proxied DNS records in your Cloudflare zone but want to disable it on Proxied DNS records targeting your SFCC environment, keep the Zone-level **Browser Integrity Check** feature enabled and use a **Configuration Rule** to disable **Browser Integrity Check** specifically for the hostnames targeting your SFCC environment. For example:
-      1. Create a new **Configuration Rule** by navigating to **Rules > Configuration Rules** and click **Create rule**:
+   1. _Option 1: Zone-level_ - Navigate to **Security > Settings**, find **Browser Integrity Check** and toggle it off to disable it. This setting applies to every Proxied DNS record in your Cloudflare zone.
+   2. _Option 2: Per Proxied DNS record_ - If you want to keep **Browser Integrity Check** enabled for other Proxied DNS records in your Cloudflare zone but want to disable it on Proxied DNS records targeting your SFCC environment, keep the Zone-level **Browser Integrity Check** feature enabled and use a **Configuration Rule** to disable **Browser Integrity Check** specifically for the hostnames targeting your SFCC environment. For example:
+      1. Create a new **Configuration Rule** by navigating to **Rules** > **Overview** and selecting **Create rule** next to **Configuration Rules**:
          1. **Rule name:** `Disable Browser Integrity Check on SFCC hostnames`
-         2. **Field:** *Hostname*
-         3. **Operator:** *is in* (this will match against multiple hostnames specified in the **Value** field)
+         2. **Field:** _Hostname_
+         3. **Operator:** _is in_ (this will match against multiple hostnames specified in the **Value** field)
          4. **Value:** `www.example.com` `dev.example.com`
          5. Scroll down to **Browser Integrity Check** and click the **+ Add** button:
             1. Set the toggle to **Off** (a grey X will be displayed)
@@ -111,13 +115,13 @@ If you do have a `CAA` record, verify that it permits SSL certificates to be iss
    1. Your SFCC environment, also called a **Realm**, will contain one to many SFCC Proxy Zones, which is where caching will always occur. In the corresponding SFCC Proxy Zone for your domain, SFCC performs their own cache optimization, so it is recommended to bypass the cache on the Proxied DNS records in your Cloudflare zone which target your SFCC environment to prevent a "double caching" scenario. This can be accomplished with a **Cache Rule**.
    2. If the **Cache Rule** is not created, caching will occur in both your Cloudflare zone and your corresponding SFCC Proxy Zone, which can cause issues if and when the cache is invalidated or purged in your SFCC environment.
       1. Additional information on caching in your SFCC environment can be found in [SFCC's Content Cache Documentation](https://developer.salesforce.com/docs/commerce/b2c-commerce/guide/b2c-content-cache.html)
-   3. Create a new **Cache Rule** by navigating to **Rules > Cache Rules** and click **Create rule**:
+   3. Create a new **Cache Rule** by navigating to **Rules** > **Overview** and selecting **Create rule** next to **Cache Rules**:
       1. **Rule name:** `Bypass cache on SFCC hostnames`
-      2. **Field:** *Hostname*
-      3. **Operator:** *is in* (this will match against multiple hostnames specified in the **Value** field)
+      2. **Field:** _Hostname_
+      3. **Operator:** _is in_ (this will match against multiple hostnames specified in the **Value** field)
       4. **Value:** `www.example.com` `dev.example.com`
-      5. **Cache eligibility:** Select **Bypass cache**
-      6. Scroll to the bottom of the page and click **Deploy**
-5. *Optional* - Upload your Custom Certificate from **SFCC Business Manager** to your Cloudflare zone
+      5. **Cache eligibility:** Select **Bypass cache**.
+      6. Scroll to the bottom of the page and select **Deploy**.
+5. _Optional_ - Upload your Custom Certificate from **SFCC Business Manager** to your Cloudflare zone:
    1. The Custom Certificate you uploaded via **SFCC Business Manager** or **SFCC CDN-API**, which exists within your corresponding SFCC Proxy Zone, will terminate TLS connections for your SFCC storefront hostnames. Because of that, it is optional if you want to upload the same Custom Certificate to your own Cloudflare zone. Doing so will allow Cloudflare users with specific roles in your Cloudflare account to receive expiration notifications for your Custom Certificates. Please read [renew custom certificates](/ssl/edge-certificates/custom-certificates/renewing/#renew-custom-certificates) for further details.
    2. Additionally, since you now have your own Cloudflare zone, you have access to Cloudflare's various edge certificate products which means you could have more than one certificate covering the same SANs. In that scenario, a certificate priority process occurs to determine which certificate to serve at the Cloudflare edge. If you find your SFCC storefront hostnames are presenting a different certificate compared to what you uploaded via **SFCC Business Manager** or **SFCC CDN-API**, the certificate priority process is likely the reason. Please read [certificate priority](/ssl/reference/certificate-and-hostname-priority/#certificate-deployment) for further details.
diff --git a/src/content/docs/rules/cloud-connector/examples/route-images-to-s3.mdx b/src/content/docs/rules/cloud-connector/examples/route-images-to-s3.mdx
@@ -10,13 +10,13 @@ products:
 To route requests to `/images` on your domain to an AWS S3 bucket:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
-2. Navigate to **Rules > Cloud Connector**.
+2. Go to **Rules** > **Cloud Connector**.
 3. Select **Amazon Web Services - S3** as your [cloud provider](/rules/cloud-connector/providers/).
-4. Enter the bucket URL. You can structure this in two ways:
+4. Enter the bucket URL. You can structure the URL in two ways:
    - **Subdomain-style URL**: Set the hostname to `<BUCKET_NAME>.s3.amazonaws.com`. In this case, your files should be organized in the root of the bucket, meaning the URI path will map directly to the file. For example, `https://<YOUR_HOSTNAME>/images/file.jpg` will map to `https://<BUCKET_NAME>.s3.amazonaws.com/images/file.jpg`.
    - **URI path-style URL**: Set the hostname to `s3.amazonaws.com`. Here, your bucket must include a folder named `images`, and files should be placed inside this folder. The URI path will then include the bucket name, like `https://<YOUR_HOSTNAME>/<BUCKET_NAME>/images/file.jpg` mapping to `https://s3.amazonaws.com/<BUCKET_NAME>/images/file.jpg`.
 5. _(Optional)_ Use the [Rewrite URL](/rules/transform/url-rewrite/) feature of [Transform Rules](/rules/transform/) to adjust the URL structure. For example, you can [create a URL rewrite](/rules/transform/url-rewrite/create-dashboard/) that changes `/images` to `/<BUCKET_NAME>/images` to match the URI path-style URL structure.
-6. Click **Next** and enter a descriptive name like `Route images to S3` in **Cloud Connector name**.
+6. Select **Next** and enter a descriptive name like `Route images to S3` in **Cloud Connector name**.
 7. Under **If**, select **Custom filter expression** and enter the following expression:<br />
    `http.request.full_uri wildcard "http*://<YOUR_HOSTNAME>/images/*"`<br />
    Replace `<YOUR_HOSTNAME>` with desired hostname.
diff --git a/src/content/docs/rules/cloud-connector/examples/send-eu-visitors-to-gcs.mdx b/src/content/docs/rules/cloud-connector/examples/send-eu-visitors-to-gcs.mdx
@@ -10,13 +10,13 @@ products:
 To route requests from visitors in the European Union to a Google Cloud Storage bucket:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
-2. Go to **Rules > Cloud Connector**.
+2. Go to **Rules** > **Cloud Connector**.
 3. Select **Google Cloud Platform - Cloud Storage** as your [cloud provider](/rules/cloud-connector/providers/).
-4. Enter the bucket URL. You can structure this in two ways:
+4. Enter the bucket URL. You can structure the URL in two ways:
    - **Subdomain-style URL**: For `<BUCKET_NAME>.storage.googleapis.com`, your files should be organized in the root of the bucket. For example, `https://<YOUR_HOSTNAME>/index.html` will map to `https://<BUCKET_NAME>.storage.googleapis.com/index.html`.
    - **URI path-style URL**: If you set the hostname to `storage.googleapis.com`, your bucket must include folders corresponding to the intended URI paths. For example, if you want `https://<YOUR_HOSTNAME>/eu/index.html` to map to a file in your bucket, the file should be placed at `https://storage.googleapis.com/<BUCKET_NAME>/eu/index.html`.
 5. _(Optional)_ Use the [Rewrite URL](/rules/transform/url-rewrite/) feature of [Transform Rules](/rules/transform/) to adjust the URL structure. For example, you can [create a URL rewrite](/rules/transform/url-rewrite/create-dashboard/) that changes `/eu` to `/<BUCKET_NAME>` to match the URI path-style URL structure.
-6. Click **Next** and enter a descriptive name like "Route EU visitors to GCP" in Cloud Connector name.
+6. Select **Next** and enter a descriptive name like `Route EU visitors to GCP` in **Cloud Connector name**.
 7. Under **If**, select **Custom filter expression** and enter the following expression:
    `(ip.src.is_in_european_union)`<br />
    This expression targets traffic from European Union users.
diff --git a/src/content/docs/rules/cloud-connector/examples/serve-static-assets-from-azure.mdx b/src/content/docs/rules/cloud-connector/examples/serve-static-assets-from-azure.mdx
@@ -10,9 +10,9 @@ products:
 To serve static assets from an Azure Blob Storage container:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
-2. Navigate to **Rules > Cloud Connector**.
+2. Navigate to **Rules** > **Cloud Connector**.
 3. Select **Microsoft Azure - Blob Storage** as your [cloud provider](/rules/cloud-connector/providers/).
-4. Enter the bucket URL. Here’s how to structure it:
+4. Enter the bucket URL. Use the following URL structure:
    - **Subdomain-style URL**: Set the hostname to `<BUCKET_NAME>.blob.core.windows.net`. In this case, your bucket should include a folder named `static-assets`, and files should be placed inside this folder. For example, `https://<YOUR_HOSTNAME>/static-assets/style.css` will map to `https://<BUCKET_NAME>.blob.core.windows.net/static-assets/style.css`.
 5. _(Optional)_ Use the [Rewrite URL](/rules/transform/url-rewrite/) feature of [Transform Rules](/rules/transform/) to adjust the URL structure. For example, you can [create a URL rewrite](/rules/transform/url-rewrite/create-dashboard/) that changes `/static-assets` to `/my-pages-project/static-assets` to match the file structure of your object storage bucket.
 6. Click **Next** and enter a descriptive name like `Serve static assets from Azure` in **Cloud Connector name**.
diff --git a/src/content/docs/rules/origin-rules/examples/change-uri-path-and-host-header.mdx b/src/content/docs/rules/origin-rules/examples/change-uri-path-and-host-header.mdx
