Update note style in various docs

doc/public_access/public_access.md

@@ -42,10 +42,10 @@ They will appear in the public access directory (`/public`) for project members
 
 ## Visibility of groups
 
->**Note:**
-[Starting with][3323] GitLab 8.6, the group visibility has changed and can be
-configured the same way as projects. In previous versions, a group's page was
-always visible to all users.
+NOTE: **Note:**
+[Starting with](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3323) GitLab 8.6,
+the group visibility has changed and can be configured the same way as projects.
+In previous versions, a group's page was always visible to all users.
 
 Like with projects, the visibility of a group can be set to dictate whether
 anonymous users, all signed in users, or only explicit group members can view
@@ -53,8 +53,6 @@ it. The restriction for visibility levels on the application setting level also
 applies to groups, so if that's set to internal, the explore page will be empty
 for anonymous users. The group page now has a visibility level icon.
 
-[3323]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3323
-
 ## Visibility of users
 
 The public page of a user, located at `/username`, is always visible whether

doc/push_rules/push_rules.md

@@ -51,7 +51,7 @@ will get rejected.
 
 ## Enabling push rules
 
->**Note:**
+NOTE: **Note:**
 GitLab administrators can set push rules globally under
 **Admin area > Push Rules** that all new projects will inherit. You can later
 override them in a project's settings.
@@ -76,7 +76,7 @@ The following options are available.
 | Prohibited file names | **Starter** 7.10 | Any committed filenames that match this regular expression are not allowed to be pushed. Leave empty to allow any filenames. |
 | Maximum file size | **Starter** 7.12 | Pushes that contain added or updated files that exceed this file size (in MB) are rejected. Set to 0 to allow files of any size. |
 
->**Tip:**
+TIP: **Tip:**
 GitLab uses [RE2 syntax](https://github.com/google/re2/wiki/Syntax) for regular expressions in push rules, and you can test them at the [GoLang regex tester](https://regex-golang.appspot.com).
 
 ## Prevent pushing secrets to the repository
@@ -91,7 +91,7 @@ pushes to the repository when a file matches a regular expression as read from
 [`files_blacklist.yml`][list] (make sure you are at the right branch
 as your GitLab version when viewing this file).
 
-NOTE: **Note**:
+NOTE: **Note:**
 Files already committed won't get restricted by this push rule.
 
 Below is an example list of what will be rejected by these regular expressions:

doc/subscriptions/index.md

@@ -46,7 +46,8 @@ After purchase, the license file is sent to the email address tied to the Custom
 
 ### Link your GitLab.com account with your Customers Portal account
 
-NOTE: **Note:** This is *required* for GitLab.com subscriptions.
+NOTE: **Note:**
+This is *required* for GitLab.com subscriptions.
 
 Once signed into the customers portal, if your account is not already linked, you should be prompted to link your account with a "Link my GitLab Account" button.
 

doc/system_hooks/system_hooks.md

@@ -31,7 +31,9 @@ The triggers for most of these are self-explanatory, but `project_update` and `p
 
 System hooks can be used, e.g. for logging or changing information in a LDAP server.
 
-NOTE: **Note:** We follow the same structure and deprecations as [Webhooks](../user/project/integrations/webhooks.md) for Push and Tag events, but we never display commits.
+NOTE: **Note:**
+We follow the same structure and deprecations as [Webhooks](../user/project/integrations/webhooks.md)
+for Push and Tag events, but we never display commits.
 
 ## Hooks request example