Resolve follow-up issues in V&A Content

doc/user/admin_area/settings/visibility_and_access_controls.md

@@ -105,7 +105,7 @@ With GitLab's access restrictions, you can select with which protocols users can
 GitLab.
 
 Disabling an access protocol does not block access to the server itself via those ports. The ports
-used for the protocol, SSH or HTTP, will still be accessible. The GitLab restrictions apply at the
+used for the protocol, SSH or HTTP(S), will still be accessible. The GitLab restrictions apply at the
 application level.
 
 To specify the enabled Git access protocols:
@@ -150,7 +150,7 @@ For more details, see [SSH key restrictions](../../../security/ssh_keys_restrict
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3586) in GitLab 10.3.
 
-This option is enabled by default. By disabling it, both pull and push mirroring will no longer
+This option is enabled by default. By disabling it, both [pull and push mirroring](../../../workflow/repository_mirroring.md) will no longer
 work in every repository and can only be re-enabled by an admin on a per-project basis.
 
 ![Mirror settings](img/mirror_settings.png)

doc/user/group/index.md

@@ -186,8 +186,7 @@ By default, [Developers and Maintainers](../permissions.md#group-members-permiss
 
 To change this setting for a specific group:
 
-1. Go to the group's page.
-1. Go to **Settings > General**.
+1. Go to the group's **Settings > General** page.
 1. Expand the **Permissions, LFS, 2FA** section.
 1. Select the desired option in the **Allowed to create projects** dropdown list.
 1. Click **Save changes**.