update URLs

Author: ranbel

public/__redirects

@@ -719,7 +719,7 @@
 ## zero-trust-web access / clientless-access
 /learning-paths/zero-trust-web-access/concepts/reverse-proxy-server/ https://www.cloudflare.com/learning/cdn/glossary/reverse-proxy/ 301
 /zero-trust-web-access/concepts/zero-trust/ https://www.cloudflare.com/learning/security/glossary/what-is-zero-trust/ 301
-/learning-paths/zero-trust-web-access/concepts/zero-trust-web-access/ /learning-paths/zero-trust-web-access/concepts/clientless-access/ 301
+/learning-paths/zero-trust-web-access/concepts/zero-trust-web-access/ /learning-paths/clientless-access/concepts/what-is-clientless-access/ 301
 
 ## dns-filtering / secure-internet-traffic
 /learning-paths/dns-filtering/ /learning-paths/secure-internet-traffic/ 301
@@ -746,7 +746,7 @@
 /learning-paths/secure-internet-traffic/ /learning-paths/secure-internet-traffic/concepts/ 301
 /learning-paths/secure-o365-email/ /learning-paths/secure-o365-email/concepts/ 301
 /learning-paths/workers/ /learning-paths/workers/concepts/ 301
-/learning-paths/zero-trust-web-access/ /learning-paths/zero-trust-web-access/concepts/ 301
+/learning-paths/clientless-access/ /learning-paths/clientless-access/concepts/ 301
 /learning-paths/application-security/default-traffic-security/security-level/ /learning-paths/application-security/default-traffic-security/browser-integrity/ 301
 
 # more redirects in the /dynamic/ section
@@ -1902,6 +1902,8 @@
 /learning-paths/dns-filtering/create-policy/* /learning-paths/secure-internet-traffic/build-dns-policies/:splat 301
 ## Secure your Internet Traffic
 /learning-paths/secure-internet-traffic/connect-devices/* /learning-paths/secure-internet-traffic/connect-devices-networks/:splat 301
+## Zero Trust Web Access --> Clientless Access
+/learning-paths/zero-trust-web-access/* /learning-paths/clientless-access/:splat 301
 
 # Cloudflare for SaaS
 /ssl/ssl-for-saas/common-tasks/* /cloudflare-for-platforms/cloudflare-for-saas/ 301

src/content/docs/cloudflare-one/implementation-guides/zero-trust-web-access.mdx renamed to src/content/docs/cloudflare-one/implementation-guides/clientless-access.mdx

@@ -1,7 +1,7 @@
 ---
 pcx_content_type: navigation
 title: Deploy clientless access
-external_link: /learning-paths/zero-trust-web-access/concepts/
+external_link: /learning-paths/clientless-access/concepts/
 sidebar:
   order: 3
 ---

src/content/docs/cloudflare-one/implementation-guides/index.mdx

@@ -32,7 +32,7 @@ Implementation guides cover deployment steps and best practices for specific Clo
 
 <LinkTitleCard
 	title="Deploy clientless access"
-	href="/learning-paths/zero-trust-web-access/concepts/"
+	href="/learning-paths/clientless-access/concepts/"
 	icon="laptop"
 >
 	Secure access to internal web applications without a device client.

src/content/docs/learning-paths/zero-trust-web-access/access-application/best-practices.mdx renamed to src/content/docs/learning-paths/clientless-access/access-application/best-practices.mdx

@@ -22,4 +22,4 @@ Access applications have an inherently flexible and powerful domain structure ca
 
 Many customers who have workflows designed around internal web applications, especially those that were built internally, often see challenges related to interdependencies on multiple internal services. Separately, there can be challenges related to SPAs (Single-Page Applications) that make deploying clientless access difficult. For example, an application may have iFrames or other embedded systems that rely on different internal and/or external addresses.
 
-If your internal service operates in this way, we recommend specifying multiple top-level domains in a single Access application. Otherwise, if the goal of using multiple domains is to streamline or simplify policy creation, we recommend making one primary domain per application, and automating the rest of your deployment [using Terraform](/learning-paths/zero-trust-web-access/terraform/) or another Infrastructure as Code (IaC) service.
+If your internal service operates in this way, we recommend specifying multiple top-level domains in a single Access application. Otherwise, if the goal of using multiple domains is to streamline or simplify policy creation, we recommend making one primary domain per application, and automating the rest of your deployment [using Terraform](/learning-paths/clientless-access/terraform/) or another Infrastructure as Code (IaC) service.

src/content/docs/learning-paths/zero-trust-web-access/access-application/create-access-app.mdx renamed to src/content/docs/learning-paths/clientless-access/access-application/create-access-app.mdx

@@ -6,7 +6,7 @@ sidebar:
 
 ---
 
-Now that you have [connected your private applications](/learning-paths/zero-trust-web-access/connect-private-applications/) to Cloudflare, secure those applications behind Cloudflare Access.
+Now that you have [connected your private applications](/learning-paths/clientless-access/connect-private-applications/) to Cloudflare, secure those applications behind Cloudflare Access.
 
 ## Objectives
 

src/content/docs/learning-paths/zero-trust-web-access/access-application/index.mdx renamed to src/content/docs/learning-paths/clientless-access/access-application/index.mdx

@@ -230,7 +230,7 @@ Requires Data Loss Prevention add-on.
 
 Block users on unmanaged devices from downloading files that contain credit card numbers. This logic requires two policies:
 
-- **Policy 1: [Disable file downloads in isolated browser](/learning-paths/zero-trust-web-access/advanced-workflows/isolate-application/#disable-file-downloads-in-isolated-browser)**
+- **Policy 1: [Disable file downloads in isolated browser](/learning-paths/clientless-access/advanced-workflows/isolate-application/#disable-file-downloads-in-isolated-browser)**
 
 - **Policy 2: Block credit card numbers**
 

src/content/docs/learning-paths/zero-trust-web-access/advanced-workflows/external-evaluation.mdx renamed to src/content/docs/learning-paths/clientless-access/advanced-workflows/external-evaluation.mdx

@@ -25,4 +25,4 @@ To configure Clientless Web Isolation to augment clientless access, refer to [th
 
 * For guidance on building Gateway policies for private network applications, refer to [Secure your first application](/learning-paths/replace-vpn/build-policies/create-policy/).
 * If you already deployed the WARP client to some devices as part of a mixed-access methodology, ensure that your Gateway firewall policies do not rely on device posture checks. Because Clientless Web Isolation is not a machine in your fleet, it will not return any values for device posture checks.
-* You can standardize the user experience by making specific applications available in your App Launcher as [bookmarks](/learning-paths/zero-trust-web-access/customize-ux/bookmarks/). In this case, you would create a new bookmark for `https://<team-name>.cloudflareaccess.com/browser/https://internalresource.com`, which would take users directly to an isolated session with your application.
+* You can standardize the user experience by making specific applications available in your App Launcher as [bookmarks](/learning-paths/clientless-access/customize-ux/bookmarks/). In this case, you would create a new bookmark for `https://<team-name>.cloudflareaccess.com/browser/https://internalresource.com`, which would take users directly to an isolated session with your application.