Add latest changes from gitlab-org/gitlab@master

39 files changed, 145 insertions, 98 deletions

diff --git a/doc/administration/gitaly/index.md b/doc/administration/gitaly/index.md
index b1c54041b22..c7f7c4c58a5 100644
--- a/doc/administration/gitaly/index.md
+++ b/doc/administration/gitaly/index.md
@@ -597,7 +597,7 @@ To migrate to Gitaly Cluster:
 
 1. Create the required storage. Refer to
    [repository storage recommendations](praefect.md#repository-storage-recommendations).
-1. Create and configure [Gitaly Cluster](praefect.md). 
+1. Create and configure [Gitaly Cluster](praefect.md).
 1. Configure the existing Gitaly instance [to use TPC](praefect.md#use-tcp-for-existing-gitlab-instances), if not already configured that way.
 1. [Move the repositories](../operations/moving_repositories.md#move-repositories). To migrate to
    Gitaly Cluster, existing repositories stored outside Gitaly Cluster must be moved. There is no
diff --git a/doc/administration/pages/index.md b/doc/administration/pages/index.md
index 9d095bdac22..024fb12a51f 100644
--- a/doc/administration/pages/index.md
+++ b/doc/administration/pages/index.md
@@ -1521,3 +1521,12 @@ To fix that:
    - Store your deployments locally, by commenting out that line.
 
 1. Save the changes you made to your `gitlab.rb` file, then [reconfigure GitLab](../restart_gitlab.md#omnibus-gitlab-reconfigure).
+
+### 404 error `The page you're looking for could not be found`
+
+If you get a `404 Page Not Found` response from GitLab Pages:
+
+1. Check `.gitlab-ci.yml` contains the job `pages:`.
+1. Check the current project's pipeline to confirm the job `pages:deploy` is being run.
+
+Without the `pages:deploy` job, the updates to your GitLab Pages site are never published.
diff --git a/doc/api/graphql/reference/index.md b/doc/api/graphql/reference/index.md
index e8f8b0cf16b..708c05f9e69 100644
--- a/doc/api/graphql/reference/index.md
+++ b/doc/api/graphql/reference/index.md
@@ -16486,6 +16486,18 @@ four standard [pagination arguments](#connection-pagination-arguments):
 | <a id="projectiterationstimeframe"></a>`timeframe` | [`Timeframe`](#timeframe) | List items overlapping the given timeframe. |
 | <a id="projectiterationstitle"></a>`title` **{warning-solid}** | [`String`](#string) | **Deprecated** in 15.4. The argument will be removed in 15.4. Please use `search` and `in` fields instead. |
 
+##### `Project.job`
+
+One job belonging to the project, selected by ID.
+
+Returns [`CiJob`](#cijob).
+
+###### Arguments
+
+| Name | Type | Description |
+| ---- | ---- | ----------- |
+| <a id="projectjobid"></a>`id` | [`JobID!`](#jobid) | ID of the job. |
+
 ##### `Project.jobs`
 
 Jobs of a project. This field can only be resolved for one project in any single request.
diff --git a/doc/architecture/blueprints/pods/index.md b/doc/architecture/blueprints/pods/index.md
index 0deeefa6d5c..fc33a4f441b 100644
--- a/doc/architecture/blueprints/pods/index.md
+++ b/doc/architecture/blueprints/pods/index.md
@@ -54,7 +54,7 @@ A top-level namespace is the logical object container in the code that represent
 
 A top-level namespace is the root of nested collection namespaces and projects. The namespace and its related entities form a tree-like hierarchy: Namespaces are the nodes of the tree, projects are the leaves. An organization usually contains a single top-level namespace, called a workspace.
 
-Example: 
+Example:
 
 `https://gitlab.com/gitlab-org/gitlab/`:
 
@@ -117,7 +117,7 @@ A number of technical issues need to be resolved to implement Pods (in no partic
 
 ## Iteration 1
 
-Ultimately, a Pods architecture should offer the same user experience as self-managed and GitLab dedicated. However, at this moment GitLab.com has many more "social-network"-like capabilities that will be difficult to implement with a Pods architecture. We should evaluate if the SMB and mid market segment is interested in these features, or if not having them is acceptable in most cases. 
+Ultimately, a Pods architecture should offer the same user experience as self-managed and GitLab dedicated. However, at this moment GitLab.com has many more "social-network"-like capabilities that will be difficult to implement with a Pods architecture. We should evaluate if the SMB and mid market segment is interested in these features, or if not having them is acceptable in most cases.
 
 The first iteration of Pods will still contain some limitations that would break cross-workspace workflows. This means it may only be acceptable for new customers, or for existing customers that are briefed.
 
diff --git a/doc/ci/ci_cd_for_external_repos/bitbucket_integration.md b/doc/ci/ci_cd_for_external_repos/bitbucket_integration.md
index c536ff59b84..cfe7be064fb 100644
--- a/doc/ci/ci_cd_for_external_repos/bitbucket_integration.md
+++ b/doc/ci/ci_cd_for_external_repos/bitbucket_integration.md
@@ -15,7 +15,8 @@ GitLab CI/CD can be used with Bitbucket Cloud by:
 To use GitLab CI/CD with a Bitbucket Cloud repository:
 
 1. In GitLab, create a project:
-   1. On the top menu, select **Projects > Create new project**.
+   1. In GitLab, on the top bar, select **Main menu > Projects > View all projects**.
+   1. On the right of the page, select **New project**.
    1. Select **Run CI/CD for external repository**.
    1. Select **Repository by URL**.
    1. Fill in the fields with information from the repository in Bitbucket:
diff --git a/doc/ci/ci_cd_for_external_repos/github_integration.md b/doc/ci/ci_cd_for_external_repos/github_integration.md
index a928d315c6b..a48822fc214 100644
--- a/doc/ci/ci_cd_for_external_repos/github_integration.md
+++ b/doc/ci/ci_cd_for_external_repos/github_integration.md
@@ -34,7 +34,8 @@ repositories:
       `repo` and `admin:repo_hook` so that GitLab can access your project,
       update commit statuses, and create a web hook to notify GitLab of new commits.
 1. In GitLab, create a project:
-   1. On the top menu, select **Projects > Create new project**.
+   1. In GitLab, on the top bar, select **Main menu > Projects > View all projects**.
+   1. On the right of the page, select **New project**.
    1. Select **Run CI/CD for external repository**.
    1. Select **GitHub**.
    1. For **Personal access token**, paste the token.
@@ -61,7 +62,8 @@ To manually enable GitLab CI/CD for your repository:
    1. Enter a **Token description** and update the scope to allow
       `repo` so that GitLab can access your project and update commit statuses.
 1. In GitLab, create a project:
-   1. On the top menu, select **Projects > Create new project**.
+   1. In GitLab, on the top bar, select **Main menu > Projects > View all projects**.
+   1. On the right of the page, select **New project**.
    1. Select **Run CI/CD for external repository** and **Repository by URL**.
    1. In the **Git repository URL** field, enter the HTTPS URL for your GitHub repository.
       If your project is private, use the personal access token you just created for authentication.
diff --git a/doc/ci/ci_cd_for_external_repos/index.md b/doc/ci/ci_cd_for_external_repos/index.md
index 00685df049d..7c0889a329a 100644
--- a/doc/ci/ci_cd_for_external_repos/index.md
+++ b/doc/ci/ci_cd_for_external_repos/index.md
@@ -24,7 +24,8 @@ snippets disabled. These features
 
 To connect to an external repository:
 
-1. On the top bar, select **Main menu > Projects > Create new project**.
+1. In GitLab, on the top bar, select **Main menu > Projects > View all projects**.
+1. On the right of the page, select **New project**.
 1. Select **Run CI/CD for external repository**.
 1. Select **GitHub** or **Repository by URL**.
 1. Complete the fields.
diff --git a/doc/development/code_review.md b/doc/development/code_review.md
index 79146e0b8bc..c320540401f 100644
--- a/doc/development/code_review.md
+++ b/doc/development/code_review.md
@@ -148,7 +148,7 @@ with [domain expertise](#domain-experts).
 | `~frontend` changes (*1*)       | [Frontend maintainer](https://about.gitlab.com/handbook/engineering/projects/#gitlab_maintainers_frontend). |
 | `~UX` user-facing changes (*3*) | [Product Designer](https://about.gitlab.com/handbook/engineering/projects/#gitlab_reviewers_UX). Refer to the [design and user interface guidelines](contributing/design.md) for details. |
 | Adding a new JavaScript library (*1*) | - [Frontend foundations member](https://about.gitlab.com/direction/ecosystem/foundations/) if the library significantly increases the [bundle size](https://gitlab.com/gitlab-org/frontend/playground/webpack-memory-metrics/-/blob/master/doc/report.md).<br/>- A [legal department member](https://about.gitlab.com/handbook/legal/) if the license used by the new library hasn't been approved for use in GitLab.<br/><br/>More information about license compatibility can be found in our [GitLab Licensing and Compatibility documentation](licensing.md). |
-| A new dependency or a file system change | [Distribution team member](https://about.gitlab.com/company/team/). See how to work with the [Distribution team](https://about.gitlab.com/handbook/engineering/development/enablement/systems/distribution/#how-to-work-with-distribution) for more details. |
+| A new dependency or a file system change | - [Distribution team member](https://about.gitlab.com/company/team/). See how to work with the [Distribution team](https://about.gitlab.com/handbook/engineering/development/enablement/systems/distribution/#how-to-work-with-distribution) for more details.<br/>- For Rubygems, request an [AppSec review](gemfile.md#request-an-appsec-review). |
 | `~documentation` changes | [Technical writer](https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments) based on assignments in the appropriate [DevOps stage group](https://about.gitlab.com/handbook/product/categories/#devops-stages). |
 | Changes to development guidelines | Follow the [review process](development_processes.md#development-guidelines-review) and get the approvals accordingly. |
 | End-to-end **and** non-end-to-end changes (*4*) | [Software Engineer in Test](https://about.gitlab.com/handbook/engineering/quality/#individual-contributors). |
diff --git a/doc/development/documentation/index.md b/doc/development/documentation/index.md
index f8deca1af1a..f4e74973fd7 100644
--- a/doc/development/documentation/index.md
+++ b/doc/development/documentation/index.md
@@ -42,7 +42,7 @@ run only the jobs that match the type of contribution. If your contribution cont
 **only** documentation changes, then only documentation-related jobs run, and
 the pipeline completes much faster than a code contribution.
 
-If you are submitting documentation-only changes to Omnibus, Charts, or Operator, 
+If you are submitting documentation-only changes to Omnibus, Charts, or Operator,
 the fast pipeline is not determined automatically. Instead, create branches for
 docs-only merge requests using the following guide:
 
diff --git a/doc/development/fe_guide/index.md b/doc/development/fe_guide/index.md
index 5c58df19534..d90c270153e 100644
--- a/doc/development/fe_guide/index.md
+++ b/doc/development/fe_guide/index.md
@@ -36,7 +36,7 @@ Sign in to BrowserStack with the credentials saved in the **Engineering** vault
 
 ## Initiatives
 
-You can find current frontend initiatives with a cross-functional impact on epics 
+You can find current frontend initiatives with a cross-functional impact on epics
 with the label [frontend-initiative](https://gitlab.com/groups/gitlab-org/-/epics?state=opened&page=1&sort=UPDATED_AT_DESC&label_name[]=frontend-initiative).
 
 ## Principles
diff --git a/doc/development/gemfile.md b/doc/development/gemfile.md
index d993604ab7d..7383616af7d 100644
--- a/doc/development/gemfile.md
+++ b/doc/development/gemfile.md
@@ -15,6 +15,23 @@ We do not allow gems that are fetched from Git repositories. All gems have
 to be available in the RubyGems index. We want to minimize external build
 dependencies and build times.
 
+## Request an Appsec review
+
+When adding a new gem to our `Gemfile` or even changing versions in
+`Gemfile.lock` it is strongly recommended that you
+[request a Security review](https://about.gitlab.com/handbook/engineering/security/#how-to-request-a-security-review).
+New gems add an extra security risk for GitLab, and it is important to
+evaluate this risk before we ship this to production. Technically, just adding
+a new gem and pushing to a branch in our main `gitlab` project is a security
+risk as it will run in CI using your GitLab.com credentials. As such you should
+evaluate early on if you think this gem seems legitimate before you even
+install it.
+
+Reviewers should also be aware of our related
+[recommendations for reviewing community contributions](code_review.md#community-contributions)
+and take care before running a pipeline for community contributions that
+contains changes to `Gemfile` or `Gemfile.lock`.
+
 ## License compliance
 
 Refer to [licensing guidelines](licensing.md) for ensuring license compliance.
diff --git a/doc/development/testing_guide/end_to_end/feature_flags.md b/doc/development/testing_guide/end_to_end/feature_flags.md
index 9b72148b614..9a39161f1ad 100644
--- a/doc/development/testing_guide/end_to_end/feature_flags.md
+++ b/doc/development/testing_guide/end_to_end/feature_flags.md
@@ -195,7 +195,7 @@ End-to-end tests should pass with a feature flag enabled before it is enabled on
 There are two ways to confirm that end-to-end tests pass:
 
 - If a merge request adds or edits a [feature flag definition file](../../feature_flags/index.md#feature-flag-definition-and-validation),
-  two `e2e:package-and-test` jobs (`ee:instance-parallel` and `ee:instance-parallel-ff-inverse`) are included automatically in the merge request pipeline. 
+  two `e2e:package-and-test` jobs (`ee:instance-parallel` and `ee:instance-parallel-ff-inverse`) are included automatically in the merge request pipeline.
   One job runs the application with default feature flag state and another sets it to inverse value. The jobs execute the same suite of tests to confirm that they pass with the feature flag either enabled or disabled.
 - In some cases, if end-to-end test jobs didn't trigger automatically, or if it has run the tests with the default feature flag values (which might not be desired),
   you can create a Draft MR that enables the feature flag to ensure that all E2E tests pass with the feature flag enabled and disabled.
diff --git a/doc/development/testing_guide/end_to_end/index.md b/doc/development/testing_guide/end_to_end/index.md
index 40d610cfffc..cc9c02a65ce 100644
--- a/doc/development/testing_guide/end_to_end/index.md
+++ b/doc/development/testing_guide/end_to_end/index.md
@@ -15,7 +15,7 @@ together.
 
 ## How do we test GitLab?
 
-We use [Omnibus GitLab](https://gitlab.com/gitlab-org/omnibus-gitlab) to build GitLab packages and then we test these packages 
+We use [Omnibus GitLab](https://gitlab.com/gitlab-org/omnibus-gitlab) to build GitLab packages and then we test these packages
 using the [GitLab QA orchestrator](https://gitlab.com/gitlab-org/gitlab-qa) tool to run the end-to-end tests located in the `qa` directory.
 
 ### Testing nightly builds
diff --git a/doc/development/value_stream_analytics.md b/doc/development/value_stream_analytics.md
index a6cde553325..bbea89d5645 100644
--- a/doc/development/value_stream_analytics.md
+++ b/doc/development/value_stream_analytics.md
@@ -286,7 +286,7 @@ The group VSA Vuex store makes use of [Vuex modules](https://vuex.vuejs.org/guid
 
 ### Shared components
 
-Parts of the UI are shared between project VSA and group VSA such as the stage table and path. These shared components live in the project VSA directory `app/assets/javascripts/cycle_analytics/components` and are included at the group level VSA where needed. 
+Parts of the UI are shared between project VSA and group VSA such as the stage table and path. These shared components live in the project VSA directory `app/assets/javascripts/cycle_analytics/components` and are included at the group level VSA where needed.
 
 All the frontend code for group-level features are located in `ee/app/assets/javascripts/analytics/cycle_analytics/components`.
 
diff --git a/doc/integration/kerberos.md b/doc/integration/kerberos.md
index cff29189464..49c5828ae32 100644
--- a/doc/integration/kerberos.md
+++ b/doc/integration/kerberos.md
@@ -372,8 +372,8 @@ There are a number of potential causes and solutions for this error message.
 
 #### Kerberos integration not using a dedicated port
 
-GitLab CI/CD doesn’t work with a Kerberos-enabled GitLab instance unless the Kerberos integration 
-is configured to [use a dedicated port](kerberos.md#http-git-access-with-kerberos-token-passwordless-authentication). 
+GitLab CI/CD doesn’t work with a Kerberos-enabled GitLab instance unless the Kerberos integration
+is configured to [use a dedicated port](kerberos.md#http-git-access-with-kerberos-token-passwordless-authentication).
 
 #### Lack of connectivity between client machine and Kerberos server
 
diff --git a/doc/policy/maintenance.md b/doc/policy/maintenance.md
index 58cf333bb2d..02a1c5a53dc 100644
--- a/doc/policy/maintenance.md
+++ b/doc/policy/maintenance.md
@@ -139,7 +139,7 @@ For very serious security issues, there is
 to backport security fixes to even more monthly releases of GitLab.
 This decision is made on a case-by-case basis.
 
-In some circumstances we may choose to address a vulnerability using the [patch release](#patch-releases) process or the regular monthly release process, that is, updating the current stable release only, with no backports. Factors influencing this decision include very low likelihood of exploitation, low impact, fix complexity and risk to stability. We will **always address 
+In some circumstances we may choose to address a vulnerability using the [patch release](#patch-releases) process or the regular monthly release process, that is, updating the current stable release only, with no backports. Factors influencing this decision include very low likelihood of exploitation, low impact, fix complexity and risk to stability. We will **always address
 high and critical** security issues with a security release.
 
 ## More information
diff --git a/doc/raketasks/backup_gitlab.md b/doc/raketasks/backup_gitlab.md
index 9e3e49a60b8..8d72195e43a 100644
--- a/doc/raketasks/backup_gitlab.md
+++ b/doc/raketasks/backup_gitlab.md
@@ -36,7 +36,7 @@ The backup command requires [additional parameters](backup_restore.md#back-up-an
 your installation is using PgBouncer, for either performance reasons or when using it with a Patroni cluster.
 
 WARNING:
-The backup command doesn't verify if another backup is already running, as described in 
+The backup command doesn't verify if another backup is already running, as described in
 [issue 362593](https://gitlab.com/gitlab-org/gitlab/-/issues/362593). We strongly recommend
 you make sure that all backups are complete before starting a new one.
 
diff --git a/doc/security/token_overview.md b/doc/security/token_overview.md
index b49e42b5860..e585f2caeca 100644
--- a/doc/security/token_overview.md
+++ b/doc/security/token_overview.md
@@ -136,4 +136,4 @@ This table shows available scopes per token. Scopes can be limited further on to
 - Be careful not to include tokens when pasting code, console commands, or log outputs into an issue or MR description or comment.
 - Don’t log credentials in the console logs. Consider [protecting](../ci/variables/index.md#protected-cicd-variables) and
   [masking](../ci/variables/index.md#mask-a-cicd-variable) your credentials.
-- Review all currently active access tokens of all types on a regular basis and revoke any that are no longer needed. 
+- Review all currently active access tokens of all types on a regular basis and revoke any that are no longer needed.
diff --git a/doc/tutorials/move_personal_project_to_a_group.md b/doc/tutorials/move_personal_project_to_a_group.md
index dce685bff98..49ce09a2ed4 100644
--- a/doc/tutorials/move_personal_project_to_a_group.md
+++ b/doc/tutorials/move_personal_project_to_a_group.md
@@ -64,7 +64,7 @@ Before you move your project to a group:
 
 Now you're ready to move your project:
 
-1. On the top bar, select **Main menu > Projects > View all projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Settings > General**.
 1. Expand **Advanced**.
 1. Under **Transfer project**, choose the group to transfer the project to.
@@ -85,7 +85,7 @@ your related resources and tools, such as websites and package managers.
 
 You can now view your project in your group:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. Look for your project under **Subgroups and projects**.
 
 Start enjoying the benefits of a group! For example, as the group Owner, you can
diff --git a/doc/user/admin_area/settings/continuous_integration.md b/doc/user/admin_area/settings/continuous_integration.md
index 1e4f5529c7b..9e711b8f5e2 100644
--- a/doc/user/admin_area/settings/continuous_integration.md
+++ b/doc/user/admin_area/settings/continuous_integration.md
@@ -70,7 +70,7 @@ runner settings:
 
 To view the rendered details:
 
-1. On the top bar, select **Main menu > Project** and select any group or project.
+1. On the top bar, select **Main menu > Projects** or **Main menu > Groups** and find your project or group.
 1. On the left sidebar, select **Settings > CI/CD**.
 1. Expand **Runners**.
 
diff --git a/doc/user/application_security/get-started-security.md b/doc/user/application_security/get-started-security.md
index f66530314b6..ee7864b5ce9 100644
--- a/doc/user/application_security/get-started-security.md
+++ b/doc/user/application_security/get-started-security.md
@@ -18,7 +18,7 @@ The following steps will help you get the most from GitLab application security
    feature branch scans to be compared against. This allows [merge requests](../project/merge_requests/index.md)
    to display only newly-introduced vulnerabilities. Otherwise, merge requests will display every
    vulnerability in the branch, regardless of whether it was introduced by a change in the branch.
-   - If you are after simplicity, enable only Secret Detection first. It only has one analyzer, 
+   - If you are after simplicity, enable only Secret Detection first. It only has one analyzer,
    no build requirements, and relatively simple findings: is this a secret or not?
    - It is good practice to enable Dependency Scanning early so you can start identifying existing
    vulnerable packages in your codebase.
diff --git a/doc/user/application_security/security_dashboard/index.md b/doc/user/application_security/security_dashboard/index.md
index 1cf605c16bb..967e8da58a9 100644
--- a/doc/user/application_security/security_dashboard/index.md
+++ b/doc/user/application_security/security_dashboard/index.md
@@ -49,7 +49,7 @@ To reduce false negatives in [dependency scans](../../../user/application_securi
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/285477) in GitLab 13.11, date range slider to visualize data between given dates.
 
 The project Security Dashboard shows the total number of vulnerabilities
-over time, with up to 365 days of historical data. Data refresh begins daily at 01:15 UTC via a scheduled job. 
+over time, with up to 365 days of historical data. Data refresh begins daily at 01:15 UTC via a scheduled job.
 Each refresh captures a snapshot of open vulnerabilities. Data is not backported to prior days
 so vulnerabilities opened after the job has already run for the day will not be reflected in the
 counts until the following day's refresh job.
@@ -99,7 +99,7 @@ To view project security status for a group:
 1. Select **Security > Security Dashboard**.
 
 Each project is assigned a letter [grade](#project-vulnerability-grades) according to the highest-severity open vulnerability.
-Dismissed or resolved vulnerabilities are excluded. Each project can receive only one letter grade and will appear only once 
+Dismissed or resolved vulnerabilities are excluded. Each project can receive only one letter grade and will appear only once
 in the Project security status report.
 
 To view vulnerabilities, go to the group's [vulnerability report](../vulnerability_report/index.md).
diff --git a/doc/user/clusters/management_project_template.md b/doc/user/clusters/management_project_template.md
index 18f1729ae63..cd71be321cc 100644
--- a/doc/user/clusters/management_project_template.md
+++ b/doc/user/clusters/management_project_template.md
@@ -45,7 +45,8 @@ If you have already configured the agent and connected a cluster with GitLab:
 
 To create a project from the cluster management project template:
 
-1. On the top bar, select **Main menu > Projects > Create new project**.
+1. In GitLab, on the top bar, select **Main menu > Projects > View all projects**.
+1. On the right of the page, select **New project**.
 1. Select **Create from template**.
 1. From the list of templates, next to **GitLab Cluster Management**, select **Use template**.
 1. Enter the project details.
diff --git a/doc/user/group/access_and_permissions.md b/doc/user/group/access_and_permissions.md
index 949587209d6..bdef13af3f9 100644
--- a/doc/user/group/access_and_permissions.md
+++ b/doc/user/group/access_and_permissions.md
@@ -50,7 +50,7 @@ configured by an administrator.
 
 To change the permitted Git access protocols for a group:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Settings > General**.
 1. Expand the **Permissions and group features** section.
 1. Choose the permitted protocols from **Enabled Git access protocols**.
@@ -91,7 +91,7 @@ You should consider some security implications before configuring IP address res
 
 To restrict group access by IP address:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Settings > General**.
 1. Expand the **Permissions and group features** section.
 1. In the **Restrict access by IP address** field, enter IPv4 or IPv6 address ranges in CIDR notation.
@@ -111,7 +111,7 @@ You can prevent users with email addresses in specific domains from being added
 
 To restrict group access by domain:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Settings > General**.
 1. Expand the **Permissions and group features** section.
 1. In the **Restrict membership by email** field, enter the domain names.
@@ -155,7 +155,7 @@ If you prevent group sharing outside the hierarchy for the **Animals** group:
 
 To prevent sharing outside of the group's hierarchy:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Settings > General**.
 1. Expand **Permissions and group features**.
 1. Select **Members cannot invite groups outside of `<group_name>` and its subgroups**.
@@ -169,7 +169,7 @@ to enable tighter control over project access.
 
 To prevent a project from being shared with other groups:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Settings > General**.
 1. Expand the **Permissions and group features** section.
 1. Select **Projects in `<group_name>` cannot be shared with other groups**.
@@ -183,7 +183,7 @@ added to a project lose access when the setting is enabled.
 As a group owner, you can prevent non-members from requesting access to
 your group.
 
-1. On the top bar, **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, **Main menu > Groups** and find your group.
 1. Select **Your Groups**.
 1. Find the group and select it.
 1. From the left menu, select **Settings > General**.
@@ -205,7 +205,7 @@ If even one is set to `true`, then the group does not allow outside forks.
 
 To prevent projects from being forked outside the group:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Settings > General**.
 1. Expand the **Permissions and group features** section.
 1. Check **Prevent project forking outside current group**.
@@ -227,7 +227,7 @@ The setting does not cascade. Projects in subgroups observe the subgroup configu
 
 To prevent members from being added to projects in a group:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Settings > General**.
 1. Under **Membership**, select **Users cannot be added to projects in this group**.
 1. Select **Save changes**.
@@ -274,7 +274,7 @@ To create group links via filter:
 
 LDAP user permissions can be manually overridden by an administrator. To override a user's permissions:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Group information > Members**.
 1. In the row for the user you are editing, select the pencil (**{pencil}**) icon.
 1. Select **Edit permissions** in the modal.
diff --git a/doc/user/group/manage.md b/doc/user/group/manage.md
index d55d410acea..ca9ff0d7b3e 100644
--- a/doc/user/group/manage.md
+++ b/doc/user/group/manage.md
@@ -44,7 +44,7 @@ For details about groups, watch [GitLab Namespaces (users, groups and subgroups)
 
 To remove a group and its contents:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Settings > General**.
 1. Expand the **Advanced** section.
 1. In the **Remove group** section, select **Remove group**.
@@ -82,7 +82,7 @@ Prerequisites:
 
 To immediately remove a group marked for deletion:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Settings > General**.
 1. Expand **Advanced**.
 1. In the "Permanently remove group" section, select **Remove group**.
@@ -97,7 +97,7 @@ are deleted.
 
 To restore a group that is marked for deletion:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. Select **Settings > General**.
 1. Expand the **Path, transfer, remove** section.
 1. In the Restore group section, select **Restore group**.
@@ -106,7 +106,7 @@ To restore a group that is marked for deletion:
 
 As a user, you can request to be a member of a group, if an administrator allows it.
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. Under the group name, select **Request Access**.
 
 As many as ten of the most-recently-active group owners receive an email with your request.
@@ -127,7 +127,7 @@ To find members in a group, you can sort, filter, or search.
 
 Filter a group to find members. By default, all members in the group and subgroups are displayed.
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. Above the list of members, in the **Filter members** box, enter filter criteria.
    - To view members in the group only, select **Membership = Direct**.
    - To view members of the group and its subgroups, select **Membership = Inherited**.
@@ -138,7 +138,7 @@ Filter a group to find members. By default, all members in the group and subgrou
 
 You can search for members by name, username, or email.
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Group information > Members**.
 1. Above the list of members, in the **Filter members** box, enter search criteria.
 1. To the right of the **Filter members** box, select the magnifying glass (**{search}**).
@@ -147,7 +147,7 @@ You can search for members by name, username, or email.
 
 You can sort members by **Account**, **Access granted**, **Max role**, or **Last sign-in**.
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Group information > Members**.
 1. Above the list of members, on the top right, from the **Account** list, select
    the criteria to filter by.
@@ -158,7 +158,7 @@ You can sort members by **Account**, **Access granted**, **Max role**, or **Last
 
 You can give a user access to all projects in a group.
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Group information > Members**.
 1. Select **Invite members**.
 1. Fill in the fields.
@@ -184,7 +184,7 @@ Prerequisites:
 
 To remove a member from a group:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Group information > Members**.
 1. Next to the member you want to remove, select **Remove member**.
 1. Optional. On the **Remove member** confirmation box:
@@ -226,12 +226,12 @@ You can change the owner of a group. Each group must always have at least one
 member with the Owner role.
 
 - As an administrator:
-  1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+  1. On the top bar, select **Main menu > Groups** and find your group.
   1. On the left sidebar, select **Group information > Members**.
   1. Give a different member the **Owner** role.
   1. Refresh the page. You can now remove the **Owner** role from the original owner.
 - As the current group's owner:
-  1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+  1. On the top bar, select **Main menu > Groups** and find your group.
   1. On the left sidebar, select **Group information > Members**.
   1. Give a different member the **Owner** role.
   1. Have the new owner sign in and remove the **Owner** role from you.
@@ -251,7 +251,7 @@ create a new group and transfer projects to it instead.
 
 To change your group path (group URL):
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Settings > General** page.
 1. Expand the **Advanced** section.
 1. Under **Change group URL**, enter a new name.
@@ -332,7 +332,7 @@ When transferring groups, note:
 
 To transfer a group:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Settings > General**.
 1. Expand the **Advanced** section.
 1. In the **Remove group** section, select **Transfer group**.
@@ -362,7 +362,7 @@ the default setting.
 
 To enable delayed deletion of projects in a group:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Settings > General**.
 1. Expand the **Permissions and group features** section.
 1. Scroll to:
@@ -384,7 +384,7 @@ You can disable all email notifications related to the group, which includes its
 
 To disable email notifications:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Settings > General**.
 1. Expand the **Permissions and group features** section.
 1. Select **Email notifications are disabled**.
@@ -404,7 +404,7 @@ This is particularly helpful for groups with a large number of users.
 
 To disable group mentions:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Settings > General**.
 1. Expand the **Permissions and group features** section.
 1. Select **Group mentions are disabled**.
@@ -417,7 +417,7 @@ To disable group mentions:
 
 You can export a list of members in a group or subgroup as a CSV.
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group or subgroup.
+1. On the top bar, select **Main menu > Groups** and find your group or subgroup.
 1. On the left sidebar, select either **Group information > Members** or **Subgroup information > Members**.
 1. Select **Export as CSV**.
 1. After the CSV file has been generated, it is emailed as an attachment to the user that requested it.
@@ -444,7 +444,7 @@ Prerequisite:
 
 To specify a user cap:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
    You can set a cap on the top-level group only.
 1. On the left sidebar, select **Settings > General**.
 1. Expand **Permissions and group features**.
@@ -466,7 +466,7 @@ Prerequisite:
 
 To remove the user cap:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Settings > General**.
 1. Expand **Permissions and group features**.
 1. In the **User cap** box, delete the value.
@@ -487,7 +487,7 @@ Prerequisite:
 
 To approve members that are pending because they've exceeded the user cap:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Settings > Usage Quotas**.
 1. On the **Seats** tab, under the alert, select **View pending approvals**.
 1. For each member you want to approve, select **Approve**.
@@ -518,7 +518,7 @@ Define project templates at a group level by setting a group as the template sou
 
 To enable group file templates:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Settings > General**.
 1. Expand the **Templates** section.
 1. Choose a project to act as the template repository.
@@ -536,7 +536,7 @@ that belong to the group.
 
 To view the merge request approval settings for a group:
 
-1. On the top bar, select **Main menu > Groups > View all groups** and find your group.
+1. On the top bar, select **Main menu > Groups** and find your group.
 1. On the left sidebar, select **Settings > General**.
 1. Expand the **Merge request approvals** section.
 1. Select the settings you want.
diff --git a/doc/user/infrastructure/clusters/connect/new_civo_cluster.md b/doc/user/infrastructure/clusters/connect/new_civo_cluster.md
index 955701636bf..f9feef6329c 100644
--- a/doc/user/infrastructure/clusters/connect/new_civo_cluster.md
+++ b/doc/user/infrastructure/clusters/connect/new_civo_cluster.md
@@ -35,7 +35,8 @@ Start by [importing the example project by URL](../../../project/import/repo_by_
 
 To import the project:
 
-1. On the top bar, select **Main menu > Create new project**.
+1. In GitLab, on the top bar, select **Main menu > Projects > View all projects**.
+1. On the right of the page, select **New project**.
 1. Select **Import project**.
 1. Select **Repository by URL**.
 1. For the **Git repository URL**, enter `https://gitlab.com/civocloud/gitlab-terraform-civo.git`.
diff --git a/doc/user/infrastructure/clusters/connect/new_eks_cluster.md b/doc/user/infrastructure/clusters/connect/new_eks_cluster.md
index f6d15e6da24..126968baee7 100644
--- a/doc/user/infrastructure/clusters/connect/new_eks_cluster.md
+++ b/doc/user/infrastructure/clusters/connect/new_eks_cluster.md
@@ -34,7 +34,8 @@ Start by [importing the example project by URL](../../../project/import/repo_by_
 
 To import the project:
 
-1. On the top bar, select **Main menu > Create new project**.
+1. In GitLab, on the top bar, select **Main menu > Projects > View all projects**.
+1. On the right of the page, select **New project**.
 1. Select **Import project**.
 1. Select **Repository by URL**.
 1. For the **Git repository URL**, enter `https://gitlab.com/gitlab-org/configure/examples/gitlab-terraform-eks.git`.
diff --git a/doc/user/infrastructure/clusters/connect/new_gke_cluster.md b/doc/user/infrastructure/clusters/connect/new_gke_cluster.md
index 5cdc8e7bf90..a23a9e7a6e5 100644
--- a/doc/user/infrastructure/clusters/connect/new_gke_cluster.md
+++ b/doc/user/infrastructure/clusters/connect/new_gke_cluster.md
@@ -41,7 +41,8 @@ Start by [importing the example project by URL](../../../project/import/repo_by_
 
 To import the project:
 
-1. On the top bar, select **Main menu > Create new project**.
+1. In GitLab, on the top bar, select **Main menu > Projects > View all projects**.
+1. On the right of the page, select **New project**.
 1. Select **Import project**.
 1. Select **Repository by URL**.
 1. For the **Git repository URL**, enter `https://gitlab.com/gitlab-org/configure/examples/gitlab-terraform-gke.git`.
diff --git a/doc/user/namespace/index.md b/doc/user/namespace/index.md
index 172be7873a7..683c9b7d31b 100644
--- a/doc/user/namespace/index.md
+++ b/doc/user/namespace/index.md
@@ -6,13 +6,13 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # Namespaces
 
-In GitLab, a *namespace* provides one place to organize your related projects. Projects in one namespace are separate from projects in other namespaces, 
+In GitLab, a *namespace* provides one place to organize your related projects. Projects in one namespace are separate from projects in other namespaces,
 which means you can use the same name for projects in different namespaces.
 
 GitLab has two types of namespaces:
 
 - A *Personal* namespace, which is based on your username and provided to you when you create your account.
-  - If you change your username, the project and namespace URLs in your account also change. Before you change your username, 
+  - If you change your username, the project and namespace URLs in your account also change. Before you change your username,
     read about [repository redirects](../project/repository/index.md#what-happens-when-a-repository-path-changes).
   - You cannot create subgroups in a personal namespace.
   - Groups in your namespace do not inherit your namespace permissions and group features.
diff --git a/doc/user/packages/maven_repository/index.md b/doc/user/packages/maven_repository/index.md
index 47fb1431981..eae0c886013 100644
--- a/doc/user/packages/maven_repository/index.md
+++ b/doc/user/packages/maven_repository/index.md
@@ -670,14 +670,20 @@ Downloading from gitlab-maven: http://gitlab.example.com/api/v4/projects/PROJECT
 
 ### Use Maven with `mvn dependency:get`
 
-You can install packages by using the Maven commands directly.
+You can install packages by using the Maven `dependency:get` [command](https://maven.apache.org/plugins/maven-dependency-plugin/get-mojo.html) directly.
 
 1. In your project directory, run:
 
    ```shell
-   mvn dependency:get -Dartifact=com.nickkipling.app:nick-test-app:1.1-SNAPSHOT
+   mvn dependency:get -Dartifact=com.nickkipling.app:nick-test-app:1.1-SNAPSHOT -DremoteRepositories=gitlab-maven::::<gitlab endpoint url>  -s <path to settings.xml>
    ```
 
+   - `<gitlab endpoint url>` is the URL of the GitLab [endpoint](#use-the-gitlab-endpoint-for-maven-packages).
+   - `<path to settings.xml>` is the path to the `settings.xml` file that contains the [authentication details](#authenticate-to-the-package-registry-with-maven).
+
+NOTE:
+The repository IDs in the command(`gitlab-maven`) and the `settings.xml` file must match.
+
 The message should show that the package is downloading from the Package Registry:
 
 ```shell
diff --git a/doc/user/profile/index.md b/doc/user/profile/index.md
index ad67fe4bfd8..e4cf905bbce 100644
--- a/doc/user/profile/index.md
+++ b/doc/user/profile/index.md
@@ -111,8 +111,8 @@ the README file with information, it's included on your profile page.
 
 To create a new project and add its README to your profile:
 
-1. On the top bar, select **Main menu > Projects**.
-1. Select **Create new project**.
+1. On the top bar, select **Main menu > Projects > View all projects**.
+1. On the right of the page, select **New project**.
 1. Select **Create blank project**.
 1. Enter the project details:
    - In the **Project name** field, enter the name for your new project.
diff --git a/doc/user/project/import/gitlab_com.md b/doc/user/project/import/gitlab_com.md
index 6c0f18dbdd3..8d30a9c7f52 100644
--- a/doc/user/project/import/gitlab_com.md
+++ b/doc/user/project/import/gitlab_com.md
@@ -16,7 +16,8 @@ Prerequisite:
 
 To import a GitLab.com project to your self-managed GitLab instance:
 
-1. On the top bar, select **Main menu > Projects > Create new project**.
+1. In GitLab, on the top bar, select **Main menu > Projects > View all projects**.
+1. On the right of the page, select **New project**.
 1. Select **Import project**.
 1. Select **GitLab.com**.
 1. Give GitLab.com permission to access your projects.
diff --git a/doc/user/project/import/repo_by_url.md b/doc/user/project/import/repo_by_url.md
index f288a4891bb..d64bea2bb41 100644
--- a/doc/user/project/import/repo_by_url.md
+++ b/doc/user/project/import/repo_by_url.md
@@ -9,7 +9,8 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 You can import your existing repositories by providing the Git URL:
 
-1. On the top bar, select **Main menu > Create new project**.
+1. In GitLab, on the top bar, select **Main menu > Projects > View all projects**.
+1. On the right of the page, select **New project**.
 1. Select the **Import project** tab.
 1. Select **Repository by URL**.
 1. Enter a **Git repository URL**.
diff --git a/doc/user/project/merge_requests/creating_merge_requests.md b/doc/user/project/merge_requests/creating_merge_requests.md
index 232c951dd17..1a44126f7ff 100644
--- a/doc/user/project/merge_requests/creating_merge_requests.md
+++ b/doc/user/project/merge_requests/creating_merge_requests.md
@@ -90,7 +90,7 @@ to reduce the need for editing merge requests manually through the UI.
 
 You can create a merge request from your fork to contribute back to the main project.
 
-1. On the top bar, select **Main menu > Project**.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. Select your fork of the repository.
 1. On the left menu, go to **Merge requests**, and select **New merge request**.
 1. In the **Source branch** drop-down list box, select the branch in your forked repository as the source branch.
@@ -165,7 +165,7 @@ scenarios when you create a new merge request:
 To have merge requests from a fork by default target your own fork
 (instead of the upstream project), you can change the default.
 
-1. On the top bar, select **Main menu > Project**.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left menu, select **Settings > General > Merge requests**.
 1. In the **Target project** section, select the option you want to use for
    your default target project.
diff --git a/doc/user/project/merge_requests/index.md b/doc/user/project/merge_requests/index.md
index ca40b724d95..500fb95c193 100644
--- a/doc/user/project/merge_requests/index.md
+++ b/doc/user/project/merge_requests/index.md
@@ -160,9 +160,7 @@ change and whether you need access to a development environment:
 
 ## Assign a user to a merge request
 
-When a merge request is created, it's assigned by default to the person who created it.
-This person owns the merge request, but isn't responsible for [reviewing it](reviews/index.md).
-To assign the merge request to someone else, use the `/assign @user`
+To assign the merge request to a user, use the `/assign @user`
 [quick action](../quick_actions.md#issues-merge-requests-and-epics) in a text area in
 a merge request, or:
 
diff --git a/doc/user/project/service_desk.md b/doc/user/project/service_desk.md
index cfd5c0a9cf5..bafa2005fdf 100644
--- a/doc/user/project/service_desk.md
+++ b/doc/user/project/service_desk.md
@@ -360,7 +360,7 @@ does not count toward the license limit count.
 
 ### Moving a Service Desk issue
 
-Service Desk issues can be moved like any other issue in GitLab. 
+Service Desk issues can be moved like any other issue in GitLab.
 
 You can move a Service Desk issue the same way you
 [move a regular issue](issues/managing_issues.md#move-an-issue) in GitLab.
diff --git a/doc/user/project/settings/index.md b/doc/user/project/settings/index.md
index 3cff66e01c5..5c2118e02cf 100644
--- a/doc/user/project/settings/index.md
+++ b/doc/user/project/settings/index.md
@@ -13,7 +13,7 @@ Use the **Settings** page to manage the configuration options in your [project](
 
 You must have at least the Maintainer role to view project settings.
 
-1. On the top bar, select **Main menu > Projects > View all projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Settings > General**.
 1. To display all settings in a section, select **Expand**.
 1. Optional. Use the search box to find a setting.
@@ -23,7 +23,7 @@ You must have at least the Maintainer role to view project settings.
 Use the project general settings to edit your project details.
 
 1. Sign in to GitLab with at least the Maintainer role.
-1. On the top bar, select **Main menu > Projects > View all projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Settings > General**.
 1. In the **Project name** text box, enter your project name.
 1. In the **Project description** text box, enter your project description.
@@ -35,7 +35,7 @@ Use topics to categorize projects and find similar new projects.
 
 To assign topics to a project:
 
-1. On the top bar, select **Main menu > Projects > View all projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Settings** > **General**.
 1. In the **Topics** text box, enter the project topics. Popular topics are suggested as you type.
 1. Select **Save changes**.
@@ -226,7 +226,7 @@ This alternative ensures the compliance pipeline does not re-start the parent pi
 
 To configure visibility, features, and permissions for a project:
 
-1. On the top bar, select **Main menu > Projects > View all projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Settings > General**.
 1. Expand the **Visibility, project features, permissions** section.
 1. To change the project visibility, select the dropdown list. If you select to **Public**, you limit access to some features to **Only Project Members**.
@@ -286,7 +286,7 @@ In some environments, users can submit a [CVE identifier request](../../applicat
 
 To disable the CVE identifier request option in issues in your project:
 
-1. On the top bar, select **Main menu > Projects > View all projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Settings > General**.
 1. Expand the **Visibility, project features, permissions** section.
 1. Under **Issues**, turn off the **CVE ID requests in the issue sidebar** toggle.
@@ -298,7 +298,7 @@ Prerequisites:
 
 - You must be an Owner of the project to disable email notifications related to the project.
 
-1. On the top bar, select **Main menu > Projects > View all projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Settings > General**.
 1. Expand the **Visibility, project features, permissions** section.
 1. Clear the **Disable email notifications** checkbox.
@@ -339,7 +339,7 @@ other features are read-only. Archived projects are also hidden from project lis
 
 To archive a project:
 
-1. On the top bar, select **Main menu > Projects > View all projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Settings > General**.
 1. Expand **Advanced**.
 1. In the **Archive project** section, select **Archive project**.
@@ -380,7 +380,7 @@ When you change the repository path, users may experience issues if they push to
 
 To rename a repository:
 
-1. On the top bar, select **Main menu > Projects > View all projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Settings > General**.
 1. Expand the **Advanced** section.
 1. In the **Change path** text box, edit the path.
@@ -402,7 +402,7 @@ Prerequisites:
 
 To transfer a project:
 
-1. On the top bar, select **Main menu > Projects > View all projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Settings > General**.
 1. Expand **Advanced**.
 1. Under **Transfer project**, choose the namespace to transfer the project to.
@@ -433,7 +433,7 @@ Prerequisite:
 
 To delete a project:
 
-1. On the top bar, select **Main menu > Projects > View all projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Settings > General**.
 1. Expand **Advanced**.
 1. In the "Delete project" section, select **Delete project**.
@@ -472,7 +472,7 @@ Prerequisites:
 
 To immediately delete a project marked for deletion:
 
-1. On the top bar, select **Main menu > Projects > View all projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Settings > General**.
 1. Expand **Advanced**.
 1. In the "Permanently delete project" section, select **Delete project**.
@@ -504,7 +504,7 @@ To restore the fork relationship, [use the API](../../../api/projects.md#create-
 
 To remove a fork relationship:
 
-1. On the top bar, select **Main menu > Projects > View all projects** and find your project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. On the left sidebar, select **Settings > General**.
 1. Expand **Advanced**.
 1. In the **Remove fork relationship** section, select **Remove fork relationship**.
diff --git a/doc/user/project/working_with_projects.md b/doc/user/project/working_with_projects.md
index 49ec5fe50e2..e58bf5aa557 100644
--- a/doc/user/project/working_with_projects.md
+++ b/doc/user/project/working_with_projects.md
@@ -62,7 +62,7 @@ To create a project in GitLab:
 
 1. On the top bar, select **Main menu > Projects > View all projects**.
 1. On the right of the page, select **New project**.
-1. On the **Create new project** page, select an option:
+1. Select an option:
    - Create a [blank project](#create-a-blank-project).
    - Create a project from a:
       - [built-in template](#create-a-project-from-a-built-in-template).
@@ -207,8 +207,7 @@ Prerequisites:
   [added to your GitLab account](../ssh.md#add-an-ssh-key-to-your-gitlab-account).
 - You must have permission to add new projects to a namespace. To check if you have permission:
 
-  1. On the top bar, select **Main menu > Groups > View all groups**.
-  1. Select a group.
+  1. On the top bar, select **Main menu > Groups** and find your group.
   1. Confirm that **New project** is visible in the upper right
      corner. Contact your GitLab
      administrator if you require permission.
@@ -254,8 +253,7 @@ You can add a star to projects you use frequently to make them easier to find.
 
 To add a star to a project:
 
-1. On the top bar, select **Main menu > Projects > View all projects**.
-1. Select a project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. In the upper right corner of the page, select **Star**.
 
 ## View starred projects
@@ -280,7 +278,7 @@ called `my-project` under your username, the project is created at `https://gitl
 To view your personal projects:
 
 1. On the top bar, select **Main menu > Projects > View all projects**.
-1. Under **Your projects**, select **Personal**.
+1. In the **Your projects** tab, select **Personal**.
 
 ## Delete a project
 
@@ -289,8 +287,7 @@ you can [enable delayed project removal](../group/manage.md#enable-delayed-proje
 
 To delete a project:
 
-1. On the top bar, select **Main menu > Projects > View all projects**.
-1. Select a project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. Select **Settings > General**.
 1. Expand the **Advanced** section.
 1. Scroll down to the **Delete project** section.
@@ -324,8 +321,7 @@ Each project in the list shows:
 
 To view the activity of a project:
 
-1. On the top bar, select **Main menu > Projects > View all projects**.
-1. Select a project.
+1. On the top bar, select **Main menu > Projects** and find your project..
 1. On the left sidebar, select **Project information > Activity**.
 1. Select a tab to view the type of project activity.
 
@@ -359,8 +355,7 @@ member and cannot contribute.
 
 To leave a project:
 
-1. On the top bar, select **Main menu > Projects > View all projects**.
-1. Select a project.
+1. On the top bar, select **Main menu > Projects** and find your project.
 1. Select **Leave project**. The **Leave project** option only displays
 on the project dashboard when a project is part of a group under a
 [group namespace](../namespace/index.md).
diff --git a/doc/user/usage_quotas.md b/doc/user/usage_quotas.md
index 1f3a69944e8..828c9a3c4b0 100644
--- a/doc/user/usage_quotas.md
+++ b/doc/user/usage_quotas.md
@@ -61,7 +61,7 @@ Prerequisites:
 - To view storage usage for a namespace, you must have the Owner role for the namespace.
 
 1. Go to your project or namespace:
-   - For a project, on the top bar, select **Main menu > Projects > View all projects** and find your project.
+   - For a project, on the top bar, select **Main menu > Projects** and find your project.
    - For a namespace, enter the URL in your browser's toolbar.
 1. From the left sidebar, select **Settings > Usage Quotas**.
 1. Select the **Storage** tab.