[CF1] Updating UI instructions in partial files (#26117)

* Updating UI instructions in partial files

* Catching missed UI instructions

Author: Oxyjun

src/content/partials/cloudflare-one/access/access-block-page.mdx

@@ -7,4 +7,4 @@ Under **Block page**, choose what end users will see when they are denied access
 
 * **Cloudflare default**: Reload the [login page](/cloudflare-one/reusable-components/custom-pages/access-login-page/) and display a block message below the Cloudflare Access logo. The default message is `That account does not have access`, or you can enter a custom message.
 * **Redirect URL**: Redirect to the specified website.
-* **Custom page template**: Display a [custom block page](/cloudflare-one/reusable-components/custom-pages/access-block-page/) hosted in Zero Trust.
+* **Custom page template**: Display a [custom block page](/cloudflare-one/reusable-components/custom-pages/access-block-page/) hosted in Cloudflare One.

src/content/partials/cloudflare-one/access/add-infrastructure-app.mdx

@@ -13,7 +13,7 @@ import {
 <Tabs syncKey="dashPlusAPI">
 <TabItem label="Dashboard">
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Access** > **Applications**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Applications**.
 2. Select **Add an application**.
 3. Select **Infrastructure**.
 4. Enter any name for the application.

src/content/partials/cloudflare-one/access/add-mtls-cert.mdx

@@ -3,7 +3,7 @@ params:
   - product
 ---
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Access** > **Service auth** > **Mutual TLS**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Service credentials** > **Mutual TLS**.
 
 2. Select **Add mTLS Certificate**.
 

src/content/partials/cloudflare-one/access/add-target.mdx

@@ -16,7 +16,7 @@ To create a new target:</p>) :
 
 <Tabs syncKey="dashPlusAPI">
 <TabItem label="Dashboard">
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Networks** > **Targets**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Targets**.
 2. Select **Add a target**.
 3. In **Target hostname**, enter a user-friendly name for the <GlossaryTooltip term="target">target</GlossaryTooltip>. We recommend using the server hostname, for example `production-server`. The target hostname does not need to be unique and can be reused for multiple targets. Hostnames are used to define the targets secured by an Access application; they are not used for DNS address resolution.
 	<Details header="Hostname format restrictions">

src/content/partials/cloudflare-one/access/app-launcher.mdx

@@ -18,25 +18,25 @@ By default, the App Launcher is disabled. To enable it, you must configure a pol
 
 To enable the App Launcher:
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **Authentication**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Access settings**.
 
-2. Under the **App Launcher** card, select **Manage**.
+2. Under the **Manage your App Launcher** card, select **Manage**.
 
-3. On the **Rules** tab, [build a rule](/cloudflare-one/access-controls/policies/) to define who can access your App Launcher portal. These rules do not impact permissions for the applications secured behind Access.
+3. On the **Policies** tab, [build a policy](/cloudflare-one/access-controls/policies/) to define who can access your App Launcher portal. These rules do not impact permissions for the applications secured behind Access.
 
 4. On the **Authentication** tab, choose the identity providers users can authenticate with.
 
 5. Select **Save**.
 
-The App Launcher is now available at `<your-team-name>.cloudflareaccess.com`. You can always edit your App Launcher rules by going to **Settings** > **Authentication**.
+The App Launcher is now available at `<your-team-name>.cloudflareaccess.com`. You can always edit your App Launcher rules by going to **Access controls** > **Access settings**.
 
 ## Add a tile to the App Launcher
 
-Tiles have a one-to-one relationship with each application you create in Access. The tile names displayed in the Access App Launcher portal correspond to the application names listed under **Access** > **Applications**. For example, if you create one application for general access to your Jira deployment and a separate application that restricts requests to a particular Jira path, a user authorized for both will see separate tiles for each. If you add multiple hostnames to a single application, the user will only see the domain selected in the application's **App Launcher** settings.
+Tiles have a one-to-one relationship with each application you create in Access. The tile names displayed in the Access App Launcher portal correspond to the application names listed under **Access controls** > **Applications**. For example, if you create one application for general access to your Jira deployment and a separate application that restricts requests to a particular Jira path, a user authorized for both will see separate tiles for each. If you add multiple hostnames to a single application, the user will only see the domain selected in the application's **App Launcher** settings.
 
 To show an Access application in the App Launcher:
 
-1.  In [Zero Trust](https://one.dash.cloudflare.com/), go to **Access** > **Applications**.
+1.  In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Access controls** > **Applications**.
 2.  Select an application and select **Configure**.
 3.  Go to **Experience settings**.
 4.  Select **Show application in App Launcher**. The App Launcher link will only appear for users who are allowed by your Access policies. Blocked users will not see the app in their App Launcher.
@@ -67,7 +67,7 @@ You can display your own branding, messages, and links to users when they open t
 
 To customize the App Launcher appearance:
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Settings** > **Custom Pages**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Reusable components** > **Custom Pages**.
 2. Find the **Customize App Launcher** setting and select **Customize**.
 3. Give the App Launcher the look and feel of your organization by adding:
    - Your organization's name

src/content/partials/cloudflare-one/access/block-page.mdx

@@ -31,7 +31,7 @@ Only available on Pay-as-you-go and Enterprise plans.
 
 To create a custom block page for Access:
 
-1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Settings** > **Custom Pages**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Reusable components** > **Custom Pages**.
 
 2. Find the **Access Custom Pages** setting and select **Manage**.
 

src/content/partials/cloudflare-one/access/bookmarks.mdx

@@ -3,11 +3,11 @@
 
 ---
 
-With Cloudflare Zero Trust, you can show applications on the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) even if those applications are not secured behind Access. This way, users can access all the applications they need to work, all in one place — regardless of whether those applications are protected by Access.
+With Cloudflare One, you can show applications on the [App Launcher](/cloudflare-one/access-controls/access-settings/app-launcher/) even if those applications are not secured behind Access. This way, users can access all the applications they need to work, all in one place — regardless of whether those applications are protected by Access.
 
 Links to applications not protected by Access can be added as bookmarks. To add a bookmark:
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Access** > **Applications**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Applications**.
 
 2. Select **Add an application** > **Bookmark**.
 

src/content/partials/cloudflare-one/access/create-service-token.mdx

@@ -7,7 +7,7 @@ import { Tabs, TabItem, Details, APIRequest } from '~/components';
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Access** > **Service Auth** > **Service Tokens**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Access controls** > **Service credentials** > **Service Tokens**.
 
 2. Select **Create Service Token**.
 

src/content/partials/cloudflare-one/access/enable-isolation.mdx

@@ -6,7 +6,7 @@ import { Render } from "~/components";
 
 <Render file="clientless-browser-isolation" product="cloudflare-one" />
 
-3. Go to **Access** > **Applications**.
+3. Go to **Access controls** > **Applications**.
 4. Choose a [self-hosted application](/cloudflare-one/access-controls/applications/http-apps/self-hosted-public-app/) and select **Configure**.
 5. Go to **Policies**.
 6. Choose an [Allow policy](/cloudflare-one/access-controls/policies/) and select **Configure**.

src/content/partials/cloudflare-one/access/enable-scim-on-dashboard.mdx

@@ -6,7 +6,7 @@ params:
 
 import { Markdown } from "~/components"
 
-1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **Authentication**.
+1. In [Cloudflare One](https://one.dash.cloudflare.com), go to **Integrations** > **Identity providers**.
 
 2. Find the {props.idp} integration and select **Edit**.
 
@@ -15,8 +15,8 @@ import { Markdown } from "~/components"
 4. (Optional) Configure the following settings:
 
 * **Enable user deprovisioning**: [Revoke a user's active session](/cloudflare-one/access-controls/access-settings/session-management/#per-user) when they are removed from the SCIM application in {props.idp}. This will invalidate all active Access sessions and prompt for reauthentication for any [WARP session policies](/cloudflare-one/team-and-resources/devices/warp/configure-warp/warp-sessions/).
-* **Remove user seat on deprovision**: [Remove a user's seat](/cloudflare-one/team-and-resources/users/seat-management/) from your Zero Trust account when they are removed from the SCIM application in {props.idp}.
-* **SCIM identity update behavior**: Choose what happens in Zero Trust when the user's identity updates in {props.idp}.
+* **Remove user seat on deprovision**: [Remove a user's seat](/cloudflare-one/team-and-resources/users/seat-management/) from your Cloudflare One account when they are removed from the SCIM application in {props.idp}.
+* **SCIM identity update behavior**: Choose what happens in Cloudflare One when the user's identity updates in {props.idp}.
 	- _Automatic identity updates_: Automatically update the [User Registry identity](/cloudflare-one/insights/logs/users/) when {props.idp} sends an updated identity or group membership through SCIM. This identity is used for Gateway policies and WARP [device profiles](/cloudflare-one/team-and-resources/devices/warp/configure-warp/device-profiles/); Access will read the user's updated identity when they reauthenticate.
 	- _Group membership change reauthentication_: [Revoke a user's active session](/cloudflare-one/access-controls/access-settings/session-management/#per-user) when their group membership changes in {props.idp}. This will invalidate all active Access sessions and prompt for reauthentication for any [WARP session policies](/cloudflare-one/team-and-resources/devices/warp/configure-warp/warp-sessions/). Access will read the user's updated group membership when they reauthenticate.
 	- _No action_: Update the user's identity the next time they reauthenticate to Access or WARP.