Doc Consistency: security

doc/security/reset_user_password.md

@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: howto
 ---
 
-# How to reset user password
+# How to reset user password **(FREE SELF)**
 
 There are a few ways to reset the password of a user.
 

doc/security/ssh_keys_restrictions.md

@@ -27,7 +27,7 @@ the minimum key length for each technology:
    ![SSH keys restriction admin settings](img/ssh_keys_restrictions_settings.png)
 
 If a restriction is imposed on any key type, users cannot upload new SSH keys that don't meet the
-requirement. Any existing keys that don't meet it are disabled but not removed and users cannot to
+requirement. Any existing keys that don't meet it are disabled but not removed and users cannot
 pull or push code using them.
 
 An icon is visible to the user of a restricted key in the SSH keys section of their profile:

doc/security/token_overview.md

@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: reference
 ---
 
-# GitLab Token overview
+# GitLab Token overview **(FREE)**
 
 This document lists tokens used in GitLab, their purpose and, where applicable, security guidance.
 

doc/security/two_factor_authentication.md

@@ -44,7 +44,7 @@ Gitlab::CurrentSettings.update!('require_two_factor_authentication': false)
 
 ## Enforce 2FA for all users in a group **(FREE)**
 
-> [Introduced in](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/24965) GitLab 12.0, 2FA settings for a group are also applied to subgroups.
+> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/24965) in GitLab 12.0, 2FA settings for a group are also applied to subgroups.
 
 To enforce 2FA only for certain groups:
 

doc/security/user_email_confirmation.md

@@ -5,7 +5,7 @@ group: Access
 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
 ---
 
-# User email confirmation at sign-up
+# User email confirmation at sign-up **(FREE SELF)**
 
 GitLab can be configured to require confirmation of a user's email address when
 the user signs up. When this setting is enabled, the user is unable to sign in until

doc/security/user_file_uploads.md

@@ -5,7 +5,7 @@ group: Access
 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
 ---
 
-# User File Uploads
+# User File Uploads **(FREE)**
 
 Images that are attached to issues, merge requests, or comments
 do not require authentication to be viewed if they are accessed directly by URL.