Merge branch 'docs-multicluster-setup-issue' into 'master'

Add workaround for issue preventing multi-cluster setup from working

See merge request gitlab-org/gitlab!50757

doc/topics/autodevops/index.md

@@ -307,6 +307,11 @@ and verifying your application is deployed as a Review App in the Kubernetes
 cluster with the `review/*` environment scope. Similarly, you can check the
 other environments.
 
+[Cluster environment scope isn't respected](https://gitlab.com/gitlab-org/gitlab/-/issues/20351)
+when checking for active Kubernetes clusters. For multi-cluster setup to work with Auto DevOps,
+create a fallback cluster with **Cluster environment scope** set to `*`. A new cluster isn't
+required. You can use any of the clusters already added.
+
 ## Limitations
 
 The following restrictions apply.
@@ -481,7 +486,7 @@ that works for this problem. Follow these steps to use the tool in Auto DevOps:
 
 ### Error: error initializing: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached
 
-As [announced in the official CNCF blogpost](https://www.cncf.io/blog/2020/10/07/important-reminder-for-all-helm-users-stable-incubator-repos-are-deprecated-and-all-images-are-changing-location/),
+As [announced in the official CNCF blog post](https://www.cncf.io/blog/2020/10/07/important-reminder-for-all-helm-users-stable-incubator-repos-are-deprecated-and-all-images-are-changing-location/),
 the stable Helm chart repository was deprecated and removed on November 13th, 2020.
 You may encounter this error after that date.
 
@@ -526,7 +531,7 @@ To fix your custom chart:
    it's used to verify the integrity of the downloaded dependencies.
 
 You can find more information in
-[issue #263778, "Migrate PostgreSQL from stable Helm repo"](https://gitlab.com/gitlab-org/gitlab/-/issues/263778).
+[issue #263778, "Migrate PostgreSQL from stable Helm repository"](https://gitlab.com/gitlab-org/gitlab/-/issues/263778).
 
 ### Error: release .... failed: timed out waiting for the condition
 
@@ -545,7 +550,7 @@ page of the deployed application on port 5000. If your application isn't configu
 to serve anything at the root page, or is configured to run on a specific port
 *other* than 5000, this check fails.
 
-If it fails, you should see these failures within the events for the relevant
+If it fails, you should see these failures in the events for the relevant
 Kubernetes namespace. These events look like the following example:
 
 ```plaintext