Merge branch 'jts/revert-docs' into 'master'

Resets our docs on speedy deployments

See merge request !441

runbooks/how_to_speed_auto_deploy_process_for_urgent_merge_requests.md

@@ -8,13 +8,10 @@ speed up the auto-deploy process:
 
 1. Cherry-pick the merge request into the latest auto-deploy branch by
    adding `~Pick into auto-deploy` and the `severity::2` or higher labels.
-1. Trigger the [`auto_deploy:pick`] [pipeline schedule](https://ops.gitlab.net/gitlab-org/release/tools/-/pipeline_schedules).
-1. Enable the `auto_deploy_tag_latest` feature flag.
-1. Trigger the [`auto_deploy:prepare`] [pipeline schedule](https://ops.gitlab.net/gitlab-org/release/tools/-/pipeline_schedules).  This will create the new
-   auto-deploy branch.
-1. Trigger the [`auto_deploy:tag`] [pipeline schedule](https://ops.gitlab.net/gitlab-org/release/tools/-/pipeline_schedules). This will create
-   a coordinated pipeline with the merge request that needs to be deployed using
-   the new branch created in the prior step.
+1. Trigger the [`auto_deploy:pick`] [pipeline schedule].
+1. Enable the [`auto_deploy_tag_latest`] feature flag.
+1. Trigger the [`auto_deploy:tag`] [pipeline schedule]. This will create
+   a coordinated pipeline with the merge request that needs to be deployed.
 
 Once the merge request in the auto-deploy branch has a green pipeline, disable the
 [`auto_deploy_tag_latest`] feature flag, disabling the flag before could lead to
@@ -23,3 +20,4 @@ tagging an auto-deploy package using an earlier commit than the required merge r
 [`auto_deploy:pick`]: https://ops.gitlab.net/gitlab-org/release/tools/-/pipeline_schedules/72/edit
 [`auto_deploy:tag`]: https://ops.gitlab.net/gitlab-org/release/tools/-/pipeline_schedules/74/edit
 [`auto_deploy_tag_latest`]: https://ops.gitlab.net/gitlab-org/release/tools/-/feature_flags/191/edit
+[pipeline schedule]: https://ops.gitlab.net/gitlab-org/release/tools/-/pipeline_schedules