Robert Speicher
--- a/runbooks/how-to-recover-from-canceled-pipeline.md

+ 3

− 1
+++ b/runbooks/how-to-recover-from-canceled-pipeline.md

+ 3

− 1
 # How to recover from a canceled coordinated pipeline?
+> NOTE: This should be resolved as of January 2022: <https://gitlab.com/gitlab-org/gitlab/-/issues/341561>
 With the current GitLab stable version - 14.3 at the moment of this guide - there's no
 straightforward way to restart a canceled coordinated pipeline. Canceling a multi-project pipeline,
 such as the coordinated pipeline, causes the [bridge jobs not to be initiated], recovering from this
 @@ -11,7 +13,7 @@ situation is complicated and time consuming. Because of this, **it's strongly ad
 @@ -11,7 +13,7 @@ situation is complicated and time consuming. Because of this, **it's strongly ad
 In the strange case the Release Manager requires to recover the coordinated pipeline, there are
 some steps they can follow depending on the scenario.
-### Continue with the deployments of the canceled pipelnie
+### Continue with the deployments of the canceled pipeline
 Bridge jobs, or deployment jobs, of a canceled coordinated pipeline are mark as `skipped`. 
 To initiate them Release Managers need to retry the previous job: