diff --git a/src/content/docs/learning-paths/zero-trust-web-access/alternative-onramps/clientless-rbi.mdx b/src/content/docs/learning-paths/zero-trust-web-access/alternative-onramps/clientless-rbi.mdx
index e54ecded3c8ee5a..5f5ecf996602547 100644
--- a/src/content/docs/learning-paths/zero-trust-web-access/alternative-onramps/clientless-rbi.mdx
+++ b/src/content/docs/learning-paths/zero-trust-web-access/alternative-onramps/clientless-rbi.mdx
@@ -8,7 +8,7 @@ sidebar:
 
 :::note
 
-Requires the Browser Isolation add-on. 
+Requires the Browser Isolation add-on.
 :::
 
 [Clientless Web Isolation](/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation/) allows you to on-ramp user traffic to your private network without needing to install the WARP client. Users access private applications by going to a prefixed URL:
diff --git a/src/content/docs/learning-paths/zero-trust-web-access/initial-setup/add-site.mdx b/src/content/docs/learning-paths/zero-trust-web-access/initial-setup/add-site.mdx
index 710c89ee1917661..27f09e4c93aa16e 100644
--- a/src/content/docs/learning-paths/zero-trust-web-access/initial-setup/add-site.mdx
+++ b/src/content/docs/learning-paths/zero-trust-web-access/initial-setup/add-site.mdx
@@ -24,7 +24,7 @@ You only need to add one domain to Cloudflare, since you can create an infinite
 
   If Cloudflare is unable to identify your domain as a registered domain, make sure you are using an existing [top-level domain](https://www.cloudflare.com/learning/dns/top-level-domain/) (`.com`, `.net`, `.biz`, or others).
 
-  Additionally, Cloudflare requires your `apex domain` to be one level below a valid TLD defined in the [Public Suffix List (PSL)](https://github.com/publicsuffix/list/blob/master/public_suffix_list.dat). 
+  Additionally, Cloudflare requires your `apex domain` to be one level below a valid TLD defined in the [Public Suffix List (PSL)](https://github.com/publicsuffix/list/blob/master/public_suffix_list.dat).
   :::
 
 5. Review your DNS records and select **Continue**.
diff --git a/src/content/docs/learning-paths/zero-trust-web-access/migrate-applications/index.mdx b/src/content/docs/learning-paths/zero-trust-web-access/migrate-applications/index.mdx
index edb3188df17ae3c..d9647efd66e9e47 100644
--- a/src/content/docs/learning-paths/zero-trust-web-access/migrate-applications/index.mdx
+++ b/src/content/docs/learning-paths/zero-trust-web-access/migrate-applications/index.mdx
@@ -10,7 +10,7 @@ Publish internal applications that users currently access from a traditional cor
 
 :::note
 
-The remaining modules (Modules 6-9) discuss special considerations and setup options for enterprise environments. If you are only looking to configure a basic ZTWA setup, feel free to skip them. 
+The remaining modules (Modules 6-9) discuss special considerations and setup options for enterprise environments. If you are only looking to configure a basic ZTWA setup, feel free to skip them.
 :::
 
 ## Objectives
diff --git a/src/content/docs/learning-paths/zero-trust-web-access/terraform/publish-apps-with-terraform.mdx b/src/content/docs/learning-paths/zero-trust-web-access/terraform/publish-apps-with-terraform.mdx
index 04c8ca6f232acaa..74296f42f08e09a 100644
--- a/src/content/docs/learning-paths/zero-trust-web-access/terraform/publish-apps-with-terraform.mdx
+++ b/src/content/docs/learning-paths/zero-trust-web-access/terraform/publish-apps-with-terraform.mdx
@@ -30,7 +30,7 @@ Create a `.tf` file and copy-paste the following example. Fill in your API token
 
 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Networks** > **Tunnels**.
 2. Select the tunnel name.
-3. Copy the **Tunnel ID**. 
+3. Copy the **Tunnel ID**.
 
 </Details>
 
@@ -67,7 +67,7 @@ variable "tunnel_id" {
 
 :::caution
 
-To prevent accidentally exposing your Cloudflare credentials, do not save this file in your version control system. Learn more about [tracking a Terraform configuration](/terraform/tutorial/track-history/). 
+To prevent accidentally exposing your Cloudflare credentials, do not save this file in your version control system. Learn more about [tracking a Terraform configuration](/terraform/tutorial/track-history/).
 :::
 
 ## 3. Configure Cloudflare resources
@@ -106,7 +106,7 @@ resource "cloudflare_tunnel_config" "example_config" {
 
 :::note
 
-Public hostname configurations must include a catch-all ingress rule at the bottom of the file. 
+Public hostname configurations must include a catch-all ingress rule at the bottom of the file.
 :::
 
 ### Create an Access application
@@ -152,5 +152,5 @@ Users can now access the private application by going to the public URL and auth
 
 :::note
 
-If you need to modify the Access application, Access policy or DNS record, you must make the changes via Terraform. Changes made via the dashboard will break Terraform’s state. To prevent this from happening, [set the dashboard to read-only](/cloudflare-one/api-terraform/#set-dashboard-to-read-only). 
+If you need to modify the Access application, Access policy or DNS record, you must make the changes via Terraform. Changes made via the dashboard will break Terraform's state. To prevent this from happening, [set the dashboard to read-only](/cloudflare-one/api-terraform/#set-dashboard-to-read-only).
 :::