Fix the links

doc/topics/autodevops/customize.md

@@ -332,7 +332,7 @@ applications.
 | `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_DEPLOY_DEBUG`              | From GitLab 13.1, if this variable is present, Helm will output debug logs. |
-| `AUTO_DEVOPS_ALLOW_TO_FORCE_DEPLOY_V<N>` | From [auto-deploy-image](https://gitlab.com/gitlab-org/cluster-integration/auto-deploy-image) v1.0.0, if this variable is present, a new major version of chart is forcibly deployed. [More details](upgrading_auto_deploy_assets.md#ignore-warning-and-continue-deploying) |
+| `AUTO_DEVOPS_ALLOW_TO_FORCE_DEPLOY_V<N>` | From [auto-deploy-image](https://gitlab.com/gitlab-org/cluster-integration/auto-deploy-image) v1.0.0, if this variable is present, a new major version of chart is forcibly deployed. [More details](upgrading_auto_deploy_dependencies.md#ignore-warning-and-continue-deploying) |
 | `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). |

doc/topics/autodevops/stages.md

@@ -466,7 +466,7 @@ application runs.
 ### Upgrade auto-deploy-app Chart
-You can upgrade auto-deploy-app chart by following the [upgrade guide](upgrading_auto_deploy_assets.md).
+You can upgrade auto-deploy-app chart by following the [upgrade guide](upgrading_auto_deploy_dependencies.md).
 ### Workers

doc/topics/autodevops/upgrading_auto_deploy_dependencies.md

@@ -103,7 +103,7 @@ variables:
 1. Execute `<environment-name>:helm-2to3:migrate` job.
 1. Deploy your environment as usual. This deployment will use Helm 3
 1. If the deployment succeeded, you can safely run `environment:helm-2to3:cleanup`. This deletes *all* Helm 2 release data from the namespace.
-  * In case you accidentally delete the Helm 2 releases before you are ready, the `<environment-name>:helm2to3:migrate` job persists a backup for 1 week a job artifact called `helm-2-release-backups`. The backup is in a kubernetes manifest file and and they can be restored using `kubectl apply -f $backup`.
+1. In case you accidentally delete the Helm 2 releases before you are ready, the `<environment-name>:helm2to3:migrate` job persists a backup for 1 week a job artifact called `helm-2-release-backups`. The backup is in a Kubernetes manifest file and they can be restored using `kubectl apply -f $backup`.
 1. Unset the `MIGRATE_HELM_2TO3` variable
 #### Traffic routing change for canary deployment and incremental rollout
@@ -123,9 +123,9 @@ For more details, see the [v2 auto-deploy-app chart resource architecture](#v2-c
 **Upgrade steps**
-1. [Make sure](#which-dependency-version-is-my-project-currently-using) your project is using v1 auto-deploy-image. If not, [specify the version](#use-a-specific-version-of-auto-deploy-dependencies)
+1. [Make sure](#before-starting-the-upgrade-process-you-need-to-find-out-what-dependency-version-your-project-is-using) your project is using v1 auto-deploy-image. If not, [specify the version](#use-a-specific-version-of-auto-deploy-dependencies)
 1. If you're at the middle of `canary` or `rollout` deployments, promote it to `production` at first in order to delete the unstable tracks.
-1. [Make sure](#which-dependency-version-is-my-project-currently-using) your project is using v2 auto-deploy-image. If not, [specify the version](#use-a-specific-version-of-auto-deploy-dependencies)
+1. [Make sure](#before-starting-the-upgrade-process-you-need-to-find-out-what-dependency-version-your-project-is-using) your project is using v2 auto-deploy-image. If not, [specify the version](#use-a-specific-version-of-auto-deploy-dependencies)
 1. Set `AUTO_DEVOPS_FORCE_DEPLOY_V2` environment variable with a value `true` in the GitLab CI.
 1. Create a new pipeline and execute `production` job to renew the resource architecture with v2 auto-deploy-app chart.
 1. Remove `AUTO_DEVOPS_FORCE_DEPLOY_V2` environment variable.
@@ -133,7 +133,7 @@ For more details, see the [v2 auto-deploy-app chart resource architecture](#v2-c
 ### Use a specific version of Auto Deploy dependencies
 To use a specifc version of Auto Deploy dependencies, the most recommended way is to specify
-the previous Auto Deploy stable template that [contains the desired version of `auto-deploy-image` and `auto-deploy-app` chart](#which-dependency-version-is-my-project-currently-using).
+the previous Auto Deploy stable template that [contains the desired version of `auto-deploy-image` and `auto-deploy-app` chart](#before-starting-the-upgrade-process-you-need-to-find-out-what-dependency-version-your-project-is-using).
 For example, if the template is bundled in GitLab v13.3, change your `.gitlab-ci.yml` to:

doc/topics/autodevops/upgrading_chart.md

 ---
-redirect_to: 'upgrading_auto_deploy_assets.md'
+redirect_to: 'upgrading_auto_deploy_dependencies.md'
 ---
-This document was moved to [another location](upgrading_auto_deploy_assets.md).
+This document was moved to [another location](upgrading_auto_deploy_dependencies.md).