Docs: Fixed Notes that didn't match style guide

Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/244970

doc/administration/pages/index.md

@@ -375,7 +375,7 @@ Pages access control is disabled by default. To enable it:
 1. [Reconfigure GitLab](../restart_gitlab.md#omnibus-gitlab-reconfigure).
 1. Users can now configure it in their [projects' settings](../../user/project/pages/pages_access_control.md).
 
-NOTE: **Important:**
+NOTE:
 For this setting to be effective with multi-node setups, it has to be applied to
 all the App nodes and Sidekiq nodes.
 

doc/administration/repository_storage_types.md

@@ -179,7 +179,7 @@ LFS objects are also [S3 compatible](lfs/index.md#storing-lfs-objects-in-remote-
 
 ## Legacy storage
 
-NOTE: **Deprecated:**
+WARNING:
 In GitLab 13.0, hashed storage is enabled by default and the legacy storage is
 deprecated. If you haven't migrated yet, check the
 [migration instructions](raketasks/storage.md#migrate-to-hashed-storage).

doc/administration/snippets/index.md

@@ -29,7 +29,7 @@ This setting is not available through the [Admin Area settings](../../user/admin
 In order to configure this setting, use either the Rails console
 or the [Application settings API](../../api/settings.md).
 
-NOTE: **IMPORTANT:**
+NOTE:
 The value of the limit **must** be in bytes.
 
 #### Through the Rails console

doc/install/google_cloud_platform/index.md

@@ -10,7 +10,7 @@ type: howto
 
 This guide will help you install GitLab on a [Google Cloud Platform (GCP)](https://cloud.google.com/) instance.
 
-NOTE: **Alternative installation method:**
+NOTE:
 Google provides a whitepaper for [deploying production-ready GitLab on
 Google Kubernetes Engine](https://cloud.google.com/solutions/deploying-production-ready-gitlab-on-gke),
 including all steps and external resource configuration. These are an alternative to using a GCP VM, and use

doc/user/profile/active_sessions.md

@@ -32,7 +32,7 @@ exceeds 100, the oldest ones are deleted.
 1. Use the previous steps to navigate to **Active Sessions**.
 1. Click on **Revoke** besides a session. The current session cannot be revoked, as this would sign you out of GitLab.
 
-NOTE: **Note:**
+NOTE:
 When any session is revoked all **Remember me** tokens for all
 devices are revoked. See ['Why do I keep getting signed out?'](index.md#why-do-i-keep-getting-signed-out)
 for more information about the **Remember me** feature.

doc/user/project/deploy_boards.md

@@ -74,7 +74,7 @@ To display the Deploy Boards for a specific [environment](../../ci/environments/
 
 1. Have a Kubernetes cluster up and running.
 
-   NOTE: **Running on OpenShift:**
+   NOTE:
    If you are using OpenShift, ensure that you're using the `Deployment` resource
    instead of `DeploymentConfiguration`. Otherwise, the Deploy Boards won't render
    correctly. For more information, read the

doc/user/search/advanced_global_search.md

@@ -9,7 +9,7 @@ type: reference
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/109) in GitLab [Starter](https://about.gitlab.com/pricing/) 8.4.
 
-NOTE: **GitLab.com availability:**
+NOTE:
 Advanced Search (powered by Elasticsearch) is enabled for Bronze and above on GitLab.com since 2020-07-10.
 
 Leverage Elasticsearch for faster, more advanced code search across your entire

doc/user/search/advanced_search_syntax.md

@@ -9,7 +9,7 @@ type: reference
 
 > - Introduced in [GitLab Enterprise Starter](https://about.gitlab.com/pricing/) 9.2
 
-NOTE: **GitLab.com availability:**
+NOTE:
 Advanced Search (powered by Elasticsearch) is enabled for Bronze and above on GitLab.com since 2020-07-10.
 
 Use advanced queries for more targeted search results.