Add latest changes from gitlab-org/gitlab@master

13 files changed, 33 insertions, 33 deletions

diff --git a/doc/user/group/bulk_editing/index.md b/doc/user/group/bulk_editing/index.md
index 5c7538cb53e..8db9c7fd76c 100644
--- a/doc/user/group/bulk_editing/index.md
+++ b/doc/user/group/bulk_editing/index.md
@@ -6,14 +6,14 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # Bulk editing issues, epics, and merge requests at the group level **(PREMIUM)**
 
-NOTE: **Note:**
+NOTE:
 Bulk editing issues and merge requests is also available at the **project level**.
 For more details, see [Bulk editing issues and merge requests at the project level](../../project/bulk_editing.md).
 
 If you want to update attributes across multiple issues, epics, or merge requests in a group, you
 can do it by bulk editing them, that is, editing them together.
 
-NOTE: **Note:**
+NOTE:
 Only the items visible on the current page are selected for bulk editing (up to 20).
 
 ![Bulk editing](img/bulk-editing_v13_2.png)
@@ -22,7 +22,7 @@ Only the items visible on the current page are selected for bulk editing (up to
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/7249) in [GitLab Premium](https://about.gitlab.com/pricing/) 12.1.
 
-NOTE: **Note:**
+NOTE:
 You need a permission level of [Reporter or higher](../../permissions.md) to manage issues.
 
 When bulk editing issues in a group, you can edit the following attributes:
@@ -46,7 +46,7 @@ To update multiple project issues at the same time:
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/7250) in [GitLab Premium](https://about.gitlab.com/pricing/) 12.2.
 
-NOTE: **Note:**
+NOTE:
 You need a permission level of [Reporter or higher](../../permissions.md) to manage epics.
 
 When bulk editing epics in a group, you can edit their labels.
@@ -63,7 +63,7 @@ To update multiple epics at the same time:
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/12719) in [GitLab Premium](https://about.gitlab.com/pricing/) 12.2.
 
-NOTE: **Note:**
+NOTE:
 You need a permission level of [Developer or higher](../../permissions.md) to manage merge requests.
 
 When bulk editing merge requests in a group, you can edit the following attributes:
diff --git a/doc/user/group/custom_project_templates.md b/doc/user/group/custom_project_templates.md
index 7ec29a43fc6..639671c1345 100644
--- a/doc/user/group/custom_project_templates.md
+++ b/doc/user/group/custom_project_templates.md
@@ -20,7 +20,7 @@ To use a custom project template for a new project you need to:
 1. Edit your group's settings to look to your 'templates' subgroup for templates:
    1. In the left-hand menu, click **{settings}** **Settings > General**.
 
-      NOTE: **Note:**
+      NOTE:
       If you don't have access to the group's settings, you may not have sufficient privileges (for example, you may need developer or higher permissions).
 
    1. Scroll to **Custom project templates** and click **Expand**. If no **Custom project templates** section displays, make sure you've created a subgroup, and added a project (repository) to it.
@@ -56,7 +56,7 @@ gitlab.com/acmeco/
 Users can configure a GitLab group that serves as template
 source under a group's **Settings > General > Custom project templates**.
 
-NOTE: **Note:**
+NOTE:
 GitLab administrators can
 [set project templates for an entire GitLab instance](../admin_area/custom_project_templates.md).
 
@@ -66,7 +66,7 @@ available to every signed-in user, if all enabled [project features](../project/
 
 However, private projects will be available only if the user is a member of the project.
 
-NOTE: **Note:**
+NOTE:
 Only direct subgroups can be set as the template source. Projects of nested subgroups of a selected template source cannot be used.
 
 Repository and database information that are copied over to each new project are
diff --git a/doc/user/group/epics/index.md b/doc/user/group/epics/index.md
index bcd58d7834c..e87a5f4a801 100644
--- a/doc/user/group/epics/index.md
+++ b/doc/user/group/epics/index.md
@@ -20,7 +20,7 @@ An epic's page contains the following tabs:
   - Click the chevron (**>**) next to a parent epic to reveal the child epics and issues.
   - Hover over the total counts to see a breakdown of open and closed items.
 
-  NOTE: **Note:**
+  NOTE:
   The number provided here includes all epics associated with this project. The number includes epics for which users may not yet have permission.
 
 - **Roadmap**: a roadmap view of child epics which have start and due dates.
diff --git a/doc/user/group/epics/manage_epics.md b/doc/user/group/epics/manage_epics.md
index d623e663e5b..9cc7a35bc32 100644
--- a/doc/user/group/epics/manage_epics.md
+++ b/doc/user/group/epics/manage_epics.md
@@ -65,7 +65,7 @@ You can edit multiple epics at once. To learn how to do it, visit
 
 ## Delete an epic
 
-NOTE: **Note:**
+NOTE:
 To delete an epic, you need to be an [Owner](../../permissions.md#group-members-permissions) of a group/subgroup.
 
 When editing the description of an epic, select the **Delete** button to delete the epic.
@@ -141,7 +141,7 @@ The sort option and order is saved and used wherever you browse epics, including
 
 If you're working on items that contain private information, you can make an epic confidential.
 
-NOTE: **Note:**
+NOTE:
 A confidential epic can only contain confidential issues and confidential child epics.
 
 To make an epic confidential:
diff --git a/doc/user/group/index.md b/doc/user/group/index.md
index 5176d7c4e59..e7cc94ebd9f 100644
--- a/doc/user/group/index.md
+++ b/doc/user/group/index.md
@@ -226,7 +226,7 @@ To change this setting for a specific group:
 
 To change this setting globally, see [Default branch protection](../admin_area/settings/visibility_and_access_controls.md#default-branch-protection).
 
-NOTE: **Note:**
+NOTE:
 In [GitLab Premium or higher](https://about.gitlab.com/pricing/), GitLab administrators can choose to [disable group owners from updating the default branch protection](../admin_area/settings/visibility_and_access_controls.md#disable-group-owners-from-updating-default-branch-protection).
 
 ## Add projects to a group
@@ -342,7 +342,7 @@ Group links can be created using either a CN or a filter. These group links are
 
 For more information on the administration of LDAP and group sync, refer to the [main LDAP documentation](../../administration/auth/ldap/index.md#group-sync).
 
-NOTE: **Note:**
+NOTE:
 If an LDAP user is a group member when LDAP Synchronization is added, and they are not part of the LDAP group, they will be removed from the group.
 
 ### Creating group links via CN **(STARTER ONLY)**
@@ -482,7 +482,7 @@ To change your group path (group URL):
 1. Enter a new name under **Change group URL**.
 1. Click **Change group URL**.
 
-CAUTION: **Caution:**
+WARNING:
 It is currently not possible to rename a namespace if it contains a
 project with [Container Registry](../packages/container_registry/index.md) tags,
 because the project cannot be moved.
@@ -716,7 +716,7 @@ To enable delayed deletion of projects:
 1. Expand the **Permissions, LFS, 2FA** section, and check **Enable delayed project removal**.
 1. Click **Save changes**.
 
-NOTE: **Note:**
+NOTE:
 The group setting for delayed deletion is not inherited by sub-groups and has to be individually defined for each group.
 
 #### Prevent project forking outside group **(PREMIUM)**
diff --git a/doc/user/group/insights/index.md b/doc/user/group/insights/index.md
index a773e1a1974..b559e6806e9 100644
--- a/doc/user/group/insights/index.md
+++ b/doc/user/group/insights/index.md
@@ -40,7 +40,7 @@ more details about the `.gitlab/insights.yml` configuration file.
 
 If you have access to view a group, then you have access to view their Insights.
 
-NOTE: **Note:**
+NOTE:
 Issues or merge requests that you don't have access to (because you don't have
 access to the project they belong to, or because they are confidential) are
 filtered out of the Insights charts.
diff --git a/doc/user/group/iterations/index.md b/doc/user/group/iterations/index.md
index 8627f449e61..a06c7a8f325 100644
--- a/doc/user/group/iterations/index.md
+++ b/doc/user/group/iterations/index.md
@@ -38,7 +38,7 @@ From there you can create a new iteration or click an iteration to get a more de
 
 ## Create an iteration
 
-NOTE: **Note:**
+NOTE:
 You need Developer [permissions](../../permissions.md) or higher to create an iteration.
 
 To create an iteration:
@@ -52,7 +52,7 @@ To create an iteration:
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/218277) in [GitLab Starter](https://about.gitlab.com/pricing/) 13.2.
 
-NOTE: **Note:**
+NOTE:
 You need Developer [permissions](../../permissions.md) or higher to edit an iteration.
 
 To edit an iteration, click the three-dot menu (**{ellipsis_v}**) > **Edit iteration**.
diff --git a/doc/user/group/repositories_analytics/index.md b/doc/user/group/repositories_analytics/index.md
index 6530bcaac5c..3ba158cf6a1 100644
--- a/doc/user/group/repositories_analytics/index.md
+++ b/doc/user/group/repositories_analytics/index.md
@@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/215104) in [GitLab Premium](https://about.gitlab.com/pricing/) 13.4.
 
-CAUTION: **Warning:**
+WARNING:
 This feature might not be available to you. Check the **version history** note above for details.
 
 ## Latest project test coverage list
diff --git a/doc/user/group/saml_sso/group_managed_accounts.md b/doc/user/group/saml_sso/group_managed_accounts.md
index c3004e5e0f1..15dd91bece2 100644
--- a/doc/user/group/saml_sso/group_managed_accounts.md
+++ b/doc/user/group/saml_sso/group_managed_accounts.md
@@ -7,7 +7,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 # Group Managed Accounts **(PREMIUM)**
 
-CAUTION: **Caution:**
+WARNING:
 This [Closed Beta](https://about.gitlab.com/handbook/product/gitlab-the-product/#sts=Closed%20Beta) feature is being re-evaluated in favor of a different
 [identity model](https://gitlab.com/groups/gitlab-org/-/epics/4345) that does not require separate accounts.
 We recommend that group administrators who haven't yet implemented this feature wait for
diff --git a/doc/user/group/saml_sso/index.md b/doc/user/group/saml_sso/index.md
index cc9145b9e7b..f3824d44d35 100644
--- a/doc/user/group/saml_sso/index.md
+++ b/doc/user/group/saml_sso/index.md
@@ -45,7 +45,7 @@ GitLab.com uses the SAML NameID to identify users. The NameID element:
 The relevant field name and recommended value for supported providers are in the [provider specific notes](#providers).
 appropriate corresponding field.
 
-CAUTION: **Warning:**
+WARNING:
 Once users have signed into GitLab using the SSO SAML setup, changing the `NameID` breaks the configuration and potentially locks users out of the GitLab group.
 
 #### NameID Format
@@ -73,7 +73,7 @@ After you set up your identity provider to work with GitLab, you must configure
 
 ![Group SAML Settings for GitLab.com](img/group_saml_settings_v13_3.png)
 
-NOTE: **Note:**
+NOTE:
 Please note that the certificate [fingerprint algorithm](#additional-providers-and-setup-options) must be in SHA1. When configuring the identity provider, use a secure signature algorithm.
 
 ### SSO enforcement
@@ -92,7 +92,7 @@ When SSO enforcement is enabled for a group, users can't share a project in the
 
 ## Providers
 
-NOTE: **Note:**
+NOTE:
 GitLab is unable to provide support for IdPs that are not listed here.
 
 | Provider | Documentation |
@@ -240,7 +240,7 @@ Users can unlink SAML for a group from their profile page. This can be helpful i
 - You no longer want a group to be able to sign you in to GitLab.com.
 - Your SAML NameID has changed and so GitLab can no longer find your user.
 
-CAUTION: **Warning:**
+WARNING:
 Unlinking an account removes all roles assigned to that user within the group.
 If a user relinks their account, roles need to be reassigned.
 
diff --git a/doc/user/group/saml_sso/scim_setup.md b/doc/user/group/saml_sso/scim_setup.md
index 81bd8abff3f..d519864627c 100644
--- a/doc/user/group/saml_sso/scim_setup.md
+++ b/doc/user/group/saml_sso/scim_setup.md
@@ -92,14 +92,14 @@ You can then test the connection by clicking on **Test Connection**. If the conn
 
 1. Save your changes. For reference, you can view [an example configuration in the troubleshooting reference](../../../administration/troubleshooting/group_saml_scim.md#azure-active-directory).
 
-   NOTE: **Note:**
+   NOTE:
    If you used a unique identifier **other than** `objectId`, be sure to map it to `externalId`.
 
 1. Below the mapping list click on **Show advanced options > Edit attribute list for AppName**.
 
 1. Ensure the `id` is the primary and required field, and `externalId` is also required.
 
-   NOTE: **Note:**
+   NOTE:
    `username` should neither be primary nor required as we don't support
    that field on GitLab SCIM yet.
 
@@ -108,7 +108,7 @@ You can then test the connection by clicking on **Test Connection**. If the conn
 
    ![Provisioning status toggle switch](img/scim_provisioning_status.png)
 
-   NOTE: **Note:**
+   NOTE:
    You can control what is actually synced by selecting the `Scope`. For example,
    `Sync only assigned users and groups` only syncs the users assigned to
    the application (`Users and groups`), otherwise, it syncs the whole Active Directory.
@@ -116,7 +116,7 @@ You can then test the connection by clicking on **Test Connection**. If the conn
 Once enabled, the synchronization details and any errors appears on the
 bottom of the **Provisioning** screen, together with a link to the audit logs.
 
-CAUTION: **Warning:**
+WARNING:
 Once synchronized, changing the field mapped to `id` and `externalId` may cause a number of errors. These include provisioning errors, duplicate users, and may prevent existing users from accessing the GitLab group.
 
 ### Okta configuration steps
@@ -194,7 +194,7 @@ provider or users list for the specific app.
 
 Upon the next sync, the user is deprovisioned, which means that the user is removed from the group.
 
-NOTE: **Note:**
+NOTE:
 Deprovisioning does not delete the user account.
 
 ```mermaid
diff --git a/doc/user/group/settings/import_export.md b/doc/user/group/settings/import_export.md
index b0d705c3a04..fc0f0f16ded 100644
--- a/doc/user/group/settings/import_export.md
+++ b/doc/user/group/settings/import_export.md
@@ -55,7 +55,7 @@ The following items are **not** exported:
 - Runner tokens
 - SAML discovery tokens
 
-NOTE: **Note:**
+NOTE:
 For more details on the specific data persisted in a group export, see the
 [`import_export.yml`](https://gitlab.com/gitlab-org/gitlab/blob/master/lib/gitlab/import_export/group/import_export.yml) file.
 
@@ -75,7 +75,7 @@ For more details on the specific data persisted in a group export, see the
 1. Alternatively, you can come back to the project settings and download the
    file from there by clicking **Download export**, or generate a new file by clicking **Regenerate export**.
 
-NOTE: **Note:**
+NOTE:
 The maximum import file size can be set by the Administrator, default is 50MB.
 As an administrator, you can modify the maximum import file size. To do so, use the `max_import_size` option in the [Application settings API](../../../api/settings.md#change-application-settings) or the [Admin UI](../../admin_area/settings/account_and_limit_settings.md).
 
diff --git a/doc/user/group/subgroups/index.md b/doc/user/group/subgroups/index.md
index 926bc3d2c4e..be86e5cfa2b 100644
--- a/doc/user/group/subgroups/index.md
+++ b/doc/user/group/subgroups/index.md
@@ -159,10 +159,10 @@ this list using dropdown on the right side:
 
 ### Overriding the ancestor group membership
 
-NOTE: **Note:**
+NOTE:
 You must be an Owner of a group to be able to add members to it.
 
-NOTE: **Note:**
+NOTE:
 A user's permissions in a subgroup cannot be lower than in any of its ancestor groups.
 Therefore, you cannot reduce a user's permissions in a subgroup with respect to its ancestor groups.