Merge branch '7697-rename-maven-packages-feature-to-maven-repository' into 'master'

Resolve "Rename Maven packages feature to `Maven Repository`"

Closes #7697

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

doc/administration/index.md

@@ -125,7 +125,7 @@ created in snippets, wikis, and repos.
 - [Default labels](../user/admin_area/labels.html): Create labels that will be automatically added to every new project.
 - [Restrict the use of public or internal projects](../public_access/public_access.md#restricting-the-use-of-public-or-internal-projects): Restrict the use of visibility levels for users when they create a project or a snippet.
 - [Custom project templates](../user/admin_area/custom_project_templates.md): Configure a set of projects to be used as custom templates when creating a new project. **[PREMIUM ONLY]**
-- [Maven packages repository](maven_packages.md): Enable Maven packages repository within GitLab.
+- [Maven Repository](maven_repository.md): Enable Maven Repository within GitLab.
 
 ### Repository settings
 

doc/administration/maven_packages.md → doc/administration/maven_repository.md

-# GitLab Maven repository administration
+# GitLab Maven Repository administration
 
 >
 [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/issues/5811)
 in GitLab 11.3. To learn how to use
 
-When the GitLab Maven repository is enabled, every project in GitLab will have
+When the GitLab Maven Repository is enabled, every project in GitLab will have
 its own space to store [Maven](https://maven.apache.org/) packages.
 
 To learn how to use it, see the [user documentation](../user/project/packages/maven.md).
 
-## Enabling the Packages repository
+## Enabling the Maven Repository
 
 NOTE: **Note:**
 Once enabled, newly created projects will have the Packages feature enabled by
 default. Existing projects will need to
 [explicitly enabled it](../user/project/packages/maven.md#enabling-the-packages-repository).
 
-To enable the Packages repository:
+To enable the Maven repository:
 
 **Omnibus GitLab installations**
 

doc/user/project/packages/maven.md → doc/user/project/packages/maven_repository.md

-# GitLab Maven Packages repository **[PREMIUM]**
+# GitLab Maven Repository **[PREMIUM]**
 
 > Introduced in [GitLab Premium](https://about.gitlab.com/pricing/) 11.3.
 
-With the GitLab [Maven](https://maven.apache.org) Packages repository, every
+With the GitLab [Maven](https://maven.apache.org) Repository, every
 project can have its own space to store its Maven artifacts.
 
-![GitLab Maven repository](img/maven_package_view.png)
+![GitLab Maven Repository](img/maven_package_view.png)
 
-## Enabling the Packages repository
+## Enabling Maven Repository
 
 NOTE: **Note:**
 This option is available only if your GitLab administrator has
-[enabled the Packages repository](../../../administration/maven_packages.md).
+[enabled Maven Repository](../../../administration/maven_repository.md).
 
-In order to use the GitLab Maven Packages repository, you must enable the
-Packages repository. To enable (or disable) it:
+In order to use the GitLab Maven Repository, you must enable the
+Repository. To enable (or disable) it:
 
 1. Navigate to your project's **Settings > General > Permissions**.
 1. Find the "Packages" feature and enable it.
@@ -24,7 +24,7 @@ You should then be able to see the **Packages** section on the left sidebar.
 Next, you must configure your project to authorize with the GitLab Maven
 repository.
 
-## Authenticating to the GitLab Maven repository
+## Authenticating to the GitLab Maven Repository
 
 If a project is private or you want to upload Maven artifacts to GitLab,
 credentials will need to be provided for authorization. Support is available for
@@ -134,7 +134,7 @@ artifacts or even delete them.
 
 ## Creating Maven packages with GitLab CI/CD
 
-Once you have your repository configured to use the GitLab Maven Packages repository,
+Once you have your repository configured to use the GitLab Maven Repository,
 you can configure GitLab CI/CD to build new packages automatically. The example below
 shows how to create a new package each time the `master` branch is updated: