diff --git a/doc/ci/environments/deployment_safety.md b/doc/ci/environments/deployment_safety.md
index de6d668f4c3d34ea7334420e2375ce26dd8e3710..a46685810853d31066dac6462e1516a330e06efa 100644
--- a/doc/ci/environments/deployment_safety.md
+++ b/doc/ci/environments/deployment_safety.md
@@ -90,7 +90,7 @@ When an older deployment job starts, it fails and is labeled:
 - `The deployment job is older than the latest deployment, and therefore failed.`
   when viewing the completed job.
 
-When an older deployment job is manual, the play button is disabled with a message
+When an older deployment job is manual, the **Run** (**{play}**) button is disabled with a message
 `This deployment job does not run automatically and must be started manually, but it's older than the latest deployment, and therefore can't run.`.
 
 Job age is determined by the job start time, not the commit time, so a newer commit
diff --git a/doc/ci/environments/img/incremental_rollouts_play_v12_7.png b/doc/ci/environments/img/incremental_rollouts_play_v12_7.png
deleted file mode 100644
index 9d3ca258b08909f1b4aa5c12a81a4eb91176b651..0000000000000000000000000000000000000000
Binary files a/doc/ci/environments/img/incremental_rollouts_play_v12_7.png and /dev/null differ
diff --git a/doc/ci/environments/incremental_rollouts.md b/doc/ci/environments/incremental_rollouts.md
index 09cd88630193c6a7c570c49fe2e6c6310b04b9d8..b0199a1c569eb3aaaa51faca33be864a2fd4f909 100644
--- a/doc/ci/environments/incremental_rollouts.md
+++ b/doc/ci/environments/incremental_rollouts.md
@@ -66,12 +66,9 @@ rollout 10%:
     ROLLOUT_PERCENTAGE: 10
 ```
 
-When the jobs are built, a **play** button appears next to the job's name. Select **play**
+After the jobs are built, select **Run** (**{play}**) next to the job's name
 to release each stage of pods. You can also rollback by running a lower percentage job. Once 100%
-is reached, you cannot roll back using this method. It is still possible to roll back by redeploying
-the old version using the **Rollback** button on the environment page.
-
-![Play button](img/incremental_rollouts_play_v12_7.png)
+is reached, you cannot roll back using this method. To roll back a deployment, see [retry or roll back a deployment](../../ci/environments/index.md#retry-or-roll-back-a-deployment).
 
 A [deployable application](https://gitlab.com/gl-release/incremental-rollout-example) is
 available, demonstrating manually triggered incremental rollouts.
diff --git a/doc/ci/environments/index.md b/doc/ci/environments/index.md
index 88e20a4e15be1b58f2135c930050f6379bc82052..414ceacd735068f4384140bc4e847a171ecbac7d 100644
--- a/doc/ci/environments/index.md
+++ b/doc/ci/environments/index.md
@@ -304,10 +304,10 @@ deploy_prod:
 
 The `when: manual` action:
 
-- Exposes a play button for the job in the GitLab UI, with the text **Can be manually deployed to <environment>**.
-- Means the `deploy_prod` job is only triggered when the play button is selected.
+- Exposes the **Run** (**{play}**) button for the job in the GitLab UI, with the text **Can be manually deployed to <environment>**.
+- Means the `deploy_prod` job must be triggered manually.
 
-You can find the play button in the pipelines, environments, deployments, and jobs views.
+You can find **Run** (**{play}**) in the pipelines, environments, deployments, and jobs views.
 
 ## Track newly included merge requests per deployment
 
diff --git a/doc/ci/examples/laravel_with_gitlab_and_envoy/index.md b/doc/ci/examples/laravel_with_gitlab_and_envoy/index.md
index b7e345b544f6029adeba373e59a58b61e636a2b1..53787b5b772b37183ceae6054b808b6a57874d2c 100644
--- a/doc/ci/examples/laravel_with_gitlab_and_envoy/index.md
+++ b/doc/ci/examples/laravel_with_gitlab_and_envoy/index.md
@@ -632,7 +632,7 @@ Select it to see the runner's output.
 
 ![pipeline page](img/pipeline_page.png)
 
-After our code passed through the pipeline successfully, we can deploy to our production server by selecting the **play** button on the right side.
+After our code passed through the pipeline successfully, we can deploy to our production server by selecting **Run** (**{play}**) on the right side.
 
 ![pipelines page deploy button](img/pipelines_page_deploy_button.png)
 
diff --git a/doc/ci/jobs/index.md b/doc/ci/jobs/index.md
index c9058c1c9439680187b49e88399152e198fc4c39..210d9eb99833b979e8dd2d2c002f29f69cb0dc80 100644
--- a/doc/ci/jobs/index.md
+++ b/doc/ci/jobs/index.md
@@ -264,7 +264,7 @@ When running manual jobs you can supply additional job specific variables.
 
 You can do this from the job page of the manual job you want to run with
 additional variables. To access this page, select the **name** of the manual job in
-the pipeline view, *not* the play (**{play}**) button.
+the pipeline view, *not* **Run** (**{play}**).
 
 Define CI/CD variables here when you want to alter the execution of a job that uses
 [CI/CD variables](../variables/index.md).
diff --git a/doc/ci/jobs/job_control.md b/doc/ci/jobs/job_control.md
index 4305d84ce249b3f262ecef8f2be254beff5041d2..1e4dd4b47f3b296ac9d96f944ca268331d138db4 100644
--- a/doc/ci/jobs/job_control.md
+++ b/doc/ci/jobs/job_control.md
@@ -63,7 +63,7 @@ To run a manual job, you must have permission to merge to the assigned branch:
 
 1. Go to the pipeline, job, [environment](../environments/index.md#configure-manual-deployments),
    or deployment view.
-1. Next to the manual job, select **Play** (**{play}**).
+1. Next to the manual job, select **Run** (**{play}**).
 
 You can also [add custom CI/CD variables when running a manual job](index.md#specifying-variables-when-running-manual-jobs).
 
@@ -143,7 +143,7 @@ timed rollout 10%:
 To stop the active timer of a delayed job, select **Unschedule** (**{time-out}**).
 This job can no longer be scheduled to run automatically. You can, however, execute the job manually.
 
-To start a delayed job manually, select **Unschedule** (**{time-out}**) to stop the delay timer and then select **Play** (**{play}**).
+To start a delayed job manually, select **Unschedule** (**{time-out}**) to stop the delay timer and then select **Run** (**{play}**).
 Soon GitLab Runner starts the job.
 
 ## Parallelize large jobs
diff --git a/doc/ci/pipelines/index.md b/doc/ci/pipelines/index.md
index 61bf11c46c572e9ab91a75993dfd4e3573390fd7..45f361a7d1afdd3bd32a206b0f46db6ccd955da7 100644
--- a/doc/ci/pipelines/index.md
+++ b/doc/ci/pipelines/index.md
@@ -200,8 +200,7 @@ For each `var` or `file_var`, a key and value are required.
 [Manual jobs](../jobs/job_control.md#create-a-job-that-must-be-run-manually),
 allow you to require manual interaction before moving forward in the pipeline.
 
-You can do this straight from the pipeline graph. Just select the play button
-to execute that particular job.
+You can do this straight from the pipeline graph. Select **Run** (**{play}**) to execute that particular job.
 
 For example, your pipeline can start automatically, but require a manual action to
 [deploy to production](../environments/index.md#configure-manual-deployments).
@@ -212,7 +211,7 @@ In the example below, the `production` stage has a job with a manual action:
 #### Start all manual jobs in a stage
 
 If a stage contains only manual jobs, you can start all the jobs at the same time
-by selecting **Play all manual** (**{play}**) above the stage. If the stage contains
+by selecting **Run all manual** (**{play}**) above the stage. If the stage contains
 non-manual jobs, the option is not displayed.
 
 ### Skip a pipeline
diff --git a/doc/ci/pipelines/schedules.md b/doc/ci/pipelines/schedules.md
index 931cfec7e167187377386156c68b034631285b6d..d4116754dcd4c375f9c8c4c0573b189cd3452095 100644
--- a/doc/ci/pipelines/schedules.md
+++ b/doc/ci/pipelines/schedules.md
@@ -62,7 +62,7 @@ the next scheduled time:
 1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Build > Pipeline schedules**.
 1. On the right of the list, for
-   the pipeline you want to run, select **Play** (**{play}**).
+   the pipeline you want to run, select **Run** (**{play}**).
 
 You can manually run scheduled pipelines once per minute.