[CF1] IA revamp: update branding (cloudflare#26200)

* revert cloudflare one organization

* ZT--> CF1

Author: ranbel

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

@@ -1,13 +1,13 @@
 ---
-title: Cloudflare Zero Trust
+title: Cloudflare One
 
 pcx_content_type: overview
 sidebar:
   order: 1
 head:
   - tag: title
     content: Overview
-description: Learn how to secure self-hosted and SaaS applications with Cloudflare Zero Trust. Configure a unified dashboard for seamless access and security.
+description: Learn how to secure self-hosted and SaaS applications with Cloudflare One. Configure a unified dashboard for seamless access and security.
 ---
 
 import {
@@ -25,13 +25,13 @@ import {
 
 <Description>
 
-Secure your organization with Cloudflare Zero Trust — a cloud security model that replaces legacy perimeters with Cloudflare’s global network.
+Secure your organization with Cloudflare One — a cloud security platform that replaces legacy perimeters with Cloudflare's global network.
 
 </Description>
 
 <Plan type="all" />
 
-Cloudflare Zero Trust is part of Cloudflare One, our name for the Secure Access Service Edge (SASE) platform that protects enterprise applications, users, devices, and networks.
+Cloudflare One is a Secure Access Service Edge (SASE) platform that combines Zero Trust security and enterprise networking services.
 
 By progressively adopting Cloudflare One, organizations can move away from a patchwork of hardware appliances and point solutions, and instead consolidate security and networking through a unified control plane that includes products like [Cloudflare Access](/cloudflare-one/access-controls/policies/), [Secure Web Gateway (SWG)](/cloudflare-one/traffic-policies/), [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/), [Data Loss Prevention (DLP)](/cloudflare-one/data-loss-prevention/), [Remote Browser Isolation (RBI)](/cloudflare-one/remote-browser-isolation/), [Cloud Access Security Broker (CASB)](/cloudflare-one/integrations/cloud-and-saas/), and [Email security](/cloudflare-one/email-security/).
 
@@ -47,7 +47,7 @@ Refer to our [SASE reference architecture](/reference-architecture/architectures
 	Get started
 </LinkButton>
 <LinkButton variant="secondary" href="https://one.dash.cloudflare.com/">
-	Zero Trust dashboard
+	Cloudflare One dashboard
 </LinkButton>
 <LinkButton variant="primary" href="/cloudflare-one/implementation-guides/">
 	Implementation guides
@@ -63,7 +63,7 @@ Authenticate users accessing your applications, seamlessly onboard third-party u
 
 <RelatedProduct header="Cloudflare Tunnel" href="/cloudflare-one/networks/connectors/cloudflare-tunnel/" product="zero-trust-networks">
 
-Securely connect your resources to Cloudflare without exposing a public IP by using Cloudflare Tunnel, which establishes outbound-only connections from your infrastructure to Cloudflare’s global network via the lightweight `cloudflared` daemon.
+Securely connect your resources to Cloudflare without exposing a public IP by using Cloudflare Tunnel, which establishes outbound-only connections from your infrastructure to Cloudflare's global network via the lightweight `cloudflared` daemon.
 
 </RelatedProduct>
 

src/content/docs/cloudflare-one/insights/analytics-overview.mdx

@@ -11,7 +11,7 @@ To view the Analytics overview, log into [Cloudflare One](https://one.dash.cloud
 
 The Analytics overview includes reports and insights across the following products and categories:
 
-- [Global status](#global-status) of your Cloudflare One organization
+- [Global status](#global-status) of your Zero Trust Organization
 - [Access](#access)
 - Gateway
   - [HTTP traffic](#proxy-traffic)
@@ -30,7 +30,7 @@ In **Global status**, you can view a report on your organization's Cloudflare On
 - SaaS integrations
 - DLP profiles
 
-You can also view a report on your [seat usage](/cloudflare-one/team-and-resources/users/seat-management/) across your Cloudflare One organization that contains the following metrics:
+You can also view a report on your [seat usage](/cloudflare-one/team-and-resources/users/seat-management/) across your Zero Trust Organization that contains the following metrics:
 
 - Total seats
 - Used seats

src/content/docs/cloudflare-one/integrations/identity-providers/adfs.mdx

@@ -190,7 +190,7 @@ To enable Cloudflare One to accept the claims and assertions sent from AD FS, fo
 
    This is the default location. You can find your federation service identifier in AD FS.
 
-6. In the **IdP Entity ID or Issuer URL** field, enter your Cloudflare One team domain and include this callback at the end of the path: `/cdn-cgi/access/callback`. For example:
+6. In the **IdP Entity ID or Issuer URL** field, enter your Cloudflare Zero Trust team domain and include this callback at the end of the path: `/cdn-cgi/access/callback`. For example:
 
    ```txt
    https://<your-team-name>.cloudflareaccess.com/cdn-cgi/access/callback

src/content/docs/cloudflare-one/integrations/identity-providers/okta.mdx

@@ -12,7 +12,7 @@ Additionally, you can configure Okta to use risk information from Cloudflare One
 
 ## Prerequisites
 
-- A [Cloudflare One organization](/cloudflare-one/setup/) with any subscription tier (including Free)
+- A [Zero Trust Organization](/cloudflare-one/setup/) with any subscription tier (including Free)
 - A [Cloudflare One administrator role](/cloudflare-one/roles-permissions/) with `Access Edit` permissions
 
 ## Supported features
@@ -30,7 +30,7 @@ To set up the Okta integration using the Okta Integration Network (OIN) App Cata
 4. Search for `Cloudflare` and select the **Cloudflare One** app.
 5. Select **Add integration**.
 6. In **Application label**, enter a name for the application (for example, `Cloudflare Access`).
-7. In **Team domain**, enter your Cloudflare One team domain:
+7. In **Team domain**, enter your Cloudflare Zero Trust team domain:
 
    ```txt
    <your-team-name>.cloudflareaccess.com

src/content/docs/cloudflare-one/setup.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 import { Render } from "~/components";
 
-This guide covers the recommended steps to start securing your users and devices with Cloudflare One.
+This guide covers the recommended steps to start securing your users and devices with Cloudflare Zero Trust.
 
 :::note
 
@@ -18,26 +18,26 @@ To get started with a specific use case, refer to our [implementation guides](/c
 
 Sign up for a [Cloudflare account](https://dash.cloudflare.com/sign-up).
 
-## Create a Cloudflare One organization
+## Create a Zero Trust Organization
 
 <Render file="choose-team-name" product="cloudflare-one" />
 
-Welcome to Cloudflare One! You can now explore a list of one-click actions we have designed to help you kickstart your Cloudflare One experience.
+Welcome to Cloudflare Zero Trust! You can now explore a list of one-click actions we have designed to help you kickstart your experience.
 
 ## Install the WARP client on your devices
 
 If you want to enable security features such as Browser Isolation, HTTP filtering, AV scanning, and device posture, or connect networks to Cloudflare, here are the next steps you need to take:
 
-1. **Set up a login method.** Configure [One-time PIN](/cloudflare-one/integrations/identity-providers/one-time-pin/) or connect a [third-party identity provider](/cloudflare-one/integrations/identity-providers/) in Cloudflare One. This is the login method your users will utilize when authenticating to add a new device to your Cloudflare One setup.
+1. **Set up a login method.** Configure [One-time PIN](/cloudflare-one/integrations/identity-providers/one-time-pin/) or connect a [third-party identity provider](/cloudflare-one/integrations/identity-providers/) in Cloudflare Zero Trust. This is the login method your users will utilize when authenticating to add a new device to your Cloudflare Zero Trust setup.
 
-2. **Next, define [device enrollment permissions](/cloudflare-one/team-and-resources/devices/warp/deployment/device-enrollment/)**. Create device enrollment rules to define which users in your organization should be able to connect devices to your organization's Cloudflare One setup. As you create your rule, you will be asked to select which login method you would like users to authenticate with.
+2. **Next, define [device enrollment permissions](/cloudflare-one/team-and-resources/devices/warp/deployment/device-enrollment/)**. Create device enrollment rules to define which users in your organization should be able to connect devices to your organization's Cloudflare Zero Trust setup. As you create your rule, you will be asked to select which login method you would like users to authenticate with.
 
 3. **Install the [Cloudflare root certificate](/cloudflare-one/team-and-resources/devices/user-side-certificates/) on your devices.** Advanced security features including HTTP traffic inspection require users to install and trust the Cloudflare root certificate on their machine or device. If you are installing certificates manually on all your devices, these steps will need to be performed on each new device that is to be subject to HTTP filtering.
 
 4. **[Download](/cloudflare-one/team-and-resources/devices/warp/download-warp/) and deploy the WARP client to your devices**. Choose one of the [different ways](/cloudflare-one/team-and-resources/devices/warp/deployment/) to deploy the WARP client, depending on what works best for your organization.
 
-5. **Log in to your organization's Cloudflare One instance from your devices**. On your device, go to the Settings section in the WARP client and insert your organization's team name.
+5. **Log in to your organization's Cloudflare Zero Trust instance from your devices**. On your device, go to the Settings section in the WARP client and insert your organization's team name.
 
-Your devices are now connected to Cloudflare One through the WARP client. You can go to **Team & Resources** > **Devices** to find a list of your enrolled devices, when they were last seen, and the WARP client version they are running.
+Your devices are now connected to Cloudflare Zero Trust through the WARP client. You can go to **Team & Resources** > **Devices** to find a list of your enrolled devices, when they were last seen, and the WARP client version they are running.
 
 Next, [enforce security policies](/cloudflare-one/traffic-policies/) on your traffic and access requests.

src/content/docs/cloudflare-one/team-and-resources/devices/warp/deployment/mdm-deployment/protocol-handler.mdx

@@ -50,7 +50,7 @@ You can configure your browser to automatically launch the Cloudflare WARP appli
 
 ### Chromium-based browsers
 
-Chromium-based browsers such as Google Chrome and Microsoft Edge have a policy setting called [AutoLaunchProtocolsFromOrigins](https://learn.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#autolaunchprotocolsfromorigins). This setting takes in two parameters: a protocol for the browser to launch and the origins that are allowed to launch it. For the browser to launch WARP, you need to set the protocol to `com.cloudflare.warp` and the origin to your <GlossaryTooltip term="team domain">Zero Trust team domain</GlossaryTooltip> (`https://<your-team-name>.cloudflareaccess.com`).
+Chromium-based browsers such as Google Chrome and Microsoft Edge have a policy setting called [AutoLaunchProtocolsFromOrigins](https://learn.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#autolaunchprotocolsfromorigins). This setting takes in two parameters: a protocol for the browser to launch and the origins that are allowed to launch it. For the browser to launch WARP, you need to set the protocol to `com.cloudflare.warp` and the origin to your <GlossaryTooltip term="team domain">Cloudflare Zero Trust team domain</GlossaryTooltip> (`https://<your-team-name>.cloudflareaccess.com`).
 
 <Tabs>
 <TabItem label="Windows">

src/content/docs/cloudflare-one/team-and-resources/users/seat-management.mdx

@@ -29,7 +29,7 @@ To check the number of seats consumed by active users in your organization, log
 
 When you revoke a user, this action will terminate active sessions, but will not remove the user's consumption of an active seat.
 
-To revoke a user from your Cloudflare One organization:
+To revoke a user from your Zero Trust Organization:
 
 1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Users**.
 2. Select the checkbox next to a user with an **Active** status in the **Seat usage** column.
@@ -40,9 +40,9 @@ Revoked users can still log in if your policies allow them.
 
 ### Remove a user
 
-Removing a user from your Cloudflare One organization will free up the seat the user consumed. The user will still appear in your list of users.
+Removing a user from your Zero Trust Organization will free up the seat the user consumed. The user will still appear in your list of users.
 
-To remove a user from your Cloudflare One organization:
+To remove a user from your Zero Trust Organization:
 
 1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Team & Resources** > **Users**.
 2. Select the checkbox next to a user with an **Active** status in the **Seat usage** column.
@@ -54,7 +54,7 @@ The user will now show as **Inactive** and will no longer occupy a seat. If a us
 To automate the removal of users who have not logged in or triggered a device enrollment in a specific amount of time, turn on [seat expiration](#enable-seat-expiration).
 
 :::note[User record persistence]
-You cannot delete or archive a user record. You can [remove a user](#remove-a-user) from a seat, but their user record will remain in your Cloudflare One organization. Inactive users do not count towards billing.
+You cannot delete or archive a user record. You can [remove a user](#remove-a-user) from a seat, but their user record will remain in your Zero Trust Organization. Inactive users do not count towards billing.
 :::
 
 ### Enable seat expiration

src/content/glossary/cloudflare-one.yaml

@@ -47,7 +47,7 @@ entries:
 
   - term: Cloudflare DEX
     general_definition: |-
-      Cloudflare Digital Experience Monitoring (DEX) provides visibility into device, network, and application performance across your Cloudflare One organization.
+      Cloudflare Digital Experience Monitoring (DEX) provides visibility into device, network, and application performance across your Zero Trust Organization.
 
   - term: Cloudflare Gateway
     general_definition: |-
@@ -101,7 +101,7 @@ entries:
 
   - term: fleet
     general_definition: |-
-      a fleet is a collection of user devices. All devices in a fleet have WARP installed and are connected to a [Cloudflare One organization](/cloudflare-one/setup/#create-a-cloudflare-one-organization).
+      a fleet is a collection of user devices. All devices in a fleet have WARP installed and are connected to a [Zero Trust Organization](/cloudflare-one/setup/#create-a-zero-trust-organization).
 
   - term: identity provider
     general_definition: |-

src/content/partials/cloudflare-one/choose-team-name.mdx

@@ -1,6 +1,6 @@
 import { GlossaryTooltip, DashButton } from "~/components";
 
-1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), select **Cloudflare One**.
+1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), select **Zero Trust**.
 
    <DashButton url="https://one.dash.cloudflare.com" />
 

src/content/products/cloudflare-one.yaml

@@ -1,14 +1,13 @@
-name: Cloudflare Zero Trust
+name: Cloudflare One
 
 product:
-  title: Cloudflare Zero Trust
+  title: Cloudflare One
   url: /cloudflare-one/
   group: Cloudflare One
   wrap: true
   preview_tryout: true
 
 meta:
-  title: Cloudflare Zero Trust docs
+  title: Cloudflare One docs
   description: Replace legacy security perimeters with Cloudflare's network to protect your organization
   author: "@cloudflare"
-