Resolve "CE documentation is not CommonMark compliant"

doc/user/project/repository/gpg_signed_commits/index.md

@@ -36,15 +36,16 @@ to be met:
 ## Generating a GPG key
->**Notes:**
-- If your Operating System has `gpg2` installed, replace `gpg` with `gpg2` in
-  the following commands.
-- If Git is using `gpg` and you get errors like `secret key not available` or
-  `gpg: signing failed: secret key not available`, run the following command to
-  change to `gpg2`:
-    ```
-    git config --global gpg.program gpg2
-    ```
+> **Notes:**
+> - If your Operating System has `gpg2` installed, replace `gpg` with `gpg2` in
+>   the following commands.
+> - If Git is using `gpg` and you get errors like `secret key not available` or
+>   `gpg: signing failed: secret key not available`, run the following command to
+>   change to `gpg2`:
+>
+>     ```
+>     git config --global gpg.program gpg2
+>    ```
 If you don't already have a GPG key, the following steps will help you get
 started:

doc/user/project/repository/reducing_the_repo_size_using_git.md

@@ -33,11 +33,10 @@ following method.
 ## Using `git filter-branch` to purge files
->
-**Warning:**
-Make sure to first make a copy of your repository since rewriting history will
-purge the files and information you are about to delete. Also make sure to
-inform any collaborators to not use `pull` after your changes, but use `rebase`.
+> **Warning:**
+> Make sure to first make a copy of your repository since rewriting history will
+> purge the files and information you are about to delete. Also make sure to
+> inform any collaborators to not use `pull` after your changes, but use `rebase`.
 1. Navigate to your repository:
@@ -71,10 +70,10 @@ inform any collaborators to not use `pull` after your changes, but use `rebase`.
 Your repository should now be below the size limit.
->**Note:**
-As an alternative to `filter-branch`, you can use the `bfg` tool with a
-command like: `bfg --delete-files path/to/big_file.mpg`. Read the
-[BFG Repo-Cleaner][bfg] documentation for more information.
+> **Note:**
+> As an alternative to `filter-branch`, you can use the `bfg` tool with a
+> command like: `bfg --delete-files path/to/big_file.mpg`. Read the
+> [BFG Repo-Cleaner][bfg] documentation for more information.
 [admin-repo-size]: https://docs.gitlab.com/ee/user/admin_area/settings/account_and_limit_settings.html#repository-size-limit
 [bfg]: https://rtyley.github.io/bfg-repo-cleaner/

doc/user/reserved_names.md

@@ -13,7 +13,7 @@ For a list of words that are not allowed to be used as group or project names, s
 It is currently not possible to create a project with the following names:
-- -
+- \-
 - badges
 - blame
 - blob
@@ -40,7 +40,7 @@ It is currently not possible to create a project with the following names:
 Currently the following names are reserved as top level groups:
 - 503.html
-- -
+- \-
 - .well-known
 - 404.html
 - 422.html
@@ -88,7 +88,7 @@ Currently the following names are reserved as top level groups:
 These group names are unavailable as subgroup names:
-- -
+- \-
 - activity
 - analytics
 - audit_events

doc/workflow/lfs/manage_large_binaries_with_git_lfs.md

@@ -61,11 +61,12 @@ git commit -am "Added Debian iso"     # commit the file meta data
 git push origin master                # sync the git repo and large file to the GitLab server
 ```
->**Note**: Make sure that `.gitattributes` is tracked by git. Otherwise Git
- LFS will not be working properly for people cloning the project.
- ```bash
- git add .gitattributes
- ```
+> **Note**: Make sure that `.gitattributes` is tracked by git. Otherwise Git
+> LFS will not be working properly for people cloning the project.
+>
+> ```bash
+> git add .gitattributes
+> ```
 Cloning the repository works the same as before. Git automatically detects the
 LFS-tracked files and clones them via HTTP. If you performed the git clone

doc/workflow/notifications.md

@@ -77,10 +77,8 @@ In most of the below cases, the notification will be sent to:
   - the author and assignee of the issue/merge request
   - authors of comments on the issue/merge request
   - anyone mentioned by `@username` in the issue/merge request title or description
-  - anyone mentioned by `@username` in any of the comments on the issue/merge request
-
-    ...with notification level "Participating" or higher
-
+  - anyone mentioned by `@username` in any of the comments on the issue/merge request  
+     ...with notification level "Participating" or higher
 - Watchers: users with notification level "Watch"
 - Subscribers: anyone who manually subscribed to the issue/merge request
 - Custom: Users with notification level "custom" who turned on notifications for any of the events present in the table below