Revisions from technical writer

Bring closer to GitLab tone and style.

doc/api/merge_request_approvals.md

@@ -990,7 +990,7 @@ POST /projects/:id/merge_requests/:merge_request_iid/approve
 | `approval_password` | string  | no      | Current user's password. Required if [**Require user password to approve**](../user/project/merge_requests/approvals/settings.md#require-user-password-to-approve) is enabled in the project settings. |
 
 The `sha` parameter works in the same way as
-when [accepting a merge request](merge_requests.md#accept-mr): if it is passed, then it must
+when [accepting a merge request](merge_requests.md#merge-a-merge-request): if it is passed, then it must
 match the current HEAD of the merge request for the approval to be added. If it
 does not match, the response code is `409`.
 

doc/api/merge_requests.md

@@ -1454,9 +1454,9 @@ DELETE /projects/:id/merge_requests/:merge_request_iid
 curl --request DELETE --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/projects/4/merge_requests/85"
 ```
 
-## Accept MR
+## Merge a merge request
 
-Merge changes submitted with MR using this API.
+Accept and merge changes submitted with MR using this API.
 
 If a merge request is unable to be accepted (such as Draft, Closed, Pipeline Pending Completion, or Failed while requiring Success) - you receive a `405` and the error message 'Method Not Allowed'