Merge branch 'docs/fix-ee-only-references-to-renamed-section' into 'master'

UI changes and renamed section required changes

See merge request gitlab-org/gitlab-ee!9324

doc/ci/chatops/README.md

@@ -24,7 +24,7 @@ Since ChatOps is built upon GitLab CI/CD, the job has all the same features and
 
 * It is strongly recommended to set `only: [chat]` so the job does not run as part of the standard CI pipeline.
 * If the job is set to `when: manual`, the pipeline will be created however the job will wait to be started.
-* It is important to keep in mind that there is very limited support for access control. If the user who triggered the slash command is a developer in the project, the job will run. The job itself can utilize existing [CI/CD variables](../variables/README.html#predefined-variables-environment-variables) like `GITLAB_USER_ID` to perform additional rights validation, however these variables can be [overridden](https://docs.gitlab.com/ce/ci/variables/README.html#priority-of-variables).
+* It is important to keep in mind that there is very limited support for access control. If the user who triggered the slash command is a developer in the project, the job will run. The job itself can utilize existing [CI/CD variables](../variables/README.html#predefined-environment-variables) like `GITLAB_USER_ID` to perform additional rights validation, however these variables can be [overridden](https://docs.gitlab.com/ce/ci/variables/README.html#priority-of-variables).
 
 ### Controlling the ChatOps reply
 

doc/ci/ci_cd_for_external_repos/bitbucket_integration.md

@@ -39,7 +39,7 @@ your Git repository via URL.
 
     ![Bitbucket Cloud webhook](img/bitbucket_app_password.png)
 
-1. In GitLab from **Settings > CI/CD > Variables** add variables to allow
+1. In GitLab from **Settings > CI/CD > Environment variables** add variables to allow
    communication with Bitbucket via the Bitbucket API.
 
     `BITBUCKET_ACCESS_TOKEN`: the Bitbucket app password created above

doc/user/project/clusters/kubernetes_pod_logs.md

@@ -24,7 +24,7 @@ There are a few key requirements in order to be able to use Pod Logs:
 1. A GitLab Runner. If one is not available, they can be easily [deployed](index.md#installing-applications).
 1. Ensure a Kubernetes label of `app: $CI_ENVIRONMENT_SLUG` is applied to the
    deployments, replica sets, and pods, where `$CI_ENVIRONMENT_SLUG` is the value
-   of the [CI variable](../../../ci/variables/README.md#predefined-variables-environment-variables).
+   of the [CI variable](../../../ci/variables/README.md#predefined-environment-variables).
    This needed to determine the environment a pod belongs to
    when is more than one. These resources should be
    contained in the namespace defined in the Kubernetes service setting.

doc/user/project/packages/maven_repository.md

@@ -337,4 +337,4 @@ shows how to create a new package each time the `master` branch is updated:
 The next time the `deploy` job runs, it will copy `ci_settings.xml` to the
 user's home location (in this case the user is `root` since it runs in a
 Docker container), and Maven will utilize the configured CI
-[environment variables](../../../ci/variables/README.md#predefined-variables-environment-variables).
+[environment variables](../../../ci/variables/README.md#predefined-environment-variables).