Made "merge requests" lowercase

doc/user/project/merge_requests/approvals/settings.md

@@ -7,7 +7,7 @@ type: reference, concepts
 
 # Merge request approval settings
 
-The settings for Merge Request Approvals are found by going to
+The settings for merge request approvals are found by going to
 **Settings > General** and expanding **Merge request (MR) approvals**.
 
 ## Prevent overriding default approvals
@@ -90,7 +90,7 @@ To enable this feature:
 
 ## Security approvals in merge requests **(ULTIMATE)**
 
-Merge Request Approvals can be configured to require approval from a member
+Merge request approvals can be configured to require approval from a member
 of your security team when a vulnerability would be introduced by a merge request.
 
 For more information, see

doc/user/project/merge_requests/cherry_pick_changes.md

@@ -16,7 +16,7 @@ with a **Cherry-pick** button in merge requests and commit details.
 After the merge request has been merged, a **Cherry-pick** button displays
 to cherry-pick the changes introduced by that merge request.
 
-![Cherry-pick Merge Request](img/cherry_pick_changes_mr.png)
+![Cherry-pick merge request](img/cherry_pick_changes_mr.png)
 
 After you click that button, a modal displays a
 [branch filter search box](../repository/branches/index.md#branch-filter-search-box)
@@ -32,7 +32,7 @@ where you can choose to either:
 When you cherry-pick a merge commit, GitLab displays a system note to the related merge
 request thread. It crosslinks the new commit and the existing merge request.
 
-![Cherry-pick tracking in Merge Request timeline](img/cherry_pick_mr_timeline_v12_9.png)
+![Cherry-pick tracking in merge request timeline](img/cherry_pick_mr_timeline_v12_9.png)
 
 Each deployment's [list of associated merge requests](../../../api/deployments.md#list-of-merge-requests-associated-with-a-deployment) includes cherry-picked merge commits.
 

doc/user/project/merge_requests/code_quality.md

@@ -519,7 +519,7 @@ to change the default configuration, **not** a `.codequality.yml` file. If you u
 the wrong filename, the [default `.codeclimate.yml`](https://gitlab.com/gitlab-org/ci-cd/codequality/-/blob/master/codeclimate_defaults/.codeclimate.yml.template)
 is still used.
 
-### No Code Quality report is displayed in a Merge Request
+### No Code Quality report is displayed in a merge request
 
 This can be due to multiple reasons:
 
@@ -531,7 +531,7 @@ This can be due to multiple reasons:
   nothing is displayed.
 - The [`artifacts:expire_in`](../../../ci/yaml/README.md#artifactsexpire_in) CI/CD
   setting can cause the Code Quality artifact(s) to expire faster than desired.
-- The widgets use the pipeline of the latest commit to the target branch. If commits are made to the default branch that do not run the code quality job, this may cause the Merge Request widget to have no base report for comparison.
+- The widgets use the pipeline of the latest commit to the target branch. If commits are made to the default branch that do not run the code quality job, this may cause the merge request widget to have no base report for comparison.
 - If you use the [`REPORT_STDOUT` environment variable](https://gitlab.com/gitlab-org/ci-cd/codequality#environment-variables), no report file is generated and nothing displays in the merge request.
 - Large `gl-code-quality-report.json` files (esp. >10 MB) are [known to prevent the report from being displayed](https://gitlab.com/gitlab-org/gitlab/-/issues/2737).
   As a work-around, try removing [properties](https://github.com/codeclimate/platform/blob/master/spec/analyzers/SPEC.md#data-types)

doc/user/project/merge_requests/creating_merge_requests.md

@@ -3,14 +3,14 @@ stage: Create
 group: Code Review
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 type: howto
-description: "How to create Merge Requests in GitLab."
+description: "How to create merge requests in GitLab."
 disqus_identifier: 'https://docs.gitlab.com/ee/gitlab-basics/add-merge-request.html'
 ---
 
 # How to create a merge request **(FREE)**
 
 Before creating a merge request, read through an
-[introduction to Merge Requests](getting_started.md)
+[introduction to merge requests](getting_started.md)
 to familiarize yourself with the concept, the terminology,
 and to learn what you can do with them.
 
@@ -21,16 +21,16 @@ or through the [GitLab UI](#new-merge-request-from-a-new-branch-created-through-
 This document describes the several ways to create a merge request.
 
 When you start a new merge request, regardless of the method,
-you are taken to the [**New Merge Request** page](#new-merge-request-page)
+you are taken to the [**New merge request** page](#new-merge-request-page)
 to fill it with information about the merge request.
 
 If you push a new branch to GitLab, also regardless of the method,
-you can click the [**Create Merge Request**](#create-merge-request-button)
+you can click the [**Create merge request**](#create-merge-request-button)
 button and start a merge request from there.
 
-## New Merge Request page
+## New merge request page
 
-On the **New Merge Request** page, start by filling in the title and description
+On the **New merge request** page, start by filling in the title and description
 for the merge request. If commits already exist on the branch, GitLab suggests a
 merge request title for you:
 
@@ -43,31 +43,31 @@ merge request title for you:
 The title is the only field that is mandatory in all cases.
 
 From there, you can fill it with information (title, description,
-assignee(s), milestone, labels, approvers) and click **Create Merge Request**.
+assignee(s), milestone, labels, approvers) and click **Create merge request**.
 
 From that initial screen, you can also see all the commits,
 pipelines, and file changes pushed to your branch before submitting
 the merge request.
 
-![New Merge Request page](img/new_merge_request_page_v12_6.png)
+![New merge request page](img/new_merge_request_page_v12_6.png)
 
 NOTE:
 You can push one or more times to your branch in GitLab before
 creating the merge request.
 
-## Create Merge Request button
+## Create merge request button
 
 Once you have pushed a new branch to GitLab, visit your repository
 in GitLab and to see a call-to-action at the top of your screen
-from which you can click the button **Create Merge Request**.
+from which you can click the button **Create merge request**.
 
-![Create Merge Request button](img/create_merge_request_button_v12_6.png)
+![Create merge request button](img/create_merge_request_button_v12_6.png)
 
 You can also see the **Create merge request** button in the top-right of the:
 
 - **Project** page.
 - **Repository > Files** page.
-- **Merge Requests** page.
+- **Merge requests** page.
 
 In this case, GitLab uses the most recent branch you pushed
 changes to as the source branch, and the default branch in the current
@@ -90,7 +90,7 @@ Once you have added, edited, or uploaded the file:
 1. Click **Commit changes**.
 
 If you chose to start a merge request, you are taken to the
-[**New Merge Request** page](#new-merge-request-page), from
+[**New merge request** page](#new-merge-request-page), from
 which you can fill it in with information and submit the merge request.
 
 The merge request targets the default branch of the repository.
@@ -103,8 +103,8 @@ navigate to your project's **Repository > Branches** and click
 **New branch**. A new branch is created and you can start
 editing files.
 
-Once committed and pushed, you can click on the [**Create Merge Request**](#create-merge-request-button)
-button to open the [**New Merge Request** page](#new-merge-request-page).
+Once committed and pushed, you can click on the [**Create merge request**](#create-merge-request-button)
+button to open the [**New merge request** page](#new-merge-request-page).
 A new merge request is started using the current branch as the source,
 and the default branch in the current project as the target.
 
@@ -140,7 +140,7 @@ remote: To create a merge request for docs-new-merge-request, visit:
 remote:   https://gitlab-instance.com/my-group/my-project/merge_requests/new?merge_request%5Bsource_branch%5D=my-new-branch
 ```
 
-Copy that link and paste it in your browser, and the [**New Merge Request page**](#new-merge-request-page)
+Copy that link and paste it in your browser, and the [**New merge request page**](#new-merge-request-page)
 is displayed.
 
 There is also a number of [flags you can add to commands when pushing through the command line](../push_options.md) to reduce the need for editing merge requests manually through the UI.
@@ -148,20 +148,20 @@ There is also a number of [flags you can add to commands when pushing through th
 If you didn't push your branch to GitLab through the command line
 (for example, you used a Git CLI application to push your changes),
 you can create a merge request through the GitLab UI by clicking
-the [**Create Merge Request**](#create-merge-request-button) button.
+the [**Create merge request**](#create-merge-request-button) button.
 
 ## New merge request from an issue
 
 You can also [create a new merge request directly from an issue](../repository/web_editor.md#create-a-new-branch-from-an-issue).
 
-## New merge request from the Merge Requests page
+## New merge request from the merge requests page
 
 You can start creating a new merge request by clicking the
-**New merge request** button on the **Merge Requests** page in a project.
+**New merge request** button on the **merge requests** page in a project.
 Then choose the source project and branch that contain your changes,
 and the target project and branch where you want to merge the changes into.
 Click on **Compare branches and continue** to go to the
-[**New Merge Request** page](#new-merge-request-page) and fill in the details.
+[**New merge request** page](#new-merge-request-page) and fill in the details.
 
 ## New merge request from a fork
 
@@ -169,7 +169,7 @@ After forking a project and applying your local changes, complete the following
 create a merge request from your fork to contribute back to the main project:
 
 1. Go to **Projects > Your Projects** and select your fork of the repository.
-1. In the left menu, go to **Merge Requests**, and click **New Merge Request**.
+1. In the left menu, go to **Merge requests**, and click **New merge request**.
 1. In the **Source branch** drop-down list box, select your branch in your forked repository as the source branch.
 1. In the **Target branch** drop-down list box, select the branch from the upstream repository as the target branch.
    You can set a [default target project](#set-the-default-target-project) to
@@ -247,6 +247,6 @@ apply the patches. The target branch can be specified using the
 [`/target_branch` quick action](../quick_actions.md). If the source
 branch already exists, the patches are applied on top of it.
 
-## Reviewing and managing Merge Requests
+## Reviewing and managing merge requests
 
 Once you have submitted a merge request, it can be [reviewed and managed](reviews/index.md) through GitLab.

doc/user/project/merge_requests/csv_export.md

@@ -4,13 +4,13 @@ group: Compliance
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 ---
 
-# Export Merge Requests to CSV **(FREE)**
+# Export merge requests to CSV **(FREE)**
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/3619) in GitLab 13.6.
 
-Exporting Merge Requests CSV enables you and your team to export all the data collected from merge requests into a comma-separated values (CSV) file, which stores tabular data in plain text.
+Exporting merge requests CSV enables you and your team to export all the data collected from merge requests into a comma-separated values (CSV) file, which stores tabular data in plain text.
 
-To export Merge Requests to CSV, navigate to your **Merge Requests** from the sidebar of a project and click **Export to CSV**.
+To export merge requests to CSV, navigate to your **Merge requests** from the sidebar of a project and click **Export to CSV**.
 
 ## CSV Output
 

doc/user/project/merge_requests/drafts.md

@@ -66,7 +66,7 @@ when you mark a merge request as ready, notifications are triggered to
 When viewing or searching in your project's merge requests list, you can include or exclude
 draft merge requests:
 
-1. In your project, select **Merge Requests** from the left sidebar.
+1. Go to your project and select **Merge requests**.
 1. In the navigation bar, click **Open**, **Merged**, **Closed**, or **All** to
    filter by merge request status.
 1. Click the search box to display a list of filters and select **Draft**, or

doc/user/project/merge_requests/fail_fast_testing.md

@@ -42,7 +42,7 @@ This template requires:
 - A project built in Rails that uses RSpec for testing.
 - CI/CD configured to:
   - Use a Docker image with Ruby available.
-  - Use [Pipelines for Merge Requests](../../../ci/merge_request_pipelines/index.md#configuring-pipelines-for-merge-requests)
+  - Use [Pipelines for merge requests](../../../ci/merge_request_pipelines/index.md#configuring-pipelines-for-merge-requests)
 - [Pipelines for Merged Results](../../../ci/merge_request_pipelines/pipelines_for_merged_results/index.md#enable-pipelines-for-merged-results)
   enabled in the project settings.
 - A Docker image with Ruby available. The template uses `image: ruby:2.6` by default, but you [can override](../../../ci/yaml/includes.md#overriding-external-template-values) this.

doc/user/project/merge_requests/getting_started.md

@@ -3,12 +3,12 @@ stage: Create
 group: Code Review
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 type: index, reference
-description: "Getting started with Merge Requests."
+description: "Getting started with merge requests."
 ---
 
-# Getting started with Merge Requests **(FREE)**
+# Getting started with merge requests **(FREE)**
 
-A Merge Request (**MR**) is the basis of GitLab as a code
+A merge request (**MR**) is the basis of GitLab as a code
 collaboration and version control.
 
 When working in a Git-based platform, you can use branching
@@ -25,7 +25,7 @@ avoiding changes to be pushed directly to the default branch
 without prior reviews, tests, and approvals.
 
 When you create a new feature branch, change the files, and push
-it to GitLab, you have the option to create a **Merge Request**,
+it to GitLab, you have the option to create a **merge request**,
 which is essentially a _request_ to merge one branch into another.
 
 The branch you added your changes into is called _source branch_
@@ -122,7 +122,7 @@ Requesting a code review is an important part of contributing code. However, dec
 your code and asking for a review are no easy tasks. Using the "assignee" field for both authors and
 reviewers makes it hard for others to determine who's doing what on a merge request.
 
-The Merge Request Reviewers feature enables you to request a review of your work, and
+The merge request Reviewers feature enables you to request a review of your work, and
 see the status of the review. Reviewers help distinguish the roles of the users
 involved in the merge request. In comparison to an **Assignee**, who is directly
 responsible for creating or merging a merge request, a **Reviewer** is a team member
@@ -234,7 +234,7 @@ The feature today works only on merge. Clicking the **Remove source branch** but
 after the merge request was merged will not automatically retarget a merge request.
 This improvement is [tracked as a follow-up](https://gitlab.com/gitlab-org/gitlab/-/issues/321559).
 
-## Recommendations and best practices for Merge Requests
+## Recommendations and best practices for merge requests
 
 - When working locally in your branch, add multiple commits and only push when
   you're done, so GitLab runs only one pipeline for all the commits pushed

doc/user/project/merge_requests/merge_request_dependencies.md

@@ -5,10 +5,10 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: reference, concepts
 ---
 
-# Merge Request dependencies **(PREMIUM)**
+# Merge request dependencies **(PREMIUM)**
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/9688) in [GitLab Premium](https://about.gitlab.com/pricing/) 12.2.
-> - [Renamed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/17291) from "Cross-project dependencies" to "Merge Requests dependencies" in [GitLab Premium](https://about.gitlab.com/pricing/) 12.4.
+> - [Renamed](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/17291) from "Cross-project dependencies" to "Merge request dependencies" in [GitLab Premium](https://about.gitlab.com/pricing/) 12.4.
 > - Intra-project MR dependencies were [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/16799) in [GitLab Premium](https://about.gitlab.com/pricing/) 12.4.
 
 Merge request dependencies allows a required order of merging

doc/user/project/merge_requests/reviews/index.md

@@ -17,8 +17,8 @@ members can choose to accept or reject it.
 
 You can view merge requests for a specific project, or for all projects in a group:
 
-- **Specific project**: Go to your project and select **Merge Requests**.
-- **All projects in a group**: Go to your group and select **Merge Requests**.
+- **Specific project**: Go to your project and select **Merge requests**.
+- **All projects in a group**: Go to your group and select **Merge requests**.
   If your group contains subgroups, this view also displays merge requests from the subgroup projects.
   GitLab displays a count of open merge requests in the left sidebar, but
   [caches the value](#cached-merge-request-count) for groups with a large number of
@@ -101,15 +101,17 @@ A merge commit is created for every merge, but the branch is only merged if
 a fast-forward merge is possible. This ensures that if the merge request build
 succeeded, the target branch build also succeeds after the merge.
 
-Navigate to a project's settings, select the **Merge commit with semi-linear history**
-option under **Merge Requests: Merge method** and save your changes.
+1. Go to your project and select **Settings > General**.
+1. Expand **Merge requests**.
+1. In the **Merge method** section, select **Merge commit with semi-linear history**.
+1. Select **Save changes**.
 
 ## Perform inline code reviews
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/13950) in GitLab 11.5.
 
 In a merge request, you can leave comments in any part of the file being changed.
-In the Merge Request Diff UI, you can:
+In the merge request Diff UI, you can:
 
 - **Comment on a single line**: Select the **{comment}** **comment** icon in the
   gutter to expand the diff lines and display a comment box.
@@ -222,15 +224,15 @@ seconds and the status should update automatically.
 
 #### Bug
 
-Merge Request pipeline statuses can't be retrieved when the following occurs:
+Merge request pipeline statuses can't be retrieved when the following occurs:
 
-1. A Merge Request is created
-1. The Merge Request is closed
+1. A merge request is created
+1. The merge request is closed
 1. Changes are made in the project
-1. The Merge Request is reopened
+1. The merge request is reopened
 
 To enable the pipeline status to be properly retrieved, close and reopen the
-Merge Request again.
+merge request again.
 
 ## Tips
 

doc/user/project/merge_requests/test_coverage_visualization.md

@@ -53,12 +53,12 @@ of times the line was checked by tests.
 
 NOTE:
 A limit of 100 `<source>` nodes for Cobertura format XML files applies. If your Cobertura report exceeds
-100 nodes, there can be mismatches or no matches in the Merge Request diff view.
+100 nodes, there can be mismatches or no matches in the merge request diff view.
 
 ### Artifact expiration
 
 By default, the [pipeline artifact](../../../ci/pipelines/pipeline_artifacts.md#storage) used
-to draw the visualization on the Merge Request expires **one week** after creation.
+to draw the visualization on the merge request expires **one week** after creation.
 
 ### Automatic class path correction
 

doc/user/project/merge_requests/versions.md

@@ -49,11 +49,11 @@ This only applies to commits that are in the most recent version of a merge
 request - if commits were in a merge request, then rebased out of that merge
 request, they aren't linked.
 
-## `HEAD` comparison mode for Merge Requests
+## `HEAD` comparison mode for merge requests
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/27008) in GitLab 12.10.
 
-Merge Requests, particularly the **Changes** tab, is where source code
+Merge requests, particularly the **Changes** tab, is where source code
 is reviewed and discussed. In circumstances where the target branch was
 merged into the source branch of the merge request, the changes in the
 source and target branch can be shown mixed together making it hard to