Add latest changes from gitlab-org/gitlab@13-5-stable-eev13.5.0-rc42

1 files changed, 10 insertions, 8 deletions

diff --git a/doc/user/admin_area/abuse_reports.md b/doc/user/admin_area/abuse_reports.md
index 0283f1a9eff..4c346d7dfe8 100644
--- a/doc/user/admin_area/abuse_reports.md
+++ b/doc/user/admin_area/abuse_reports.md
@@ -20,6 +20,9 @@ To receive notifications of new abuse reports by e-mail, follow these steps:
 1. Expand the **Abuse reports** section.
 1. Provide an email address.
 
+The notification email address can also be set and retrieved
+[using the API](../../api/settings.md#list-of-settings-that-can-be-accessed-via-api-calls).
+
 ## Reporting abuse
 
 To find out more about reporting abuse, see [abuse reports user
@@ -31,14 +34,14 @@ To access abuse reports, go to **Admin Area > Abuse Reports**.
 
 There are 3 ways to resolve an abuse report, with a button for each method:
 
-- Remove user & report. This will:
-  - [Delete the reported user](../profile/account/delete_account.md) from the
+- Remove user & report. This:
+  - [Deletes the reported user](../profile/account/delete_account.md) from the
     instance.
-  - Remove the abuse report from the list.
+  - Removes the abuse report from the list.
 - [Block user](#blocking-users).
-- Remove report. This will:
-  - Remove the abuse report from the list.
-  - Remove access restrictions for the reported user.
+- Remove report. This:
+  - Removes the abuse report from the list.
+  - Removes access restrictions for the reported user.
 
 The following is an example of the **Abuse Reports** page:
 
@@ -54,8 +57,7 @@ Blocking a user:
 - Leaves them in the abuse report list.
 - Changes the **Block user** button to a disabled **Already blocked** button.
 
-The user will be notified with the
-[following message](https://gitlab.com/gitlab-org/gitlab/blob/master/app/workers/email_receiver_worker.rb#L38):
+The user is notified with the following message:
 
 ```plaintext
 Your account has been blocked. If you believe this is in error, contact a staff member.