Context switcher updates

Because the left nav is changing
and will have a button instead
of carat, and no magnifying glass.

Related to: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/127935

Author: Suzanne Selhorn

doc/administration/audit_event_streaming/index.md

@@ -46,7 +46,7 @@ Prerequisites:
 
 To add streaming destinations to a top-level group:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
+1. On the left sidebar, select **Search or go to** and find your group.
 1. Select **Secure > Audit events**.
 1. On the main area, select **Streams** tab.
 1. Select **Add streaming destination** and select **HTTP endpoint** to show the section for adding destinations.
@@ -66,7 +66,7 @@ Prerequisites:
 
 To list the streaming destinations for a top-level group:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
+1. On the left sidebar, select **Search or go to** and find your group.
 1. Select **Secure > Audit events**.
 1. On the main area, select **Streams** tab.
 1. Select the stream to expand it and see all the custom HTTP headers.
@@ -79,7 +79,7 @@ Prerequisites:
 
 To update a streaming destination's name:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
+1. On the left sidebar, select **Search or go to** and find your group.
 1. Select **Secure > Audit events**.
 1. On the main area, select **Streams** tab.
 1. Select the stream to expand.
@@ -88,7 +88,7 @@ To update a streaming destination's name:
 
 To update a streaming destination's custom HTTP headers:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
+1. On the left sidebar, select **Search or go to** and find your group.
 1. Select **Secure > Audit events**.
 1. On the main area, select **Streams** tab.
 1. Select the stream to expand.
@@ -111,7 +111,7 @@ Prerequisites:
 
 To delete a streaming destination:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
+1. On the left sidebar, select **Search or go to** and find your group.
 1. Select **Secure > Audit events**.
 1. On the main area, select the **Streams** tab.
 1. Select the stream to expand.
@@ -120,7 +120,7 @@ To delete a streaming destination:
 
 To delete only the custom HTTP headers for a streaming destination:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
+1. On the left sidebar, select **Search or go to** and find your group.
 1. Select **Secure > Audit events**.
 1. On the main area, select the **Streams** tab.
 1. Select the stream to expand.
@@ -145,7 +145,7 @@ Prerequisites:
 
 To list streaming destinations and see the verification tokens:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
+1. On the left sidebar, select **Search or go to** and find your group.
 1. Select **Secure > Audit events**.
 1. On the main area, select the **Streams**.
 1. Select the stream to expand.
@@ -162,7 +162,7 @@ A streaming destination that has an event type filter set has a **filtered** (**
 
 To update a streaming destination's event filters:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
+1. On the left sidebar, select **Search or go to** and find your group.
 1. Select **Secure > Audit events**.
 1. On the main area, select the **Streams** tab.
 1. Select the stream to expand.
@@ -203,7 +203,7 @@ Prerequisites:
 
 To add Google Cloud Logging streaming destinations to a top-level group:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
+1. On the left sidebar, select **Search or go to** and find your group.
 1. Select **Secure > Audit events**.
 1. On the main area, select **Streams** tab.
 1. Select **Add streaming destination** and select **Google Cloud Logging** to show the section for adding destinations.
@@ -218,7 +218,7 @@ Prerequisites:
 
 To list Google Cloud Logging streaming destinations for a top-level group:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
+1. On the left sidebar, select **Search or go to** and find your group.
 1. Select **Secure > Audit events**.
 1. On the main area, select **Streams** tab.
 1. Select the Google Cloud Logging stream to expand and see all the fields.
@@ -231,7 +231,7 @@ Prerequisites:
 
 To update Google Cloud Logging streaming destinations to a top-level group:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
+1. On the left sidebar, select **Search or go to** and find your group.
 1. Select **Secure > Audit events**.
 1. On the main area, select **Streams** tab.
 1. Select the Google Cloud Logging stream to expand.
@@ -246,7 +246,7 @@ Prerequisites:
 
 To delete Google Cloud Logging streaming destinations to a top-level group:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
+1. On the left sidebar, select **Search or go to** and find your group.
 1. Select **Secure > Audit events**.
 1. On the main area, select the **Streams** tab.
 1. Select the Google Cloud Logging stream to expand.

doc/administration/housekeeping.md

@@ -109,7 +109,7 @@ housekeeping tasks. The manual trigger can be useful when either:
 
 To trigger housekeeping tasks manually:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. On the left sidebar, select **Settings > General**.
 1. Expand **Advanced**.
 1. Select **Run housekeeping**.
@@ -136,7 +136,7 @@ reduce the likelihood of such race conditions.
 
 To trigger a manual prune of unreachable objects:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. On the left sidebar, select **Settings > General**.
 1. Expand **Advanced**.
 1. Select **Run housekeeping**.

doc/administration/pages/index.md

@@ -704,7 +704,7 @@ Prerequisite:
 
 To set the maximum size of each GitLab Pages site in a group, overriding the inherited setting:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
+1. On the left sidebar, select **Search or go to** and find your group.
 1. On the left sidebar, select **Settings > General**.
 1. Expand **Pages**.
 1. Enter a value under **Maximum size** in MB.
@@ -718,7 +718,7 @@ Prerequisite:
 
 To set the maximum size of GitLab Pages site in a project, overriding the inherited setting:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. On the left sidebar, select **Deploy > Pages**.
 1. In **Maximum size of pages**, enter the size in MB.
 1. Select **Save changes**.

doc/administration/settings/continuous_integration.md

@@ -77,7 +77,7 @@ runner settings:
 
 To view the rendered details:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project or group.
+1. On the left sidebar, select **Search or go to** and find your project or group.
 1. Select **Settings > CI/CD**.
 1. Expand **Runners**.
 

doc/administration/settings/project_integration_management.md

@@ -84,7 +84,7 @@ To view projects in your instance that [use custom settings](#use-custom-setting
 
 To manage group-level default settings for a project integration:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
+1. On the left sidebar, select **Search or go to** and find your group.
 1. Select **Settings > Integrations**.
 1. Select an integration.
 1. Complete the fields.
@@ -121,7 +121,7 @@ is proposed in [epic 2137](https://gitlab.com/groups/gitlab-org/-/epics/2137).
 
 To remove a group-level default setting:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
+1. On the left sidebar, select **Search or go to** and find your group.
 1. Select **Settings > Integrations**.
 1. Select an integration.
 1. Select **Reset** and confirm.
@@ -132,7 +132,7 @@ Resetting a group-level default setting removes integrations that use default se
 
 To use instance-level or group-level default settings for a project integration:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Settings > Integrations**.
 1. Select an integration.
 1. On the right, from the dropdown list, select **Use default settings**.
@@ -144,7 +144,7 @@ To use instance-level or group-level default settings for a project integration:
 
 To use custom settings for a project or group integration:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project or group.
+1. On the left sidebar, select **Search or go to** and find your project or group.
 1. Select **Settings > Integrations**.
 1. Select an integration.
 1. On the right, from the dropdown list, select **Use custom settings**.

doc/ci/caching/index.md

@@ -535,7 +535,7 @@ and should only be disabled in an environment where all users with Developer rol
 
 To use the same cache for all branches:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Settings > CI/CD**.
 1. Expand **General pipelines**.
 1. Clear the **Use separate caches for protected branches** checkbox.
@@ -630,7 +630,7 @@ The next time the pipeline runs, the cache is stored in a different location.
 
 You can clear the cache in the GitLab UI:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. On the left sidebar, select **Build > Pipelines**.
 1. In the upper-right corner, select **Clear runner caches**.
 

doc/ci/components/index.md

@@ -409,7 +409,7 @@ so other users can discover it.
 
 To mark a project as a catalog resource:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. On the left sidebar, select **Settings > General**.
 1. Expand **Visibility, project features, permissions**.
 1. Scroll down to **CI/CD Catalog resource** and select the toggle to mark the project as a catalog resource.

doc/ci/enable_or_disable_ci.md

@@ -30,7 +30,7 @@ When you disable GitLab CI/CD:
 
 To disable GitLab CI/CD in your project:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Settings > General**.
 1. Expand **Visibility, project features, permissions**.
 1. In the **Repository** section, turn off **CI/CD**.
@@ -40,7 +40,7 @@ To disable GitLab CI/CD in your project:
 
 To enable GitLab CI/CD in your project:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Settings > General**.
 1. Expand **Visibility, project features, permissions**.
 1. In the **Repository** section, turn on **CI/CD**.

doc/ci/environments/deployment_approvals.md

@@ -137,7 +137,7 @@ create a new approval rule for each entity allowed to deploy to the environment.
 
 To migrate with the UI:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Settings > CI/CD**.
 1. Expand **Protected environments**.
 1. From the **Environment** list, select your environment.
@@ -171,7 +171,7 @@ require `Administrator` to approve every deployment job in `Production`.
 By default, the user who triggers a deployment pipeline can't also approve the deployment job.
 To allow self-approval of a deployment job:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Settings > CI/CD**.
 1. Expand **Protected environments**.
 1. From the **Approval options**, select the **Allow pipeline triggerer to approve deployment** checkbox.
@@ -196,7 +196,7 @@ Prerequisites:
 
 To approve or reject a deployment to a protected environment using the UI:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Operate > Environments**.
 1. Select the environment's name.
 1. In the deployment's row, select **Approval options** (**{thumb-up}**).
@@ -233,7 +233,7 @@ granted.
 
 To view the approval details of a deployment:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Operate > Environments**.
 1. Select the environment's name.
 1. In the deployment's row, select **Approval options** (**{thumb-up}**).
@@ -249,7 +249,7 @@ The approval status details are shown:
 
 ### Using the UI
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Operate > Environments**.
 1. Select the environment being deployed to.
 1. Look for the `blocked` label.

doc/ci/environments/index.md

@@ -51,7 +51,7 @@ Deployments show up in this list only after a deployment job has created them.
 
 To search environments by name:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Operate > Environments**.
 1. In the search bar, enter your search term.
    - The length of your **search term should be 3 or more characters**.
@@ -93,7 +93,7 @@ Prerequisites:
 
 To create a static environment in the UI:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Operate > Environments**.
 1. Select **Create an environment**.
 1. Complete the fields.
@@ -345,7 +345,7 @@ If there is a problem with a deployment, you can retry it or roll it back.
 
 To retry or roll back a deployment:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Operate > Environments**.
 1. Select the environment.
 1. To the right of the deployment name:
@@ -560,7 +560,7 @@ you can view its expiration date and time.
 
 To view an environment's expiration date and time:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Operate > Environments**.
 1. Select the name of the environment.
 
@@ -573,7 +573,7 @@ you can override its expiration.
 
 To override an environment's expiration:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Operate > Environments**.
 1. Select the deployment name.
 1. in the upper-right corner, select the thumbtack (**{thumbtack}**).
@@ -600,7 +600,7 @@ Environments view, the stop and deploy jobs must be in the same
 
 To stop an environment in the GitLab UI:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Operate > Environments**.
 1. Next to the environment you want to stop, select **Stop**.
 1. On the confirmation dialog, select **Stop environment**.
@@ -664,7 +664,7 @@ Prerequisites:
 
 To delete an environment:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Operate > Environments**.
 1. Select the **Stopped** tab.
 1. Next to the environment you want to delete, select **Delete environment**.
@@ -767,7 +767,7 @@ Limitations of GitLab Auto Rollback:
 
 GitLab Auto Rollback is turned off by default. To turn it on:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Settings > CI/CD**.
 1. Expand **Automatic deployment rollbacks**.
 1. Select the checkbox for **Enable automatic rollbacks**.

doc/ci/environments/kubernetes_dashboard.md

@@ -38,7 +38,7 @@ Prerequisites:
 
 ### The environment already exists
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Operate > Environments**.
 1. Select the environment to be associated with the Kubernetes.
 1. Select **Edit**.
@@ -49,7 +49,7 @@ Prerequisites:
 
 ### The environment doesn't exist
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Operate > Environments**.
 1. Select **New environment**.
 1. Complete the **Name** field.
@@ -62,7 +62,7 @@ Prerequisites:
 
 To view a configured dashboard:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Operate > Environments**.
 1. Expand the environment associated with GitLab agent for Kubernetes.
 1. Expand **Kubernetes overview**.

doc/ci/environments/protected_environments.md

@@ -30,7 +30,7 @@ Prerequisites:
 
 To protect an environment:
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project.
+1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Settings > CI/CD**.
 1. Expand **Protected environments**.
 1. Select **Protect an environment**.
@@ -256,7 +256,7 @@ To protect a group-level environment, make sure your environments have the corre
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/325249) in GitLab 15.1.
 
-1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group.
+1. On the left sidebar, select **Search or go to** and find your group.
 1. Select **Settings > CI/CD**.
 1. Expand **Protected environments**.
 1. From the **Environment** list, select the [deployment tier of environments](index.md#deployment-tier-of-environments) you want to protect.