Add latest changes from gitlab-org/gitlab@master

14 files changed, 31 insertions, 31 deletions

diff --git a/doc/user/packages/composer_repository/index.md b/doc/user/packages/composer_repository/index.md
index 2aa9cd32bab..84f544ec4ad 100644
--- a/doc/user/packages/composer_repository/index.md
+++ b/doc/user/packages/composer_repository/index.md
@@ -127,7 +127,7 @@ To publish the package with a deploy token:
   - `<tag>` is the Git tag name of the version you want to publish.
      To publish a branch, use `branch=<branch>` instead of `tag=<tag>`.
 
-You can view the published package by going to **Packages & Registries > Package Registry** and
+You can view the published package by going to **Packages and registries > Package Registry** and
 selecting the **Composer** tab.
 
 ## Publish a Composer package by using CI/CD
@@ -150,7 +150,7 @@ You can publish a Composer package to the Package Registry as part of your CI/CD
 
 1. Run the pipeline.
 
-To view the published package, go to **Packages & Registries > Package Registry** and select the **Composer** tab.
+To view the published package, go to **Packages and registries > Package Registry** and select the **Composer** tab.
 
 ### Use a CI/CD template
 
diff --git a/doc/user/packages/conan_repository/index.md b/doc/user/packages/conan_repository/index.md
index 14a2d75ed46..ed106685b62 100644
--- a/doc/user/packages/conan_repository/index.md
+++ b/doc/user/packages/conan_repository/index.md
@@ -390,7 +390,7 @@ There are two ways to remove a Conan package from the GitLab Package Registry.
 
 - From the GitLab user interface:
 
-  Go to your project's **Packages & Registries > Package Registry**. Remove the
+  Go to your project's **Packages and registries > Package Registry**. Remove the
   package by selecting **Remove repository** (**{remove}**).
 
 ## Search for Conan packages in the Package Registry
diff --git a/doc/user/packages/container_registry/index.md b/doc/user/packages/container_registry/index.md
index 38b4e733c82..35853b5b737 100644
--- a/doc/user/packages/container_registry/index.md
+++ b/doc/user/packages/container_registry/index.md
@@ -26,7 +26,7 @@ Registry for your GitLab instance, visit the
 You can view the Container Registry for a project or group.
 
 1. Go to your project or group.
-1. Go to **Packages & Registries > Container Registry**.
+1. Go to **Packages and registries > Container Registry**.
 
 You can search, sort, filter, and [delete](#delete-images-from-within-gitlab)
 containers on this page. You can share a filtered view by copying the URL from your browser.
@@ -40,7 +40,7 @@ If a project is public, so is the Container Registry.
 You can view a list of tags associated with a given container image:
 
 1. Go to your project or group.
-1. Go to **Packages & Registries > Container Registry**.
+1. Go to **Packages and registries > Container Registry**.
 1. Select the container image you are interested in.
 
 This brings up the Container Registry **Tag Details** page. You can view details about each tag,
@@ -55,7 +55,7 @@ tags on this page. You can share a filtered view by copying the URL from your br
 To download and run a container image hosted in the GitLab Container Registry:
 
 1. Copy the link to your container image:
-   - Go to your project or group's **Packages & Registries > Container Registry**
+   - Go to your project or group's **Packages and registries > Container Registry**
      and find the image you want.
    - Next to the image name, select **Copy**.
 
@@ -139,7 +139,7 @@ To build and push to the Container Registry:
    docker push registry.example.com/group/project/image
    ```
 
-To view these commands, go to your project's **Packages & Registries > Container Registry**.
+To view these commands, go to your project's **Packages and registries > Container Registry**.
 
 ## Build and push by using GitLab CI/CD
 
@@ -395,7 +395,7 @@ images), are automatically scheduled for deletion after 24 hours if left unrefer
 
 To delete images from within GitLab:
 
-1. Navigate to your project's or group's **Packages & Registries > Container Registry**.
+1. Navigate to your project's or group's **Packages and registries > Container Registry**.
 1. From the **Container Registry** page, you can select what you want to delete,
    by either:
 
@@ -509,7 +509,7 @@ You can, however, remove the Container Registry for a project:
    and disable **Container Registry**.
 1. Select **Save changes**.
 
-The **Packages & Registries > Container Registry** entry is removed from the project's sidebar.
+The **Packages and registries > Container Registry** entry is removed from the project's sidebar.
 
 ## Change visibility of the Container Registry
 
diff --git a/doc/user/packages/container_registry/reduce_container_registry_storage.md b/doc/user/packages/container_registry/reduce_container_registry_storage.md
index f889f4836d9..590c5c14be4 100644
--- a/doc/user/packages/container_registry/reduce_container_registry_storage.md
+++ b/doc/user/packages/container_registry/reduce_container_registry_storage.md
@@ -113,7 +113,7 @@ You can create a cleanup policy in [the API](#use-the-cleanup-policy-api) or the
 
 To create a cleanup policy in the UI:
 
-1. For your project, go to **Settings > Packages & Registries**.
+1. For your project, go to **Settings > Packages and registries**.
 1. Expand the **Clean up image tags** section.
 1. Complete the fields.
 
diff --git a/doc/user/packages/dependency_proxy/index.md b/doc/user/packages/dependency_proxy/index.md
index b570bba73e5..f775ddac2ee 100644
--- a/doc/user/packages/dependency_proxy/index.md
+++ b/doc/user/packages/dependency_proxy/index.md
@@ -38,7 +38,7 @@ For a list of planned additions, view the
 To enable or turn off the Dependency Proxy for a group:
 
 1. On the top bar, select **Menu > Groups** and find your group.
-1. On the left sidebar, select **Settings > Packages & Registries**.
+1. On the left sidebar, select **Settings > Packages and registries**.
 1. Expand the **Dependency Proxy** section.
 1. To enable the proxy, turn on **Enable Proxy**. To turn it off, turn the toggle off.
 
@@ -51,7 +51,7 @@ for the entire GitLab instance.
 To view the Dependency Proxy:
 
 1. On the top bar, select **Menu > Groups** and find your group.
-1. On the left sidebar, select **Packages & Registries > Dependency Proxy**.
+1. On the left sidebar, select **Packages and registries > Dependency Proxy**.
 
 The Dependency Proxy is not available for projects.
 
@@ -176,7 +176,7 @@ You can also use [custom CI/CD variables](../../../ci/variables/index.md#custom-
 To store a Docker image in Dependency Proxy storage:
 
 1. On the top bar, select **Menu > Groups** and find your group.
-1. On the left sidebar, select **Packages & Registries > Dependency Proxy**.
+1. On the left sidebar, select **Packages and registries > Dependency Proxy**.
 1. Copy the **Dependency Proxy image prefix**.
 1. Use one of these commands. In these examples, the image is `alpine:latest`.
 1. You can also pull images by digest to specify exactly which version of an image to pull.
diff --git a/doc/user/packages/dependency_proxy/reduce_dependency_proxy_storage.md b/doc/user/packages/dependency_proxy/reduce_dependency_proxy_storage.md
index 839684da875..fecf60feeef 100644
--- a/doc/user/packages/dependency_proxy/reduce_dependency_proxy_storage.md
+++ b/doc/user/packages/dependency_proxy/reduce_dependency_proxy_storage.md
@@ -33,7 +33,7 @@ image or tag from Docker Hub.
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/340777) in GitLab 14.6
 
 You can enable an automatic time-to-live (TTL) policy for the Dependency Proxy from the user
-interface. To do this, navigate to your group's **Settings > Packages & Registries > Dependency Proxy**
+interface. To do this, navigate to your group's **Settings > Packages and registries > Dependency Proxy**
 and enable the setting to automatically clear items from the cache after 90 days.
 
 ### Enable cleanup policies with GraphQL
diff --git a/doc/user/packages/generic_packages/index.md b/doc/user/packages/generic_packages/index.md
index eb8cdd39517..312a2c119d6 100644
--- a/doc/user/packages/generic_packages/index.md
+++ b/doc/user/packages/generic_packages/index.md
@@ -123,7 +123,7 @@ or the UI.
 
 In the UI:
 
-1. For your group, go to **Settings > Packages & Registries**.
+1. For your group, go to **Settings > Packages and registries**.
 1. Expand the **Package Registry** section.
 1. Turn on the **Reject duplicates** toggle.
 1. Optional. To allow some duplicate packages, in the **Exceptions** box enter a regex pattern that
diff --git a/doc/user/packages/infrastructure_registry/index.md b/doc/user/packages/infrastructure_registry/index.md
index e6a179c9d12..48cc7b9dea9 100644
--- a/doc/user/packages/infrastructure_registry/index.md
+++ b/doc/user/packages/infrastructure_registry/index.md
@@ -18,7 +18,7 @@ projects.
 To view packages within your project:
 
 1. Go to the project.
-1. Go to **Packages & Registries > Infrastructure Registry**.
+1. Go to **Packages and registries > Infrastructure Registry**.
 
 You can search, sort, and filter packages on this page.
 
@@ -49,7 +49,7 @@ You can see the pipeline that published the package as well as the commit and th
 
 To download a package:
 
-1. Go to **Packages & Registries > Infrastructure Registry**.
+1. Go to **Packages and registries > Infrastructure Registry**.
 1. Select the name of the package you want to download.
 1. In the **Activity** section, select the name of the package you want to download.
 
@@ -64,7 +64,7 @@ You can delete packages by using [the API](../../../api/packages.md#delete-a-pro
 
 To delete a package in the UI, from your project:
 
-1. Go to **Packages & Registries > Infrastructure Registry**.
+1. Go to **Packages and registries > Infrastructure Registry**.
 1. Find the name of the package you want to delete.
 1. Select **Delete**.
 
@@ -75,7 +75,7 @@ The package is permanently deleted.
 The Infrastructure Registry is automatically enabled.
 
 For self-managed instances, a GitLab administrator can
-[disable](../../../administration/packages/index.md) **Packages & Registries**,
+[disable](../../../administration/packages/index.md) **Packages and registries**,
 which removes this menu item from the sidebar.
 
 You can also remove the Infrastructure Registry for a specific project:
diff --git a/doc/user/packages/maven_repository/index.md b/doc/user/packages/maven_repository/index.md
index eaa04404a1f..47fb1431981 100644
--- a/doc/user/packages/maven_repository/index.md
+++ b/doc/user/packages/maven_repository/index.md
@@ -605,7 +605,7 @@ To publish a package by using Gradle:
    gradle publish
    ```
 
-Now navigate to your project's **Packages & Registries** page and view the published artifacts.
+Now navigate to your project's **Packages and registries** page and view the published artifacts.
 
 ### Publishing a package with the same name or version
 
@@ -624,7 +624,7 @@ To prevent users from publishing duplicate Maven packages, you can use the [Grap
 
 In the UI:
 
-1. For your group, go to **Settings > Packages & Registries**.
+1. For your group, go to **Settings > Packages and registries**.
 1. Expand the **Package Registry** section.
 1. Turn on the **Reject duplicates** toggle.
 1. Optional. To allow some duplicate packages, in the **Exceptions** box, enter a regex pattern that matches the names and/or versions of packages you want to allow.
@@ -699,7 +699,7 @@ dependencies {
 
 ## Remove a package
 
-For your project, go to **Packages & Registries > Package Registry**.
+For your project, go to **Packages and registries > Package Registry**.
 
 To remove a package, select the red trash icon or, from the package details, the **Delete** button.
 
diff --git a/doc/user/packages/npm_registry/index.md b/doc/user/packages/npm_registry/index.md
index 2d3099f1c85..678f5681890 100644
--- a/doc/user/packages/npm_registry/index.md
+++ b/doc/user/packages/npm_registry/index.md
@@ -284,7 +284,7 @@ To upload an npm package to your project, run this command:
 npm publish
 ```
 
-To view the package, go to your project's **Packages & Registries**.
+To view the package, go to your project's **Packages and registries**.
 
 You can also define `"publishConfig"` for your project in `package.json`. For example:
 
diff --git a/doc/user/packages/package_registry/index.md b/doc/user/packages/package_registry/index.md
index 7748780d0e4..fe19c549536 100644
--- a/doc/user/packages/package_registry/index.md
+++ b/doc/user/packages/package_registry/index.md
@@ -26,7 +26,7 @@ Learn how to use the GitLab Package Registry to build your own custom package wo
 You can view packages for your project or group.
 
 1. Go to the project or group.
-1. Go to **Packages & Registries > Package Registry**.
+1. Go to **Packages and registries > Package Registry**.
 
 You can search, sort, and filter packages on this page. You can share your search results by copying
 and pasting the URL from your browser.
@@ -99,7 +99,7 @@ For information on reducing your storage use for the Package Registry, see
 The Package Registry is automatically enabled.
 
 If you are using a self-managed instance of GitLab, your administrator can remove
-the menu item, **Packages & Registries**, from the GitLab sidebar. For more information,
+the menu item, **Packages and registries**, from the GitLab sidebar. For more information,
 see the [administration documentation](../../../administration/packages/index.md).
 
 You can also remove the Package Registry for your project specifically:
@@ -109,7 +109,7 @@ You can also remove the Package Registry for your project specifically:
    **Packages** feature.
 1. Select **Save changes**.
 
-The **Packages & Registries > Package Registry** entry is removed from the sidebar.
+The **Packages and registries > Package Registry** entry is removed from the sidebar.
 
 ## Package Registry visibility permissions
 
diff --git a/doc/user/packages/package_registry/reduce_package_registry_storage.md b/doc/user/packages/package_registry/reduce_package_registry_storage.md
index cd7dd062f60..34b2f732c48 100644
--- a/doc/user/packages/package_registry/reduce_package_registry_storage.md
+++ b/doc/user/packages/package_registry/reduce_package_registry_storage.md
@@ -29,7 +29,7 @@ You can delete packages by using [the API](../../../api/packages.md#delete-a-pro
 
 To delete a package in the UI, from your group or project:
 
-1. Go to **Packages & Registries > Package Registry**.
+1. Go to **Packages and registries > Package Registry**.
 1. Find the name of the package you want to delete.
 1. Select **Delete**.
 
@@ -43,7 +43,7 @@ You can delete packages by using [the API](../../../api/packages.md#delete-a-pac
 
 To delete package files in the UI, from your group or project:
 
-1. Go to **Packages & Registries > Package Registry**.
+1. Go to **Packages and registries > Package Registry**.
 1. Find the name of the package you want to delete.
 1. Select the package to view additional details.
 1. Find the name of the file you would like to delete.
@@ -62,7 +62,7 @@ A cleanup policy defines a set of rules that, applied to a project, defines whic
 
 By default, the packages cleanup policy is disabled. To enable it:
 
-1. Go to your project **Settings > Packages & Registries**.
+1. Go to your project **Settings > Packages and registries**.
 1. Expand **Manage storage used by package assets**.
 1. Set the rules appropriately.
 
diff --git a/doc/user/packages/pypi_repository/index.md b/doc/user/packages/pypi_repository/index.md
index ba9ecbe50a3..302c88bf46f 100644
--- a/doc/user/packages/pypi_repository/index.md
+++ b/doc/user/packages/pypi_repository/index.md
@@ -309,7 +309,7 @@ Uploading mypypipackage-0.0.1.tar.gz
 100%|███████████████████████████████████████████████████████████████████████████████████████████| 4.24k/4.24k [00:00<00:00, 11.0kB/s]
 ```
 
-To view the published package, go to your project's **Packages & Registries**
+To view the published package, go to your project's **Packages and registries**
 page.
 
 If you didn't use a `.pypirc` file to define your repository source, you can
diff --git a/doc/user/packages/rubygems_registry/index.md b/doc/user/packages/rubygems_registry/index.md
index 05113d0bc10..682a3e2ecf1 100644
--- a/doc/user/packages/rubygems_registry/index.md
+++ b/doc/user/packages/rubygems_registry/index.md
@@ -130,7 +130,7 @@ Pushing gem to https://gitlab.example.com/api/v4/projects/1/packages/rubygems...
 {"message":"201 Created"}
 ```
 
-To view the published gem, go to your project's **Packages & Registries** page. Gems pushed to
+To view the published gem, go to your project's **Packages and registries** page. Gems pushed to
 GitLab aren't displayed in your project's Packages UI immediately. It can take up to 10 minutes to
 process a gem.