Add latest changes from gitlab-org/gitlab@master

7 files changed, 350 insertions, 318 deletions

diff --git a/doc/topics/autodevops/customize.md b/doc/topics/autodevops/customize.md
index 28abd73ef97..d373c3212c3 100644
--- a/doc/topics/autodevops/customize.md
+++ b/doc/topics/autodevops/customize.md
@@ -1,25 +1,26 @@
 # Customizing Auto DevOps
 
-While Auto DevOps provides great defaults to get you started, you can customize
-almost everything to fit your needs; from custom [buildpacks](#custom-buildpacks),
-to [`Dockerfile`s](#custom-dockerfile), [Helm charts](#custom-helm-chart), or
-even copying the complete [CI/CD configuration](#customizing-gitlab-ciyml)
-into your project to enable staging and canary deployments, and more.
+While [Auto DevOps](index.md) provides great defaults to get you started, you can customize
+almost everything to fit your needs. Auto DevOps offers everything from custom
+[buildpacks](#custom-buildpacks), to [`Dockerfiles](#custom-dockerfile), and
+[Helm charts](#custom-helm-chart). You can even copy the complete
+[CI/CD configuration](#customizing-gitlab-ciyml) into your project to enable
+staging and canary deployments, and more.
 
 ## Custom buildpacks
 
 If the automatic buildpack detection fails for your project, or if you want to
-use a custom buildpack, you can override the buildpack(s) using a project variable
+use a custom buildpack, you can override the buildpack using a project variable
 or a `.buildpacks` file in your project:
 
 - **Project variable** - Create a project variable `BUILDPACK_URL` with the URL
   of the buildpack to use.
-- **`.buildpacks` file** - Add a file in your project's repo called  `.buildpacks`
+- **`.buildpacks` file** - Add a file in your project's repository called `.buildpacks`,
   and add the URL of the buildpack to use on a line in the file. If you want to
-  use multiple buildpacks, you can enter them in, one on each line.
+  use multiple buildpacks, enter one buildpack per line.
 
 The buildpack URL can point to either a Git repository URL or a tarball URL.
-For Git repositories, it is possible to point to a specific Git reference (for example,
+For Git repositories, you can point to a specific Git reference (such as
 commit SHA, tag name, or branch name) by appending `#<ref>` to the Git repository URL.
 For example:
 
@@ -29,11 +30,10 @@ For example:
 
 ### Multiple buildpacks
 
-Using multiple buildpacks isn't fully supported by Auto DevOps because, when using the `.buildpacks`
-file, Auto Test will not work.
-
-The buildpack [heroku-buildpack-multi](https://github.com/heroku/heroku-buildpack-multi/),
-which is used under the hood to parse the `.buildpacks` file, doesn't provide the necessary commands
+Using multiple buildpacks is not fully supported by Auto DevOps, because Auto Test
+won't work when using the `.buildpacks` file. The buildpack
+[heroku-buildpack-multi](https://github.com/heroku/heroku-buildpack-multi/), used
+in the backend to parse the `.buildpacks` file, does not provide the necessary commands
 `bin/test-compile` and `bin/test`.
 
 If your goal is to use only a single custom buildpack, you should provide the project variable
@@ -41,18 +41,16 @@ If your goal is to use only a single custom buildpack, you should provide the pr
 
 ## Custom `Dockerfile`
 
-If your project has a `Dockerfile` in the root of the project repo, Auto DevOps
-will build a Docker image based on the Dockerfile rather than using buildpacks.
+If your project has a `Dockerfile` in the root of the project repository, Auto DevOps
+builds a Docker image based on the Dockerfile, rather than using buildpacks.
 This can be much faster and result in smaller images, especially if your
 Dockerfile is based on [Alpine](https://hub.docker.com/_/alpine/).
 
 ## Passing arguments to `docker build`
 
 Arguments can be passed to the `docker build` command using the
-`AUTO_DEVOPS_BUILD_IMAGE_EXTRA_ARGS` project variable.
-
-For example, to build a Docker image based on based on the `ruby:alpine`
-instead of the default `ruby:latest`:
+`AUTO_DEVOPS_BUILD_IMAGE_EXTRA_ARGS` project variable. For example, to build a
+Docker image based on based on the `ruby:alpine` instead of the default `ruby:latest`:
 
 1. Set `AUTO_DEVOPS_BUILD_IMAGE_EXTRA_ARGS` to `--build-arg=RUBY_VERSION=alpine`.
 1. Add the following to a custom `Dockerfile`:
@@ -65,25 +63,28 @@ instead of the default `ruby:latest`:
    ```
 
 NOTE: **Note:**
-Passing in complex values (newlines and spaces, for example) will likely
-cause escaping issues due to the way this argument is used in Auto DevOps.
-Consider using Base64 encoding of such values to avoid this problem.
+Use Base64 encoding if you need to pass complex values, such as newlines and
+spaces. Left unencoded, complex values like these can cause escaping issues
+due to how Auto DevOps uses the arguments.
 
 CAUTION: **Warning:**
 Avoid passing secrets as Docker build arguments if possible, as they may be
 persisted in your image. See
-[this discussion](https://github.com/moby/moby/issues/13490) for details.
+[this discussion of best practices with secrets](https://github.com/moby/moby/issues/13490) for details.
 
 ## Passing secrets to `docker build`
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/25514) in GitLab 12.3, but available in versions 11.9 and above.
 
-CI environment variables can be passed as [build
-secrets](https://docs.docker.com/develop/develop-images/build_enhancements/#new-docker-build-secret-information) to the `docker build` command by listing them comma separated by name in the
-`AUTO_DEVOPS_BUILD_IMAGE_FORWARDED_CI_VARIABLES` variable. For example, in order to forward the variables `CI_COMMIT_SHA` and `CI_ENVIRONMENT_NAME`, one would set `AUTO_DEVOPS_BUILD_IMAGE_FORWARDED_CI_VARIABLES` to `CI_COMMIT_SHA,CI_ENVIRONMENT_NAME`.
+CI environment variables can be passed as
+[build secrets](https://docs.docker.com/develop/develop-images/build_enhancements/#new-docker-build-secret-information) to the `docker build` command by listing them
+by name, comma-separated, in the `AUTO_DEVOPS_BUILD_IMAGE_FORWARDED_CI_VARIABLES`
+variable. For example, to forward the variables `CI_COMMIT_SHA` and `CI_ENVIRONMENT_NAME`,
+set `AUTO_DEVOPS_BUILD_IMAGE_FORWARDED_CI_VARIABLES` to `CI_COMMIT_SHA,CI_ENVIRONMENT_NAME`.
 
-Unlike build arguments, these are not persisted by Docker in the final image
-(though you can still persist them yourself, so **be careful**).
+CAUTION: **Caution:**
+Unlike build arguments, these variables are not persisted by Docker in the final image,
+though you can still persist them yourself.
 
 In projects:
 
@@ -91,7 +92,7 @@ In projects:
   variables.
 - With a `Dockerfile`, the following is required:
 
-  1. Activate the experimental `Dockerfile` syntax by adding the following
+  1. Activate the experimental `Dockerfile` syntax by adding the following code
      to the top of the file:
 
      ```dockerfile
@@ -114,30 +115,33 @@ feature to use the `--secret` flag.
 
 Auto DevOps uses [Helm](https://helm.sh/) to deploy your application to Kubernetes.
 You can override the Helm chart used by bundling up a chart into your project
-repo or by specifying a project variable:
+repository or by specifying a project variable:
 
 - **Bundled chart** - If your project has a `./chart` directory with a `Chart.yaml`
-  file in it, Auto DevOps will detect the chart and use it instead of the [default
-  one](https://gitlab.com/gitlab-org/charts/auto-deploy-app).
-  This can be a great way to control exactly how your application is deployed.
+  file in it, Auto DevOps will detect the chart and use it instead of the
+  [default chart](https://gitlab.com/gitlab-org/charts/auto-deploy-app), enabling
+  you to control exactly how your application is deployed.
 - **Project variable** - Create a [project variable](../../ci/variables/README.md#gitlab-cicd-environment-variables)
-  `AUTO_DEVOPS_CHART` with the URL of a custom chart to use or create two project variables `AUTO_DEVOPS_CHART_REPOSITORY` with the URL of a custom chart repository and `AUTO_DEVOPS_CHART` with the path to the chart.
+  `AUTO_DEVOPS_CHART` with the URL of a custom chart to use, or create two project
+  variables: `AUTO_DEVOPS_CHART_REPOSITORY` with the URL of a custom chart repository,
+  and `AUTO_DEVOPS_CHART` with the path to the chart.
 
 ## Customize values for Helm Chart
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/30628) in GitLab 12.6, `.gitlab/auto-deploy-values.yaml` will be used by default for Helm upgrades.
 
-You can override the default values in the `values.yaml` file in the [default Helm chart](https://gitlab.com/gitlab-org/charts/auto-deploy-app).
-This can be achieved by either:
+You can override the default values in the `values.yaml` file in the
+[default Helm chart](https://gitlab.com/gitlab-org/charts/auto-deploy-app) by either:
 
-- Adding a file named `.gitlab/auto-deploy-values.yaml` to your repository. It will
-  be automatically used if found.
-- Adding a file with a different name or path to the repository, and set the
-  `HELM_UPGRADE_VALUES_FILE` [environment variable](#environment-variables) with the path and name.
+- Adding a file named `.gitlab/auto-deploy-values.yaml` to your repository, which is
+  automatically used, if found.
+- Adding a file with a different name or path to the repository, and setting the
+  `HELM_UPGRADE_VALUES_FILE` [environment variable](#environment-variables) with
+  the path and name.
 
 NOTE: **Note:**
-For GitLab 12.5 and earlier, the `HELM_UPGRADE_EXTRA_ARGS` environment variable can be used to override the default chart values.
-To do so, set `HELM_UPGRADE_EXTRA_ARGS` to `--values my-values.yaml`.
+For GitLab 12.5 and earlier, use the `HELM_UPGRADE_EXTRA_ARGS` environment variable
+to override the default chart values by setting `HELM_UPGRADE_EXTRA_ARGS` to `--values <my-values.yaml>`.
 
 ## Custom Helm chart per environment
 
@@ -146,34 +150,34 @@ to the desired environment. See [Limiting environment scopes of variables](../..
 
 ## Customizing `.gitlab-ci.yml`
 
-Auto DevOps is completely customizable because the [Auto DevOps template](https://gitlab.com/gitlab-org/gitlab/blob/master/lib/gitlab/ci/templates/Auto-DevOps.gitlab-ci.yml):
+Auto DevOps is completely customizable because the
+[Auto DevOps template](https://gitlab.com/gitlab-org/gitlab/blob/master/lib/gitlab/ci/templates/Auto-DevOps.gitlab-ci.yml)
+is just an implementation of a [`.gitlab-ci.yml`](../../ci/yaml/README.md) file,
+and uses only features available to any implementation of `.gitlab-ci.yml`.
 
-- Is just an implementation of a [`.gitlab-ci.yml`](../../ci/yaml/README.md) file.
-- Uses only features available to any implementation of `.gitlab-ci.yml`.
-
-If you want to modify the CI/CD pipeline used by Auto DevOps, you can [`include`
-the template](../../ci/yaml/README.md#includetemplate) and customize as
-needed. To do this, add a `.gitlab-ci.yml` file to the root of your repository
+To modify the CI/CD pipeline used by Auto DevOps,
+[`include` the template](../../ci/yaml/README.md#includetemplate), and customize
+it as needed by adding a `.gitlab-ci.yml` file to the root of your repository
 containing the following:
 
-```yml
+```yaml
 include:
   - template: Auto-DevOps.gitlab-ci.yml
 ```
 
-Then add any extra changes you want. Your additions will be merged with the
-[Auto DevOps template](https://gitlab.com/gitlab-org/gitlab/blob/master/lib/gitlab/ci/templates/Auto-DevOps.gitlab-ci.yml) using the behaviour described for
-[`include`](../../ci/yaml/README.md#include).
+Add your changes, and your additions will be merged with the
+[Auto DevOps template](https://gitlab.com/gitlab-org/gitlab/blob/master/lib/gitlab/ci/templates/Auto-DevOps.gitlab-ci.yml)
+using the behavior described for [`include`](../../ci/yaml/README.md#include).
 
-It is also possible to copy and paste the contents of the [Auto DevOps template](https://gitlab.com/gitlab-org/gitlab/blob/master/lib/gitlab/ci/templates/Auto-DevOps.gitlab-ci.yml)
-into your project and edit this as needed. You may prefer to do it
-that way if you want to specifically remove any part of it.
+If you need to specifically remove a part of the file, you can also copy and paste the contents of the
+[Auto DevOps template](https://gitlab.com/gitlab-org/gitlab/blob/master/lib/gitlab/ci/templates/Auto-DevOps.gitlab-ci.yml)
+into your project and edit it as needed.
 
 ## Customizing the Kubernetes namespace
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/27630) in GitLab 12.6.
 
-For **non**-GitLab-managed clusters, the namespace can be customized using
+For clusters not managed by GitLab, you can customize the namespace in
 `.gitlab-ci.yml` by specifying
 [`environment:kubernetes:namespace`](../../ci/environments.md#configuring-kubernetes-deployments).
 For example, the following configuration overrides the namespace used for
@@ -212,15 +216,14 @@ include:
   - template: Jobs/Build.gitlab-ci.yml
 ```
 
-Consult the [Auto DevOps template](https://gitlab.com/gitlab-org/gitlab/blob/master/lib/gitlab/ci/templates/Auto-DevOps.gitlab-ci.yml) for information on available jobs.
+See the [Auto DevOps template](https://gitlab.com/gitlab-org/gitlab/blob/master/lib/gitlab/ci/templates/Auto-DevOps.gitlab-ci.yml) for information on available jobs.
 
 ## PostgreSQL database support
 
-In order to support applications that require a database,
+To support applications requiring a database,
 [PostgreSQL](https://www.postgresql.org/) is provisioned by default. The credentials to access
 the database are preconfigured, but can be customized by setting the associated
-[variables](#environment-variables). These credentials can be used for defining a
-`DATABASE_URL` of the format:
+[variables](#environment-variables). You can use these credentials to define a `DATABASE_URL`:
 
 ```yaml
 postgres://user:password@postgres-host:postgres-port/postgres-database
@@ -230,7 +233,7 @@ postgres://user:password@postgres-host:postgres-port/postgres-database
 
 CAUTION: **Deprecation**
 The variable `AUTO_DEVOPS_POSTGRES_CHANNEL` that controls default provisioned
-PostgreSQL currently defaults to `1`. This is scheduled to change to `2` in
+PostgreSQL currently defaults to `1`. This value is scheduled to change to `2` in
 [GitLab 13.0](https://gitlab.com/gitlab-org/gitlab/-/issues/210499).
 
 The version of the chart used to provision PostgreSQL:
@@ -250,19 +253,18 @@ To use the new PostgreSQL:
 ### Using external PostgreSQL database providers
 
 While Auto DevOps provides out-of-the-box support for a PostgreSQL container for
-production environments, for some use-cases it may not be sufficiently secure or
-resilient and you may wish to use an external managed provider for PostgreSQL.
-For example, AWS Relational Database Service.
+production environments, for some use cases, it may not be sufficiently secure or
+resilient, and you may want to use an external managed provider (such as
+AWS Relational Database Service) for PostgreSQL.
 
-You will need to define environment-scoped variables for `POSTGRES_ENABLED` and `DATABASE_URL` in your project's CI/CD settings.
-
-To achieve this:
+You must define environment-scoped variables for `POSTGRES_ENABLED` and
+`DATABASE_URL` in your project's CI/CD settings:
 
 1. Disable the built-in PostgreSQL installation for the required environments using
    scoped [environment variables](../../ci/environments.md#scoping-environments-with-specs).
    For this use case, it's likely that only `production` will need to be added to this
-   list as the builtin PostgreSQL setup for Review Apps and staging will be sufficient
-   as a high availability setup is not required.
+   list. The built-in PostgreSQL setup for Review Apps and staging is sufficient,
+   because a high availability setup is not required.
 
    ![Auto Metrics](img/disable_postgres.png)
 
@@ -273,14 +275,14 @@ To achieve this:
    postgres://user:password@postgres-host:postgres-port/postgres-database
    ```
 
-You will need to ensure that your Kubernetes cluster has network access to wherever
+You must ensure that your Kubernetes cluster has network access to wherever
 PostgreSQL is hosted.
 
 ## Environment variables
 
 The following variables can be used for setting up the Auto DevOps domain,
 providing a custom Helm chart, or scaling your application. PostgreSQL can
-also be customized, and you can easily use a [custom buildpack](#custom-buildpacks).
+also be customized, and you can use a [custom buildpack](#custom-buildpacks).
 
 ### Build and deployment
 
@@ -292,34 +294,34 @@ applications.
 | `ADDITIONAL_HOSTS`                      | Fully qualified domain names specified as a comma-separated list that are added to the Ingress hosts. |
 | `<ENVIRONMENT>_ADDITIONAL_HOSTS`        | For a specific environment, the fully qualified domain names specified as a comma-separated list that are added to the Ingress hosts. This takes precedence over `ADDITIONAL_HOSTS`. |
 | `AUTO_DEVOPS_BUILD_IMAGE_CNB_ENABLED`   | When set to a non-empty value and no `Dockerfile` is present, Auto Build builds your application using Cloud Native Buildpacks instead of Herokuish. [More details](stages.md#auto-build-using-cloud-native-buildpacks-beta). |
-| `AUTO_DEVOPS_BUILD_IMAGE_EXTRA_ARGS`    | Extra arguments to be passed to the `docker build` command. Note that using quotes will not prevent word splitting. [More details](#passing-arguments-to-docker-build). |
+| `AUTO_DEVOPS_BUILD_IMAGE_EXTRA_ARGS`    | Extra arguments to be passed to the `docker build` command. Note that using quotes won't prevent word splitting. [More details](#passing-arguments-to-docker-build). |
 | `AUTO_DEVOPS_BUILD_IMAGE_FORWARDED_CI_VARIABLES` | A [comma-separated list of CI variable names](#passing-secrets-to-docker-build) to be passed to the `docker build` command as secrets. |
 | `AUTO_DEVOPS_CHART`                     | Helm Chart used to deploy your apps. Defaults to the one [provided by GitLab](https://gitlab.com/gitlab-org/charts/auto-deploy-app). |
 | `AUTO_DEVOPS_CHART_REPOSITORY`          | Helm Chart repository used to search for charts. Defaults to `https://charts.gitlab.io`. |
 | `AUTO_DEVOPS_CHART_REPOSITORY_NAME`     | From GitLab 11.11, used to set the name of the Helm repository. Defaults to `gitlab`. |
 | `AUTO_DEVOPS_CHART_REPOSITORY_USERNAME` | From GitLab 11.11, used to set a username to connect to the Helm repository. Defaults to no credentials. Also set `AUTO_DEVOPS_CHART_REPOSITORY_PASSWORD`. |
 | `AUTO_DEVOPS_CHART_REPOSITORY_PASSWORD` | From GitLab 11.11, used to set a password to connect to the Helm repository. Defaults to no credentials. Also set `AUTO_DEVOPS_CHART_REPOSITORY_USERNAME`. |
-| `AUTO_DEVOPS_MODSECURITY_SEC_RULE_ENGINE` | From GitLab 12.5, used in combination with [Modsecurity feature flag](../../user/clusters/applications.md#web-application-firewall-modsecurity) to toggle [Modsecurity's `SecRuleEngine`](https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual-(v2.x)#SecRuleEngine) behavior. Defaults to `DetectionOnly`. |
+| `AUTO_DEVOPS_MODSECURITY_SEC_RULE_ENGINE` | From GitLab 12.5, used in combination with [ModSecurity feature flag](../../user/clusters/applications.md#web-application-firewall-modsecurity) to toggle [ModSecurity's `SecRuleEngine`](https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual-(v2.x)#SecRuleEngine) behavior. Defaults to `DetectionOnly`. |
 | `BUILDPACK_URL`                         | Buildpack's full URL. Can point to either [a Git repository URL or a tarball URL](#custom-buildpacks). |
 | `CANARY_ENABLED`                        | From GitLab 11.0, used to define a [deploy policy for canary environments](#deploy-policy-for-canary-environments-premium). |
 | `CANARY_PRODUCTION_REPLICAS`            | Number of canary replicas to deploy for [Canary Deployments](../../user/project/canary_deployments.md) in the production environment. Takes precedence over `CANARY_REPLICAS`. Defaults to 1. |
 | `CANARY_REPLICAS`                       | Number of canary replicas to deploy for [Canary Deployments](../../user/project/canary_deployments.md). Defaults to 1. |
 | `HELM_RELEASE_NAME`                     | From GitLab 12.1, allows the `helm` release name to be overridden. Can be used to assign unique release names when deploying multiple projects to a single namespace. |
 | `HELM_UPGRADE_VALUES_FILE`              | From GitLab 12.6, allows the `helm upgrade` values file to be overridden. Defaults to `.gitlab/auto-deploy-values.yaml`. |
-| `HELM_UPGRADE_EXTRA_ARGS`               | From GitLab 11.11, allows extra arguments in `helm` commands when deploying the application. Note that using quotes will not prevent word splitting. **Tip:** you can use this variable to [customize the Auto Deploy Helm chart](#custom-helm-chart) by applying custom override values with `--values my-values.yaml`. |
+| `HELM_UPGRADE_EXTRA_ARGS`               | From GitLab 11.11, allows extra arguments in `helm` commands when deploying the application. Note that using quotes won't prevent word splitting. **Tip:** you can use this variable to [customize the Auto Deploy Helm chart](#custom-helm-chart) by applying custom override values with `--values my-values.yaml`. |
 | `INCREMENTAL_ROLLOUT_MODE`              | From GitLab 11.4, if present, can be used to enable an [incremental rollout](#incremental-rollout-to-production-premium) of your application for the production environment. Set to `manual` for manual deployment jobs or `timed` for automatic rollout deployments with a 5 minute delay each one. |
 | `K8S_SECRET_*`                          | From GitLab 11.7, any variable prefixed with [`K8S_SECRET_`](#application-secret-variables) will be made available by Auto DevOps as environment variables to the deployed application. |
 | `KUBE_INGRESS_BASE_DOMAIN`              | From GitLab 11.8, can be used to set a domain per cluster. See [cluster domains](../../user/project/clusters/index.md#base-domain) for more information. |
 | `PRODUCTION_REPLICAS`                   | Number of replicas to deploy in the production environment. Takes precedence over `REPLICAS` and defaults to 1. For zero downtime upgrades, set to 2 or greater. |
 | `REPLICAS`                              | Number of replicas to deploy. Defaults to 1. |
 | `ROLLOUT_RESOURCE_TYPE`                 | From GitLab 11.9, allows specification of the resource type being deployed when using a custom Helm chart. Default value is `deployment`. |
-| `ROLLOUT_STATUS_DISABLED`               | From GitLab 12.0, used to disable rollout status check because it doesn't support all resource types, for example, `cronjob`. |
+| `ROLLOUT_STATUS_DISABLED`               | From GitLab 12.0, used to disable rollout status check because it does not support all resource types, for example, `cronjob`. |
 | `STAGING_ENABLED`                       | From GitLab 10.8, used to define a [deploy policy for staging and production environments](#deploy-policy-for-staging-and-production-environments). |
 
 TIP: **Tip:**
 Set up the replica variables using a
 [project variable](../../ci/variables/README.md#gitlab-cicd-environment-variables)
-and scale your application by just redeploying it!
+and scale your application by only redeploying it.
 
 CAUTION: **Caution:**
 You should *not* scale your application using Kubernetes directly. This can
@@ -334,7 +336,7 @@ The following table lists variables related to the database.
 |-----------------------------------------|------------------------------------|
 | `DB_INITIALIZE`                         | From GitLab 11.4, used to specify the command to run to initialize the application's PostgreSQL database. Runs inside the application pod. |
 | `DB_MIGRATE`                            | From GitLab 11.4, used to specify the command to run to migrate the application's PostgreSQL database. Runs inside the application pod. |
-| `POSTGRES_ENABLED`                      | Whether PostgreSQL is enabled. Defaults to `"true"`. Set to `false` to disable the automatic deployment of PostgreSQL. |
+| `POSTGRES_ENABLED`                      | Whether PostgreSQL is enabled. Defaults to `true`. Set to `false` to disable the automatic deployment of PostgreSQL. |
 | `POSTGRES_USER`                         | The PostgreSQL user. Defaults to `user`. Set it to use a custom username. |
 | `POSTGRES_PASSWORD`                     | The PostgreSQL password. Defaults to `testing-password`. Set it to use a custom password. |
 | `POSTGRES_DB`                           | The PostgreSQL database name. Defaults to the value of [`$CI_ENVIRONMENT_SLUG`](../../ci/variables/README.md#predefined-environment-variables). Set it to use a custom database name. |
@@ -354,35 +356,34 @@ The following table lists variables used to disable jobs.
 
 | **Variable**                            | **Description**                    |
 |-----------------------------------------|------------------------------------|
-| `CODE_QUALITY_DISABLED`                 | From GitLab 11.0, used to disable the `codequality` job. If the variable is present, the job will not be created. |
-| `CONTAINER_SCANNING_DISABLED`           | From GitLab 11.0, used to disable the `sast:container` job. If the variable is present, the job will not be created. |
-| `DAST_DISABLED`                         | From GitLab 11.0, used to disable the `dast` job. If the variable is present, the job will not be created. |
-| `DEPENDENCY_SCANNING_DISABLED`          | From GitLab 11.0, used to disable the `dependency_scanning` job. If the variable is present, the job will not be created. |
-| `LICENSE_MANAGEMENT_DISABLED`           | From GitLab 11.0, used to disable the `license_management` job. If the variable is present, the job will not be created. |
-| `PERFORMANCE_DISABLED`                  | From GitLab 11.0, used to disable the `performance` job. If the variable is present, the job will not be created. |
-| `REVIEW_DISABLED`                       | From GitLab 11.0, used to disable the `review` and the manual `review:stop` job. If the variable is present, these jobs will not be created. |
-| `SAST_DISABLED`                         | From GitLab 11.0, used to disable the `sast` job. If the variable is present, the job will not be created. |
-| `TEST_DISABLED`                         | From GitLab 11.0, used to disable the `test` job. If the variable is present, the job will not be created. |
+| `CODE_QUALITY_DISABLED`                 | From GitLab 11.0, used to disable the `codequality` job. If the variable is present, the job won't be created. |
+| `CONTAINER_SCANNING_DISABLED`           | From GitLab 11.0, used to disable the `sast:container` job. If the variable is present, the job won't be created. |
+| `DAST_DISABLED`                         | From GitLab 11.0, used to disable the `dast` job. If the variable is present, the job won't be created. |
+| `DEPENDENCY_SCANNING_DISABLED`          | From GitLab 11.0, used to disable the `dependency_scanning` job. If the variable is present, the job won't be created. |
+| `LICENSE_MANAGEMENT_DISABLED`           | From GitLab 11.0, used to disable the `license_management` job. If the variable is present, the job won't be created. |
+| `PERFORMANCE_DISABLED`                  | From GitLab 11.0, used to disable the `performance` job. If the variable is present, the job won't be created. |
+| `REVIEW_DISABLED`                       | From GitLab 11.0, used to disable the `review` and the manual `review:stop` job. If the variable is present, these jobs won't be created. |
+| `SAST_DISABLED`                         | From GitLab 11.0, used to disable the `sast` job. If the variable is present, the job won't be created. |
+| `TEST_DISABLED`                         | From GitLab 11.0, used to disable the `test` job. If the variable is present, the job won't be created. |
 
 ### Application secret variables
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/issues/49056) in GitLab 11.7.
 
-Some applications need to define secret variables that are
-accessible by the deployed application. Auto DevOps detects variables where the key starts with
-`K8S_SECRET_` and make these prefixed variables available to the
-deployed application, as environment variables.
+Some applications need to define secret variables that are accessible by the deployed
+application. Auto DevOps detects variables starting with `K8S_SECRET_`, and makes
+these prefixed variables available to the deployed application as environment variables.
 
 To configure your application variables:
 
-1. Go to your project's **Settings > CI/CD**, then expand the section
-   called **Variables**.
+1. Go to your project's **{settings}** **Settings > CI/CD**, then expand the
+   **Variables** section.
 
-1. Create a CI Variable, ensuring the key is prefixed with
+1. Create a CI/CD variable, ensuring the key is prefixed with
    `K8S_SECRET_`. For example, you can create a variable with key
    `K8S_SECRET_RAILS_MASTER_KEY`.
 
-1. Run an Auto Devops pipeline either by manually creating a new
+1. Run an Auto DevOps pipeline, either by manually creating a new
    pipeline or by pushing a code change to GitLab.
 
 Auto DevOps pipelines will take your application secret variables to
@@ -394,6 +395,7 @@ example above, you can see the secret below containing the
 
 ```shell
 $ kubectl get secret production-secret -n minimal-ruby-app-54 -o yaml
+
 apiVersion: v1
 data:
   RAILS_MASTER_KEY: MTIzNC10ZXN0
@@ -408,40 +410,37 @@ metadata:
 type: Opaque
 ```
 
-Environment variables are generally considered immutable in a Kubernetes
-pod. Therefore, if you update an application secret without changing any
-code then manually create a new pipeline, you will find that any running
-application pods will not have the updated secrets. In this case, you
-can either push a code update to GitLab to force the Kubernetes
-Deployment to recreate pods or manually delete running pods to
-cause Kubernetes to create new pods with updated secrets.
+Environment variables are generally considered immutable in a Kubernetes pod.
+If you update an application secret without changing any code, then manually
+create a new pipeline, you will find any running application pods won't have
+the updated secrets. To update the secrets, either:
+
+- Push a code update to GitLab to force the Kubernetes deployment to recreate pods.
+- Manually delete running pods to cause Kubernetes to create new pods with updated
+  secrets.
 
 NOTE: **Note:**
-Variables with multiline values are not currently supported due to
+Variables with multi-line values are not currently supported due to
 limitations with the current Auto DevOps scripting environment.
 
 ### Advanced replica variables setup
 
 Apart from the two replica-related variables for production mentioned above,
-you can also use others for different environments.
+you can also use other variables for different environments.
 
-There's a very specific mapping between Kubernetes' label named `track`,
-GitLab CI/CD environment names, and the replicas environment variable.
-The general rule is: `TRACK_ENV_REPLICAS`. Where:
+The Kubernetes' label named `track`, GitLab CI/CD environment names, and the
+replicas environment variable are combined into the format `TRACK_ENV_REPLICAS`,
+enabling you to define your own variables for scaling the pod's replicas:
 
 - `TRACK`: The capitalized value of the `track`
   [Kubernetes label](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/)
-  in the Helm Chart app definition. If not set, it will not be taken into account
+  in the Helm Chart app definition. If not set, it won't be taken into account
   to the variable name.
-- `ENV`: The capitalized environment name of the deploy job that is set in
+- `ENV`: The capitalized environment name of the deploy job, set in
   `.gitlab-ci.yml`.
 
-That way, you can define your own `TRACK_ENV_REPLICAS` variables with which
-you will be able to scale the pod's replicas easily.
-
-In the example below, the environment's name is `qa` and it deploys the track
-`foo` which would result in looking for the `FOO_QA_REPLICAS` environment
-variable:
+In the example below, the environment's name is `qa`, and it deploys the track
+`foo`, which results in an environment variable named `FOO_QA_REPLICAS`:
 
 ```yaml
 QA testing:
@@ -452,8 +451,7 @@ QA testing:
   - deploy foo
 ```
 
-The track `foo` being referenced would also need to be defined in the
-application's Helm chart, like:
+The track `foo` being referenced must also be defined in the application's Helm chart, like:
 
 ```yaml
 replicaCount: 1
@@ -482,30 +480,29 @@ service:
 TIP: **Tip:**
 You can also set this inside your [project's settings](index.md#deployment-strategy).
 
-The normal behavior of Auto DevOps is to use Continuous Deployment, pushing
+The normal behavior of Auto DevOps is to use continuous deployment, pushing
 automatically to the `production` environment every time a new pipeline is run
 on the default branch. However, there are cases where you might want to use a
-staging environment and deploy to production manually. For this scenario, the
+staging environment, and deploy to production manually. For this scenario, the
 `STAGING_ENABLED` environment variable was introduced.
 
-If `STAGING_ENABLED` is defined in your project (e.g., set `STAGING_ENABLED` to
-`1` as a CI/CD variable), then the application will be automatically deployed
-to a `staging` environment, and a  `production_manual` job will be created for
+If you define `STAGING_ENABLED`, such as setting `STAGING_ENABLED` to
+`1` as a CI/CD variable, then GitLab automatically deploys the application
+to a `staging` environment, and creates a `production_manual` job for
 you when you're ready to manually deploy to production.
 
 ### Deploy policy for canary environments **(PREMIUM)**
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-ci-yml/-/merge_requests/171) in GitLab 11.0.
 
-A [canary environment](../../user/project/canary_deployments.md) can be used
-before any changes are deployed to production.
+You can use a [canary environment](../../user/project/canary_deployments.md) before
+deploying any changes to production.
 
-If `CANARY_ENABLED` is defined in your project (e.g., set `CANARY_ENABLED` to
-`1` as a CI/CD variable) then two manual jobs will be created:
+If you define `CANARY_ENABLED` in your project, such as setting `CANARY_ENABLED` to
+`1` as a CI/CD variable, then two manual jobs are created:
 
-- `canary` which will deploy the application to the canary environment
-- `production_manual` which is to be used by you when you're ready to manually
-  deploy to production.
+- `canary` - Deploys the application to the canary environment.
+- `production_manual` - Manually deploys the application to production.
 
 ### Incremental rollout to production **(PREMIUM)**
 
@@ -514,10 +511,9 @@ If `CANARY_ENABLED` is defined in your project (e.g., set `CANARY_ENABLED` to
 TIP: **Tip:**
 You can also set this inside your [project's settings](index.md#deployment-strategy).
 
-When you have a new version of your app to deploy in production, you may want
-to use an incremental rollout to replace just a few pods with the latest code.
-This will allow you to first check how the app is behaving, and later manually
-increasing the rollout up to 100%.
+When you're ready to deploy a new version of your app to production, you may want
+to use an incremental rollout to replace just a few pods with the latest code to
+check how the application is behaving before manually increasing the rollout up to 100%.
 
 If `INCREMENTAL_ROLLOUT_MODE` is set to `manual` in your project, then instead
 of the standard `production` job, 4 different
@@ -529,14 +525,14 @@ will be created:
 1. `rollout 50%`
 1. `rollout 100%`
 
-The percentage is based on the `REPLICAS` variable and defines the number of
-pods you want to have for your deployment. If you say `10`, and then you run
-the `10%` rollout job, there will be `1` new pod + `9` old ones.
+The percentage is based on the `REPLICAS` variable, and defines the number of
+pods you want to have for your deployment. If the value is `10`, and you run the
+`10%` rollout job, there will be `1` new pod + `9` old ones.
 
-To start a job, click on the play icon next to the job's name. You are not
+To start a job, click the play icon (**{play}**) next to the job's name. You're not
 required to go from `10%` to `100%`, you can jump to whatever job you want.
 You can also scale down by running a lower percentage job, just before hitting
-`100%`. Once you get to `100%`, you cannot scale down, and you'd have to roll
+`100%`. Once you get to `100%`, you can't scale down, and you'd have to roll
 back by redeploying the old version using the
 [rollback button](../../ci/environments.md#retrying-and-rolling-back) in the
 environment page.
@@ -561,9 +557,9 @@ With `INCREMENTAL_ROLLOUT_MODE` set to `manual` and with `STAGING_ENABLED`
 ![Rollout and staging enabled](img/rollout_staging_enabled.png)
 
 CAUTION: **Caution:**
-Before GitLab 11.4 this feature was enabled by the presence of the
-`INCREMENTAL_ROLLOUT_ENABLED` environment variable.
-This configuration is deprecated and will be removed in the future.
+Before GitLab 11.4, the presence of the `INCREMENTAL_ROLLOUT_ENABLED` environment
+variable enabled this feature. This configuration is deprecated, and will be
+removed in the future.
 
 ### Timed incremental rollout to production **(PREMIUM)**
 
@@ -577,8 +573,10 @@ This configuration is based on
 
 Everything behaves the same way, except:
 
-- It's enabled by setting the `INCREMENTAL_ROLLOUT_MODE` variable to `timed`.
-- Instead of the standard `production` job, the following jobs are created with a 5 minute delay between each :
+- To enable it, set the `INCREMENTAL_ROLLOUT_MODE` variable to `timed`.
+- Instead of the standard `production` job, the following jobs are created with
+  a 5 minute delay between each:
+
   1. `timed rollout 10%`
   1. `timed rollout 25%`
   1. `timed rollout 50%`
@@ -586,15 +584,15 @@ Everything behaves the same way, except:
 
 ## Auto DevOps banner
 
-The following Auto DevOps banner will show for maintainers+ on new projects when Auto DevOps is not
-enabled:
+The following Auto DevOps banner displays for users with Maintainer or greater
+permissions on new projects when Auto DevOps is not enabled:
 
 ![Auto DevOps banner](img/autodevops_banner_v12_6.png)
 
 The banner can be disabled for:
 
-- A user when they dismiss it themselves.
-- A project by explicitly [disabling Auto DevOps](index.md#enablingdisabling-auto-devops).
+- A user, when they dismiss it themselves.
+- A project, by explicitly [disabling Auto DevOps](index.md#enablingdisabling-auto-devops).
 - An entire GitLab instance:
   - By an administrator running the following in a Rails console:
 
diff --git a/doc/topics/autodevops/img/guide_environments_metrics_v12_3.png b/doc/topics/autodevops/img/guide_environments_metrics_v12_3.png
deleted file mode 100644
index 47bf3fda53a..00000000000
--- a/doc/topics/autodevops/img/guide_environments_metrics_v12_3.png
+++ /dev/null
diff --git a/doc/topics/autodevops/img/guide_project_landing_page_v12_10.png b/doc/topics/autodevops/img/guide_project_landing_page_v12_10.png
new file mode 100644
index 00000000000..ec646c50a20
--- /dev/null
+++ b/doc/topics/autodevops/img/guide_project_landing_page_v12_10.png
diff --git a/doc/topics/autodevops/img/guide_project_landing_page_v12_3.png b/doc/topics/autodevops/img/guide_project_landing_page_v12_3.png
deleted file mode 100644
index 7eb2ee3692f..00000000000
--- a/doc/topics/autodevops/img/guide_project_landing_page_v12_3.png
+++ /dev/null
diff --git a/doc/topics/autodevops/index.md b/doc/topics/autodevops/index.md
index 043bb0dfcfa..7ed6625bea3 100644
--- a/doc/topics/autodevops/index.md
+++ b/doc/topics/autodevops/index.md
@@ -418,12 +418,23 @@ spec:
 
 ## Troubleshooting
 
-- Auto Build and Auto Test may fail in detecting your language/framework. There
-  may be no buildpack for your application, or your application may be missing the
-  key files the buildpack is looking for. For example, for Ruby applications, you must
-  have a `Gemfile` to be properly detected, even though it is possible to write a
-  Ruby app without a `Gemfile`. Try specifying a [custom
-  buildpack](customize.md#custom-buildpacks).
+- Auto Build and Auto Test may fail to detect your language or framework with the
+  following error:
+
+  ```plaintext
+  Step 5/11 : RUN /bin/herokuish buildpack build
+   ---> Running in eb468cd46085
+      -----> Unable to select a buildpack
+  The command '/bin/sh -c /bin/herokuish buildpack build' returned a non-zero code: 1
+  ```
+
+  The following are possible reasons:
+
+  - Your application may be missing the key files the buildpack is looking for. For
+    example, for Ruby applications you must have a `Gemfile` to be properly detected,
+    even though it is possible to write a Ruby app without a `Gemfile`.
+  - There may be no buildpack for your application. Try specifying a
+    [custom buildpack](customize.md#custom-buildpacks).
 - Auto Test may fail because of a mismatch between testing frameworks. In this
   case, you may need to customize your `.gitlab-ci.yml` with your test commands.
 - Auto Deploy will fail if GitLab can not create a Kubernetes namespace and
diff --git a/doc/topics/autodevops/quick_start_guide.md b/doc/topics/autodevops/quick_start_guide.md
index 493e3b727a8..3fb4aa64f3f 100644
--- a/doc/topics/autodevops/quick_start_guide.md
+++ b/doc/topics/autodevops/quick_start_guide.md
@@ -1,42 +1,45 @@
 # Getting started with Auto DevOps
 
-This is a step-by-step guide that will help you use [Auto DevOps](index.md) to
+This step-by-step guide will help you use [Auto DevOps](index.md) to
 deploy a project hosted on GitLab.com to Google Kubernetes Engine.
 
-We will use GitLab's native Kubernetes integration, so you will not need
+You will use GitLab's native Kubernetes integration, so you won't need
 to create a Kubernetes cluster manually using the Google Cloud Platform console.
-We will create and deploy a simple application that we create from a GitLab template.
+You will create and deploy a simple application that you create from a GitLab template.
 
 These instructions will also work for a self-managed GitLab instance; you'll just
 need to ensure your own [Runners are configured](../../ci/runners/README.md) and
 [Google OAuth is enabled](../../integration/google.md).
 
-## Configuring your Google account
+## Configure your Google account
 
 Before creating and connecting your Kubernetes cluster to your GitLab project,
-you need a Google Cloud Platform account. If you don't already have one,
-sign up at <https://console.cloud.google.com>. You'll need to either sign in with an existing
-Google account (for example, one that you use to access Gmail, Drive, etc.) or create a new one.
+you need a [Google Cloud Platform account](https://console.cloud.google.com).
+Sign in with an existing Google account, such as the one you use to access Gmail
+or Google Drive, or create a new one.
 
-1. Follow the steps as outlined in the ["Before you begin" section of the Kubernetes Engine docs](https://cloud.google.com/kubernetes-engine/docs/quickstart#before-you-begin)
-   in order for the required APIs and related services to be enabled.
-1. Make sure you have created a [billing account](https://cloud.google.com/billing/docs/how-to/manage-billing-account).
+1. Follow the steps described in the ["Before you begin" section](https://cloud.google.com/kubernetes-engine/docs/quickstart#before-you-begin)
+   of the Kubernetes Engine docs to enable the required APIs and related services.
+1. Ensure you've created a [billing account](https://cloud.google.com/billing/docs/how-to/manage-billing-account)
+   with Google Cloud Platform.
 
 TIP: **Tip:**
 Every new Google Cloud Platform (GCP) account receives [$300 in credit](https://console.cloud.google.com/freetrial),
-and in partnership with Google, GitLab is able to offer an additional $200 for new GCP accounts to get started with GitLab's
-Google Kubernetes Engine Integration. All you have to do is [follow this link](https://cloud.google.com/partners/partnercredit/?pcn_code=0014M00001h35gDQAQ#contact-form) and apply for credit.
+and in partnership with Google, GitLab is able to offer an additional $200 for new
+GCP accounts to get started with GitLab's Google Kubernetes Engine Integration.
+[Follow this link](https://cloud.google.com/partners/partnercredit/?pcn_code=0014M00001h35gDQAQ#contact-form)
+and apply for credit.
 
-## Creating a new project from a template
+## Create a new project from a template
 
 We will use one of GitLab's project templates to get started. As the name suggests,
 those projects provide a bare-bones application built on some well-known frameworks.
 
-1. In GitLab, click the plus icon (**+**) at the top of the navigation bar and select
+1. In GitLab, click the plus icon (**{plus-square}**) at the top of the navigation bar, and select
    **New project**.
-1. Go to the **Create from template** tab where you can choose among a Ruby on
+1. Go to the **Create from template** tab, where you can choose among a Ruby on
    Rails, Spring, or NodeJS Express project.
-   We'll use the Ruby on Rails template.
+   For this tutorial, use the Ruby on Rails template.
 
    ![Select project template](img/guide_project_template_v12_3.png)
 
@@ -48,196 +51,215 @@ those projects provide a bare-bones application built on some well-known framewo
 
 1. Click **Create project**.
 
-Now that the project is created, the next step is to create the Kubernetes cluster
-under which this application will be deployed.
+Now that you've created a project, you'll next create the Kubernetes cluster
+to deploy this project to.
 
-## Creating a Kubernetes cluster from within GitLab
+## Create a Kubernetes cluster from within GitLab
 
-1. On the project's landing page, click the button labeled **Add Kubernetes cluster**
-   (note that this option is also available when you navigate to **Operations > Kubernetes**).
+1. On your project's landing page, click **Add Kubernetes cluster**
+   (note that this option is also available when you navigate to **{cloud-gear}** **Operations > Kubernetes**).
 
-   ![Project landing page](img/guide_project_landing_page_v12_3.png)
+   ![Project landing page](img/guide_project_landing_page_v12_10.png)
 
-1. One the **Create new cluster on GKE** tab, click "Sign in with Google".
+1. On the **Add a Kubernetes cluster integration** page, click the **Create new cluster** tab,
+   then click **Google GKE**.
 
    ![Google sign in](img/guide_google_signin_v12_3.png)
 
-1. Connect with your Google account and press **Allow** when asked (this will
-   be shown only the first time you connect GitLab with your Google account).
-
-   ![Google auth](img/guide_google_auth_v12_3.png)
-
-1. The last step is to provide the cluster details. Give it a name, leave the
-   environment scope as is, and choose the GCP project under which the cluster
-   will be created. (Per the instructions when you
-   [configured your Google account](#configuring-your-google-account), a project
-   should have already been created for you.) Next, choose the
-   [region/zone](https://cloud.google.com/compute/docs/regions-zones/) under which the
-   cluster will be created, enter the number of nodes you want it to have, and
-   finally choose the [machine type](https://cloud.google.com/compute/docs/machine-types).
-
-   ![GitLab GKE cluster details](img/guide_gitlab_gke_details_v12_3.png)
-
-1. Once ready, click **Create Kubernetes cluster**.
+1. Connect with your Google account, and click **Allow** to allow access to your
+   Google account. (This authorization request is only displayed the first time
+   you connect GitLab with your Google account.)
+
+   After authorizing access, the **Add a Kubernetes cluster integration** page
+   is displayed.
+
+1. In the **Enter the details for your Kubernetes cluster** section, provide
+   details about your cluster:
+
+   - **Kubernetes cluster name**
+   - **Environment scope** - Leave this field unchanged.
+   - **Google Cloud Platform project** - Select a project. When you
+     [configured your Google account](#configure-your-google-account), a project
+     should have already been created for you.
+   - **Zone** - The [region/zone](https://cloud.google.com/compute/docs/regions-zones/) to
+     create the cluster in.
+   - **Number of nodes**
+   - **Machine type** - For more information about
+     [machine types](https://cloud.google.com/compute/docs/machine-types), see Google's documentation.
+   - **Enable Cloud Run for Anthos** - Select this checkbox to use the Cloud Run,
+     Istio, and HTTP Load Balancing add-ons for this cluster.
+   - **GitLab-managed cluster** - Select this checkbox to
+     [allow GitLab to manage namespace and service accounts](../..//user/project/clusters/index.md#gitlab-managed-clusters) for this cluster.
+
+1. Click **Create Kubernetes cluster**.
 
 After a couple of minutes, the cluster will be created. You can also see its
 status on your [GCP dashboard](https://console.cloud.google.com/kubernetes).
 
-The next step is to install some applications on your cluster that are needed
+Next, you will install some applications on your cluster that are needed
 to take full advantage of Auto DevOps.
 
-## Installing Helm, Ingress, and Prometheus
+## Install the package manager
 
-GitLab's Kubernetes integration comes with some
+After creating your Kubernetes cluster, GitLab's Kubernetes integration provides
 [pre-defined applications](../../user/project/clusters/index.md#installing-applications)
-for you to install.
-
-![Cluster applications](img/guide_cluster_apps_v12_3.png)
-
-The first one to install is Helm Tiller, a package manager for Kubernetes, which
-is needed in order to install the rest of the applications. Go ahead and click
-its **Install** button.
+for you to install. To install them, you must next install Helm Tiller, the
+Kubernetes package manager for Kubernetes, to enable the installation of other applications.
 
-Once it's installed, the other applications that rely on it will each have their **Install**
-button enabled. For this guide, we need Ingress and Prometheus. Ingress provides
-load balancing, SSL termination, and name-based virtual hosting, using NGINX behind
-the scenes. Prometheus is an open-source monitoring and alerting system that we'll
-use to supervise the deployed application. We will not install GitLab Runner as
-we'll use the shared Runners that GitLab.com provides.
+Next to **Helm Tiller**, click **Install**.
 
-After the Ingress is installed, wait a few seconds and copy the IP address that
-is displayed in order to add in your base **Domain** at the top of the page. For
-the purpose of this guide, we will use the one suggested by GitLab. Once you have
-filled in the domain, click **Save changes**.
-
-![Cluster Base Domain](img/guide_base_domain_v12_3.png)
+![Cluster applications](img/guide_cluster_apps_v12_3.png)
 
-## Enabling Auto DevOps (optional)
+After installation completes, the page reloads, and you can install other
+applications.
 
-Starting with GitLab 11.3, Auto DevOps is enabled by default. However, it is possible to disable
-Auto DevOps at both the instance-level (for self-managed instances) and also at the group-level.
-Follow these steps if Auto DevOps has been manually disabled.
+## Install Ingress and Prometheus
 
-1. First, navigate to **Settings > CI/CD > Auto DevOps**.
-1. Select **Default to Auto DevOps pipeline**.
-1. Lastly, let's select the [continuous deployment strategy](index.md#deployment-strategy)
-   which will automatically deploy the application to production once the pipeline
-   successfully runs on the `master` branch.
-1. Click **Save changes**.
+After installing **Helm Tiller**, you can install other applications that rely on it,
+including Ingress and Prometheus, which we will install in this quick start guide:
 
-   ![Auto DevOps settings](img/guide_enable_autodevops_v12_3.png)
+- Ingress - Provides load balancing, SSL termination, and name-based virtual hosting,
+  using NGINX behind the scenes.
+- Prometheus - An open-source monitoring and alerting system used to supervise the
+  deployed application.
 
-Once you complete all the above and save your changes, a new pipeline is
-automatically created. To view the pipeline, go to **CI/CD > Pipelines**.
+NOTE: **Note:**
+We won't install GitLab Runner in this quick start guide, as this guide uses the
+shared Runners provided by GitLab.com.
 
-![First pipeline](img/guide_first_pipeline_v12_3.png)
+To install the applications:
 
-In the next section we'll break down the pipeline and explain what each job does.
+- Click the **Install** button for **Ingress**.
+- When the **Ingress Endpoint** is displayed, copy the IP address.
+- Add your **Base domain**. For this guide, we will use the domain suggested by GitLab.
+- Click **Save changes**.
 
-## Deploying the application
+![Cluster Base Domain](img/guide_base_domain_v12_3.png)
 
-By now you should see the pipeline running, but what is it running exactly?
+## Enable Auto DevOps (optional)
 
-To navigate inside the pipeline, click its status badge. (Its status should be "running").
-The pipeline is split into 4 stages, each running a couple of jobs.
+While Auto DevOps is enabled by default, Auto DevOps can be disabled at both
+the instance level (for self-managed instances) and the group level. Complete
+these steps to enable Auto DevOps if it's disabled:
 
-![Pipeline stages](img/guide_pipeline_stages_v12_3.png)
+1. Navigate to **{settings}** **Settings > CI/CD > Auto DevOps**, and click **Expand**.
+1. Select **Default to Auto DevOps pipeline** to display more options.
+1. In **Deployment strategy**, select your desired [continuous deployment strategy](index.md#deployment-strategy)
+   to deploy the application to production after the pipeline successfully runs on the `master` branch.
+1. Click **Save changes**.
 
-In the **build** stage, the application is built into a Docker image and then
-uploaded to your project's [Container Registry](../../user/packages/container_registry/index.md) ([Auto Build](stages.md#auto-build)).
+   ![Auto DevOps settings](img/guide_enable_autodevops_v12_3.png)
 
-In the **test** stage, GitLab runs various checks on the application:
+After you save your changes, GitLab creates a new pipeline. To view it, go to
+**{rocket}** **CI/CD > Pipelines**.
 
-- The `test` job runs unit and integration tests by detecting the language and
-  framework ([Auto Test](stages.md#auto-test))
-- The `code_quality` job checks the code quality and is allowed to fail
-  ([Auto Code Quality](stages.md#auto-code-quality-starter)) **(STARTER)**
-- The `container_scanning` job checks the Docker container if it has any
-  vulnerabilities and is allowed to fail ([Auto Container Scanning](stages.md#auto-container-scanning-ultimate))
-- The `dependency_scanning` job checks if the application has any dependencies
-  susceptible to vulnerabilities and is allowed to fail ([Auto Dependency Scanning](stages.md#auto-dependency-scanning-ultimate)) **(ULTIMATE)**
-- The `sast` job runs static analysis on the current code to check for potential
-  security issues and is allowed to fail([Auto SAST](stages.md#auto-sast-ultimate)) **(ULTIMATE)**
-- The `license_management` job searches the application's dependencies to determine each of their
-  licenses and is allowed to fail ([Auto License Compliance](stages.md#auto-license-compliance-ultimate)) **(ULTIMATE)**
+![First pipeline](img/guide_first_pipeline_v12_3.png)
 
-NOTE: **Note:**
-As you might have noticed, all jobs except `test` are allowed to fail in the
-test stage.
+In the next section, we explain what each job does in the pipeline.
 
-The **production** stage is run after the tests and checks finish, and it automatically
-deploys the application in Kubernetes ([Auto Deploy](stages.md#auto-deploy)).
+## Deploy the application
 
-Lastly, in the **performance** stage, some performance tests will run
-on the deployed application
-([Auto Browser Performance Testing](stages.md#auto-browser-performance-testing-premium)). **(PREMIUM)**
+When your pipeline runs, what is it doing?
 
----
+To view the jobs in the pipeline, click the pipeline's status badge. The
+**{status_running}** icon displays when pipeline jobs are running, and updates
+without refreshing the page to **{status_success}** (for success) or
+**{status_failed}** (for failure) when the jobs complete.
 
-The URL for the deployed application can be found under the **Environments**
-page where you can also monitor your application. Let's explore that.
+The jobs are separated into stages:
 
-### Monitoring
+![Pipeline stages](img/guide_pipeline_stages_v12_3.png)
 
-Now that the application is successfully deployed, let's navigate to its
-website. First, go to **Operations > Environments**.
+- **Build** - The application builds a Docker image and uploads it to your project's
+  [Container Registry](../../user/packages/container_registry/index.md) ([Auto Build](stages.md#auto-build)).
+- **Test** - GitLab runs various checks on the application:
+
+  - The `test` job runs unit and integration tests by detecting the language and
+    framework ([Auto Test](stages.md#auto-test))
+  - The `code_quality` job checks the code quality and is allowed to fail
+    ([Auto Code Quality](stages.md#auto-code-quality-starter)) **(STARTER)**
+  - The `container_scanning` job checks the Docker container if it has any
+    vulnerabilities and is allowed to fail ([Auto Container Scanning](stages.md#auto-container-scanning-ultimate))
+  - The `dependency_scanning` job checks if the application has any dependencies
+    susceptible to vulnerabilities and is allowed to fail
+    ([Auto Dependency Scanning](stages.md#auto-dependency-scanning-ultimate)) **(ULTIMATE)**
+  - The `sast` job runs static analysis on the current code to check for potential
+    security issues and is allowed to fail([Auto SAST](stages.md#auto-sast-ultimate)) **(ULTIMATE)**
+  - The `license_management` job searches the application's dependencies to determine each of their
+    licenses and is allowed to fail
+    ([Auto License Compliance](stages.md#auto-license-compliance-ultimate)) **(ULTIMATE)**
+
+   NOTE: **Note:**
+   All jobs except `test` are allowed to fail in the test stage.
+
+- **Production** - After the tests and checks finish, the application deploys in
+  Kubernetes ([Auto Deploy](stages.md#auto-deploy)).
+
+- **Performance** - Performance tests are run on the deployed application
+  ([Auto Browser Performance Testing](stages.md#auto-browser-performance-testing-premium)). **(PREMIUM)**
+
+After running a pipeline, you should view your deployed website and learn how
+to monitor it.
+
+### Monitor your project
+
+After successfully deploying your application, you can view its website and check
+on its health on the **Environments** page by navigating to
+**{cloud-gear}** **Operations > Environments**. This page displays details about
+the deployed applications, and the right-hand column displays icons that link
+you to common environment tasks:
 
 ![Environments](img/guide_environments_v12_3.png)
 
-In **Environments** you can see some details about the deployed
-applications. In the rightmost column for the production environment, you can make use of the three icons:
-
-- The first icon will open the URL of the application that is deployed in
-  production. It's a very simple page, but the important part is that it works!
-- The next icon, with the small graph, will take you to the metrics page where
-  Prometheus collects data about the Kubernetes cluster and how the application
-  affects it (in terms of memory/CPU usage, latency, etc.).
-
-  ![Environments metrics](img/guide_environments_metrics_v12_3.png)
-
-- The third icon is the [web terminal](../../ci/environments.md#web-terminals)
-  and it will open a terminal session right inside the container where the
-  application is running.
-
-Right below, there is the
-[Deploy Board](../../user/project/deploy_boards.md).
-The squares represent pods in your Kubernetes cluster that are associated with
-the given environment. Hovering above each square you can see the state of a
-deployment and clicking a square will take you to the pod's logs page.
+- **{external-link}** **Open live environment** - Opens the URL of the application deployed in production
+- **{chart}** **Monitoring** - Opens the metrics page where Prometheus collects data
+  about the Kubernetes cluster and how the application
+  affects it in terms of memory usage, CPU usage, and latency
+- **{play}** **{angle-down}** **Deploy to** - Displays a list of environments you can deploy to
+- **{terminal}** **Terminal** - Opens a [web terminal](../../ci/environments.md#web-terminals)
+  session inside the container where the application is running
+- **{repeat}** **Re-deploy to environment**
+- **{stop}** **Stop environment**
+
+GitLab displays the [Deploy Board](../../user/project/deploy_boards.md) below the
+environment's information, with squares representing pods in your
+Kubernetes cluster, color-coded to show their status. Hovering over a square on
+the deploy board displays the state of the deployment, and clicking the square
+takes you to the pod's logs page.
 
 TIP: **Tip:**
-There is only one pod hosting the application at the moment, but you can add
+The example shows only one pod hosting the application at the moment, but you can add
 more pods by defining the [`REPLICAS` variable](customize.md#environment-variables)
-under **Settings > CI/CD > Environment variables**.
+in **{settings}** **Settings > CI/CD > Environment variables**.
 
-### Working with branches
+### Work with branches
 
 Following the [GitLab flow](../gitlab_flow.md#working-with-feature-branches),
-let's create a feature branch that will add some content to the application.
+you should next create a feature branch to add content to your application:
 
-Under your repository, navigate to the following file: `app/views/welcome/index.html.erb`.
-By now, it should only contain a paragraph: `<p>You're on Rails!</p>`, so let's
-start adding content. Let's use GitLab's [Web IDE](../../user/project/web_ide/index.md) to make the change. Once
-you're on the Web IDE, make the following change:
+1. In your project's repository, navigate to the following file: `app/views/welcome/index.html.erb`.
+   This file should only contain a paragraph: `<p>You're on Rails!</p>`.
+1. Open the GitLab [Web IDE](../../user/project/web_ide/index.md) to make the change.
+1. Edit the file so it contains:
 
-```html
-<p>You're on Rails! Powered by GitLab Auto DevOps.</p>
-```
+   ```html
+   <p>You're on Rails! Powered by GitLab Auto DevOps.</p>
+   ```
 
-Stage the file, add a commit message, and create a new branch and a merge request
-by clicking **Commit**.
+1. Stage the file. Add a commit message, then create a new branch and a merge request
+   by clicking **Commit**.
 
-![Web IDE commit](img/guide_ide_commit_v12_3.png)
+   ![Web IDE commit](img/guide_ide_commit_v12_3.png)
 
-Once you submit the merge request, you'll see the pipeline running. This will
-run all the jobs as [described previously](#deploying-the-application), as well as
+After submitting the merge request, GitLab runs your pipeline, and all the jobs
+in it, as [described previously](#deploy-the-application), in addition to
 a few more that run only on branches other than `master`.
 
 ![Merge request](img/guide_merge_request_v12_3.png)
 
-After a few minutes you'll notice that there was a failure in a test.
-This means there's a test that was 'broken' by our change.
-Navigating into the `test` job that failed, you can see what the broken test is:
+After a few minutes you'll notice a test failed, which means a test was
+'broken' by your change. Click on the failed `test` job to see more information
+about it:
 
 ```plaintext
 Failure:
@@ -249,30 +271,31 @@ Expected 0 to be >= 1.
 bin/rails test test/controllers/welcome_controller_test.rb:4
 ```
 
-Let's fix that:
+To fix the broken test:
 
-1. Back to the merge request, click the **Open in Web IDE** button.
-1. Find the `test/controllers/welcome_controller_test.rb` file and open it.
+1. Return to the **Overview** page for your merge request, and click **Open in Web IDE**.
+1. In the left-hand directory of files, find the `test/controllers/welcome_controller_test.rb`
+   file, and click it to open it.
 1. Change line 7 to say `You're on Rails! Powered by GitLab Auto DevOps.`
 1. Click **Commit**.
-1. On your left, under "Unstaged changes", click the little checkmark icon
+1. In the left-hand column, under **Unstaged changes**, click the checkmark icon
    to stage the changes.
-1. Write a commit message and click **Commit**.
+1. Write a commit message, and click **Commit**.
 
-Now, if you go back to the merge request you should not only see the test passing, but
-also the application deployed as a [review app](stages.md#auto-review-apps). You
-can visit it by following clicking the **View app** button. You will see
-the changes that we previously made.
+Return to the **Overview** page of your merge request, and you should not only
+see the test passing, but also the application deployed as a
+[review application](stages.md#auto-review-apps). You can visit it by clicking
+the **View app** button to see your changes deployed.
 
 ![Review app](img/guide_merge_request_review_app_v12_3.png)
 
-Once you merge the merge request, the pipeline will run on the `master` branch,
-and the application will be eventually deployed straight to production.
+After merging the merge request, GitLab runs the pipeline on the `master` branch,
+and then deploys the application to production.
 
 ## Conclusion
 
-After implementing this project, you should now have a solid understanding of the basics of Auto DevOps.
-We started from building and testing to deploying and monitoring an application
+After implementing this project, you should have a solid understanding of the basics of Auto DevOps.
+You started from building and testing, to deploying and monitoring an application
 all within GitLab. Despite its automatic nature, Auto DevOps can also be configured
 and customized to fit your workflow. Here are some helpful resources for further reading:
 
diff --git a/doc/topics/web_application_firewall/quick_start_guide.md b/doc/topics/web_application_firewall/quick_start_guide.md
index 1d3380230af..6483a56e7f7 100644
--- a/doc/topics/web_application_firewall/quick_start_guide.md
+++ b/doc/topics/web_application_firewall/quick_start_guide.md
@@ -58,7 +58,7 @@ under which this application will be deployed.
 1. On the project's landing page, click **Add Kubernetes cluster**
    (note that this option is also available when you navigate to **Operations > Kubernetes**).
 
-   ![Project landing page](../autodevops/img/guide_project_landing_page_v12_3.png)
+   ![Project landing page](../autodevops/img/guide_project_landing_page_v12_10.png)
 
 1. On the **Create new cluster on GKE** tab, click **Sign in with Google**.