Add latest changes from gitlab-org/gitlab@13-7-stable-eev13.7.0-rc42

1 files changed, 6 insertions, 6 deletions

diff --git a/doc/user/admin_area/settings/visibility_and_access_controls.md b/doc/user/admin_area/settings/visibility_and_access_controls.md
index 3740dc95c12..fe1841e7020 100644
--- a/doc/user/admin_area/settings/visibility_and_access_controls.md
+++ b/doc/user/admin_area/settings/visibility_and_access_controls.md
@@ -1,7 +1,7 @@
 ---
 stage: Create
 group: Source Code
-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/#designated-technical-writers"
+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: reference
 ---
 
@@ -43,7 +43,7 @@ To do this:
 
 1. Uncheck the **Allow owners to manage default branch protection per group** checkbox.
 
-NOTE: **Note:**
+NOTE:
 GitLab administrators can still update the default branch protection of a group.
 
 ## Default project creation protection
@@ -74,7 +74,7 @@ To ensure only admin users can delete projects:
 By default, a project marked for deletion will be permanently removed with immediate effect.
 By default, a group marked for deletion will be permanently removed after 7 days.
 
-CAUTION: **Warning:**
+WARNING:
 The default behavior of [Delayed Project deletion](https://gitlab.com/gitlab-org/gitlab/-/issues/32935) in GitLab 12.6 was changed to
 [Immediate deletion](https://gitlab.com/gitlab-org/gitlab/-/issues/220382) in GitLab 13.2.
 
@@ -151,7 +151,7 @@ For more details, see [Exporting a project and its data](../../../user/project/s
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/4696) in GitLab 8.10.
 
-With GitLab's access restrictions, you can select with which protocols users can communicate with
+With GitLab access restrictions, you can select with which protocols users can communicate with
 GitLab.
 
 Disabling an access protocol does not block access to the server itself via those ports. The ports
@@ -180,7 +180,7 @@ When only one protocol is enabled:
 On top of these UI restrictions, GitLab will deny all Git actions on the protocol
 not selected.
 
-CAUTION: **Important:**
+WARNING:
 Starting with [GitLab 10.7](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/18021),
 HTTP(S) protocol will be allowed for Git clone or fetch requests done by GitLab Runner
 from CI/CD jobs, even if _Only SSH_ was selected.
@@ -208,7 +208,7 @@ To specify a custom Git clone URL for HTTP(S):
 1. Enter a root URL for **Custom Git clone URL for HTTP(S)**.
 1. Click on **Save changes**.
 
-NOTE: **Note:**
+NOTE:
 SSH clone URLs can be customized in `gitlab.rb` by setting `gitlab_rails['gitlab_ssh_host']` and
 other related settings.