Resolve "CE documentation is not CommonMark compliant"

doc/integration/omniauth.md

@@ -50,16 +50,16 @@ that are in common for all providers that we need to consider.
   be blocked by default and will have to be unblocked by an administrator before
   they are able to sign in.
->**Note:**
-If you set `block_auto_created_users` to `false`, make sure to only
-define providers under `allow_single_sign_on` that you are able to control, like
-SAML, Shibboleth, Crowd or Google, or set it to `false` otherwise any user on
-the Internet will be able to successfully sign in to your GitLab without
-administrative approval.
-
->**Note:**
-`auto_link_ldap_user` requires the `uid` of the user to be the same in both LDAP
-and the OmniAuth provider.
+> **Note:**
+> If you set `block_auto_created_users` to `false`, make sure to only
+> define providers under `allow_single_sign_on` that you are able to control, like
+> SAML, Shibboleth, Crowd or Google, or set it to `false` otherwise any user on
+> the Internet will be able to successfully sign in to your GitLab without
+> administrative approval.
+>
+> **Note:**
+> `auto_link_ldap_user` requires the `uid` of the user to be the same in both LDAP
+> and the OmniAuth provider.
 To change these settings:
@@ -233,15 +233,15 @@ You can enable profile syncing from selected OmniAuth providers and for all or f
 When authenticating using LDAP, the user's email is always synced.
- ```ruby
-   gitlab_rails['sync_profile_from_provider'] = ['twitter', 'google_oauth2']
-   gitlab_rails['sync_profile_attributes'] = ['name', 'email', 'location']
+```ruby
+  gitlab_rails['sync_profile_from_provider'] = ['twitter', 'google_oauth2']
+  gitlab_rails['sync_profile_attributes'] = ['name', 'email', 'location']
  ```
- **For installations from source**
- ```yaml
-   omniauth:
-     sync_profile_from_provider: ['twitter', 'google_oauth2']
-     sync_profile_attributes: ['email', 'location']
- ```
+**For installations from source**
+```yaml
+  omniauth:
+    sync_profile_from_provider: ['twitter', 'google_oauth2']
+    sync_profile_attributes: ['email', 'location']
+```

doc/integration/saml.md

@@ -123,9 +123,10 @@ in your SAML IdP:
 To ease configuration, most IdP accept a metadata URL for the application to provide
 configuration information to the IdP. To build the metadata URL for GitLab, append
 `users/auth/saml/metadata` to the HTTPS URL of your GitLab installation, for instance:
-   ```
-   https://gitlab.example.com/users/auth/saml/metadata
-   ```
+
+```
+https://gitlab.example.com/users/auth/saml/metadata
+```
 At a minimum the IdP *must* provide a claim containing the user's email address, using
 claim name `email` or `mail`. The email will be used to automatically generate the GitLab

doc/topics/git/numerous_undo_possibilities_in_git/index.md

@@ -41,10 +41,9 @@ Here's what we'll cover in this tutorial:
     - [Without history modification](#undo-remote-changes-without-changing-history) (preferred way)
     - [With history modification](#undo-remote-changes-with-modifying-history) (requires
       coordination with team and force pushes).
-
-      - [Usecases when modifying history is generally acceptable](#where-modifying-history-is-generally-acceptable)
-      - [How to modify history](#how-modifying-history-is-done)
-      - [How to remove sensitive information from repository](#deleting-sensitive-information-from-commits)
+       - [Usecases when modifying history is generally acceptable](#where-modifying-history-is-generally-acceptable)
+       - [How to modify history](#how-modifying-history-is-done)
+       - [How to remove sensitive information from repository](#deleting-sensitive-information-from-commits)
 ### Branching strategy
@@ -101,24 +100,23 @@ no changes added to commit (use "git add" and/or "git commit -a")
 At this point there are 3 options to undo the local changes you have:
- - Discard all local changes, but save them for possible re-use [later](#quickly-save-local-changes)
-
-     ```shell
-     git stash
-     ```
- - Discarding local changes (permanently) to a file
-     ```shell
-     git checkout -- <file>
-     ```
- - Discard all local changes to all files permanently
-     ```shell
-     git reset --hard
-     ```
+- Discard all local changes, but save them for possible re-use [later](#quickly-save-local-changes)
+    ```shell
+    git stash
+    ```
+- Discarding local changes (permanently) to a file
+    ```shell
+    git checkout -- <file>
+    ```
+- Discard all local changes to all files permanently
+    ```shell
+    git reset --hard
+    ```
 Before executing `git reset --hard`, keep in mind that there is also a way to
 just temporary store the changes without committing them using `git stash`.
@@ -140,10 +138,10 @@ them. This is achieved by Git stashing command `git stash`, which in fact saves
 current work and runs `git reset --hard`, but it also has various
 additional options like:
- - `git stash save`, which enables including temporary commit message, which will help you identify changes, among with other options
- - `git stash list`, which lists all previously stashed commits (yes, there can be more) that were not `pop`ed
- - `git stash pop`, which redoes previously stashed changes and removes them from stashed list
- - `git stash apply`, which redoes previously stashed changes, but keeps them on stashed list
+- `git stash save`, which enables including temporary commit message, which will help you identify changes, among with other options
+- `git stash list`, which lists all previously stashed commits (yes, there can be more) that were not `pop`ed
+- `git stash pop`, which redoes previously stashed changes and removes them from stashed list
+- `git stash apply`, which redoes previously stashed changes, but keeps them on stashed list
 ### Staged local changes (before you commit)
@@ -174,29 +172,29 @@ Changes to be committed:
 Now you have 4 options to undo your changes:
- - Unstage the file to current commit (HEAD)
-     ```shell
-     git reset HEAD <file>
-     ```
- - Unstage everything - retain changes
-     ```shell
-     git reset
-     ```
- - Discard all local changes, but save them for [later](#quickly-save-local-changes)
-     ```shell
-     git stash
-     ```
- - Discard everything permanently
-     ```shell
-     git reset --hard
-     ```
+- Unstage the file to current commit (HEAD)
+    ```shell
+    git reset HEAD <file>
+    ```
+- Unstage everything - retain changes
+    ```shell
+    git reset
+    ```
+- Discard all local changes, but save them for [later](#quickly-save-local-changes)
+    ```shell
+    git stash
+    ```
+- Discard everything permanently
+    ```shell
+    git reset --hard
+    ```
 ## Committed local changes
@@ -232,42 +230,42 @@ In our example we will end up with commit `B`, that introduced bug/error. We hav
 - Undo (swap additions and deletions) changes introduced by commit `B`.
-   ```shell
-   git revert commit-B-id
-   ```
+    ```shell
+    git revert commit-B-id
+    ```
 - Undo changes on a single file or directory from commit `B`, but retain them in the staged state
-   ```shell
-   git checkout commit-B-id <file>
-   ```
+    ```shell
+    git checkout commit-B-id <file>
+    ```
 - Undo changes on a single file or directory from commit `B`, but retain them in the unstaged state
-   ```shell
-   git reset  commit-B-id <file>
-   ```
-
- - There is one command we also must not forget: **creating a new branch**
-   from the point where changes are not applicable or where the development has hit a
-   dead end. For example you have done commits `A-B-C-D` on your feature-branch
-   and then you figure `C` and `D` are wrong. At this point you either reset to `B`
-   and do commit `F` (which will cause problems with pushing and if forced pushed also with other developers)
-   since branch now looks `A-B-F`, which clashes with what other developers have locally (you will
-   [change history](#with-history-modification)), or you simply checkout commit `B` create
-   a new branch and do commit `F`. In the last case, everyone else can still do their work while you
-   have your new way to get it right and merge it back in later. Alternatively, with GitLab,
-   you can [cherry-pick](../../../user/project/merge_requests/cherry_pick_changes.md#cherry-picking-a-commit)
-   that commit into a new merge request.
-
-      ![Create a new branch to avoid clashing](img/branching.png)
-
-      ```shell
-      git checkout commit-B-id
-      git checkout -b new-path-of-feature
-      # Create <commit F>
-      git commit -a
-      ```
+    ```shell
+    git reset  commit-B-id <file>
+    ```
+
+- There is one command we also must not forget: **creating a new branch**
+  from the point where changes are not applicable or where the development has hit a
+  dead end. For example you have done commits `A-B-C-D` on your feature-branch
+  and then you figure `C` and `D` are wrong. At this point you either reset to `B`
+  and do commit `F` (which will cause problems with pushing and if forced pushed also with other developers)
+  since branch now looks `A-B-F`, which clashes with what other developers have locally (you will
+  [change history](#with-history-modification)), or you simply checkout commit `B` create
+  a new branch and do commit `F`. In the last case, everyone else can still do their work while you
+  have your new way to get it right and merge it back in later. Alternatively, with GitLab,
+  you can [cherry-pick](../../../user/project/merge_requests/cherry_pick_changes.md#cherry-picking-a-commit)
+  that commit into a new merge request.
+
+    ![Create a new branch to avoid clashing](img/branching.png)
+
+    ```shell
+    git checkout commit-B-id
+    git checkout -b new-path-of-feature
+    # Create <commit F>
+    git commit -a
+    ```
 ### With history modification
@@ -287,9 +285,9 @@ delete commit `B`.
 - Rebase the range from current commit D to A:
-   ```shell
-   git rebase -i A
-   ```
+    ```shell
+    git rebase -i A
+    ```
 - Command opens your favorite editor where you write `drop` in front of commit
  `B`, but you leave default `pick` with all other commits. Save and exit the

doc/university/README.md

@@ -73,10 +73,10 @@ The curriculum is composed of GitLab videos, screencasts, presentations, project
 #### 1.7 Community and Support
 1. [Getting Help](https://about.gitlab.com/getting-help/)
-  - Proposing Features and Reporting and Tracking bugs for GitLab
-  - The GitLab IRC channel, Gitter Chat Room, Community Forum and Mailing List
-  - Getting Technical Support
-  - Being part of our Great Community and Contributing to GitLab
+   - Proposing Features and Reporting and Tracking bugs for GitLab
+   - The GitLab IRC channel, Gitter Chat Room, Community Forum and Mailing List
+   - Getting Technical Support
+   - Being part of our Great Community and Contributing to GitLab
 1. [Getting Started with the GitLab Development Kit (GDK)](https://about.gitlab.com/2016/06/08/getting-started-with-gitlab-development-kit/)
 1. [Contributing Technical Articles to the GitLab Blog](https://about.gitlab.com/2016/01/26/call-for-writers/)
 1. [GitLab Training Workshops](https://docs.gitlab.com/ce/university/training/end-user/)

doc/university/high-availability/aws/README.md

@@ -395,5 +395,5 @@ some redundancy options but it might also imply Geographic replication.
 There is a lot of ground yet to cover so have a read through these other
 resources and feel free to open an issue to request additional material.
- * [GitLab High Availability](http://docs.gitlab.com/ce/administration/high_availability/README.html#sts=High Availability)
- * [GitLab Geo](http://docs.gitlab.com/ee/gitlab-geo/README.html)  
+* [GitLab High Availability](http://docs.gitlab.com/ce/administration/high_availability/README.html#sts=High%20Availability)
+* [GitLab Geo](http://docs.gitlab.com/ee/gitlab-geo/README.html)  

doc/university/support/README.md

@@ -55,13 +55,13 @@ Sometimes we need to upgrade customers from old versions of GitLab to latest, so
   - Keep this up-to-date as patch and version releases become available, just like our customers would
 - Try out the following installation path
   - [Install GitLab 4.2 from source](https://gitlab.com/gitlab-org/gitlab-ce/blob/d67117b5a185cfb15a1d7e749588ff981ffbf779/doc/install/installation.md)
-    - External MySQL database
-    - External NGINX
+     - External MySQL database
+     - External NGINX
   - Create some test data
-    - Populated Repos
-    - Users
-    - Groups
-    - Projects
+     - Populated Repos
+     - Users
+     - Groups
+     - Projects
   - [Backup using our Backup rake task](https://docs.gitlab.com/ce/raketasks/backup_restore.html#create-a-backup-of-the-gitlab-system)
   - [Upgrade to 5.0 source using our Upgrade documentation](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/doc/update/4.2-to-5.0.md)
   - [Upgrade to 5.1 source](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/doc/update/5.0-to-5.1.md)
@@ -72,7 +72,7 @@ Sometimes we need to upgrade customers from old versions of GitLab to latest, so
   - [Upgrade to Omnibus 7.14](https://docs.gitlab.com/omnibus/update/README.html#upgrading-from-a-non-omnibus-installation-to-an-omnibus-installation)
   - [Restore backup using our Restore rake task](https://docs.gitlab.com/ce/raketasks/backup_restore.html#restore-a-previously-created-backup)
   - [Upgrade to latest EE](https://about.gitlab.com/downloads-ee)
-    - (GitLab inc. only) Acquire and apply a license for the Enterprise Edition product, ask in #support
+     - (GitLab inc. only) Acquire and apply a license for the Enterprise Edition product, ask in #support
 - Perform a downgrade from [EE to CE](https://docs.gitlab.com/ee/downgrade_ee_to_ce/README.html)
 #### Start to learn about some of the integrations that we support
@@ -98,9 +98,9 @@ Our integrations add great value to GitLab. User questions often relate to integ
   - [Environment Information and maintenance checks](https://docs.gitlab.com/ce/raketasks/maintenance.html)
   - [GitLab check](https://docs.gitlab.com/ce/raketasks/check.html)
   - Omnibus commands
-    - [Status](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/maintenance/README.md#get-service-status)
-    - [Starting and stopping services](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/maintenance/README.md#starting-and-stopping)
-    - [Starting a rails console](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/maintenance/README.md#invoking-rake-tasks)
+     - [Status](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/maintenance/README.md#get-service-status)
+     - [Starting and stopping services](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/maintenance/README.md#starting-and-stopping)
+     - [Starting a rails console](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/maintenance/README.md#invoking-rake-tasks)
 #### Learn about the Support process
@@ -118,16 +118,16 @@ Zendesk is our Support Centre and our main communication line with our Customers
   - Here you will find a large variety of queries mainly from our Users who are self hosting GitLab CE
   - Understand the questions that are asked and dig in to try to find a solution
   - [Proceed on to the GitLab.com Support Forum](https://about.gitlab.com/handbook/support/#gitlabcom-support-trackera-namesupp-foruma)
-    - Here you will find queries regarding our own GitLab.com
-    - Helping Users here will give you an understanding of our Admin interface and other tools
+     - Here you will find queries regarding our own GitLab.com
+     - Helping Users here will give you an understanding of our Admin interface and other tools
   - [Proceed on to the Twitter tickets in Zendesk](https://about.gitlab.com/handbook/support/#twitter)
-    - Here you will gain a great insight into our userbase
-    - Learn from any complaints and problems and feed them back to the team
-    - Tweets can range from help needed with GitLab installations, the API and just general queries
+     - Here you will gain a great insight into our userbase
+     - Learn from any complaints and problems and feed them back to the team
+     - Tweets can range from help needed with GitLab installations, the API and just general queries
   - [Proceed on to Regular email Support tickets](https://about.gitlab.com/handbook/support/#regular-zendesk-tickets-a-nameregulara)
-    - Here you will find tickets from our GitLab EE Customers and GitLab CE Users
-    - Tickets here are extremely varied and often very technical
-    - You should be prepared for these tickets, given the knowledge gained from previous tiers and your training
+     - Here you will find tickets from our GitLab EE Customers and GitLab CE Users
+     - Tickets here are extremely varied and often very technical
+     - You should be prepared for these tickets, given the knowledge gained from previous tiers and your training
 - Check out your colleagues' responses
   - Hop on to the #support-live-feed channel in Slack and see the tickets as they come in and are updated
   - Read through old tickets that your colleagues have worked on
@@ -135,10 +135,10 @@ Zendesk is our Support Centre and our main communication line with our Customers
   - [Learn about Cisco WebEx](https://about.gitlab.com/handbook/support/onboarding/#webexa-namewebexa)
   - Training calls
   - Information gathering calls
-    - It's good to find out how new and prospective customers are going to be using the product and how they will set up their infrastructure
+     - It's good to find out how new and prospective customers are going to be using the product and how they will set up their infrastructure
   - Diagnosis calls
-    - When email isn't enough we may need to hop on a call and do some debugging along side the customer
-    - These paired calls are a great learning experience
+     - When email isn't enough we may need to hop on a call and do some debugging along side the customer
+     - These paired calls are a great learning experience
   - Upgrade calls
   - Emergency calls

doc/university/training/topics/bisect.md

@@ -10,7 +10,7 @@ comments: false
 - Find a commit that introduced a bug
 - Works through a process of elimination
-- Specify a known good and bad revision to begin	  	
+- Specify a known good and bad revision to begin
 ----------

doc/university/training/topics/env_setup.md

@@ -16,10 +16,10 @@ comments: false
 - **Linux**
   ```bash
-    sudo yum install git-all
+  sudo yum install git-all
   ```
   ```bash
-    sudo apt-get install git-all
+  sudo apt-get install git-all
   ```
 ----------

doc/university/training/topics/getting_started.md

@@ -9,13 +9,15 @@ comments: false
 ## Instantiating Repositories
 * Create a new repository by instantiating it through
-```bash
-git init
-```
+
+    ```bash
+    git init
+    ```
 * Copy an existing project by cloning the repository through
-```bash
-git clone <url>
-```
+
+    ```bash
+    git clone <url>
+    ```
 ----------
@@ -24,17 +26,18 @@ git clone <url>
 * To instantiate a central repository a `--bare` flag is required.
 * Bare repositories don't allow file editing or committing changes.
 * Create a bare repo with
-```bash
-git init --bare project-name.git
-```
+
+    ```bash
+    git init --bare project-name.git
+    ```
 ----------
 ## Instantiate workflow with clone
 1. Create a project in your user namespace
-  - Choose to import from 'Any Repo by URL' and use
-    https://gitlab.com/gitlab-org/training-examples.git
+   - Choose to import from 'Any Repo by URL' and use
+     https://gitlab.com/gitlab-org/training-examples.git
 2. Create a '`Workspace`' directory in your home directory.
 3. Clone the '`training-examples`' project

doc/university/training/topics/git_add.md

@@ -11,27 +11,35 @@ comments: false
 Adds content to the index or staging area.
 * Adds a list of file
-```bash
-git add <files>
-```
+
+    ```bash
+    git add <files>
+    ```
+
 * Adds all files including deleted ones
-```bash
-git add -A
-```
+
+    ```bash
+    git add -A
+    ```
 ----------
 ## Git add continued
 * Add all text files in current dir
-```bash
-git add *.txt
-```
+
+    ```bash
+    git add *.txt
+    ```
+
 * Add all text file in the project
-```bash
-git add "*.txt*"
-```
+
+    ```bash
+    git add "*.txt*"
+    ```
+
 * Adds all files in directory
-```bash
-git add views/layouts/
-```
+
+    ```bash
+    git add views/layouts/
+    ```

doc/university/training/topics/git_log.md

@@ -9,31 +9,36 @@ comments: false
 Git log lists commit history. It allows searching and filtering.
 * Initiate log
-```
-git log
-```
+
+    ```
+    git log
+    ```
 * Retrieve set number of records:
-```
-git log -n 2
-```
+
+    ```
+    git log -n 2
+    ```
 * Search commits by author. Allows user name or a regular expression.
-```
-git log --author="user_name"
-```
+
+    ```
+    git log --author="user_name"
+    ```
 ----------
 * Search by comment message.
-```
-git log --grep="<pattern>"
-```
+
+    ```
+    git log --grep="<pattern>"
+    ```
 * Search by date
-```
-git log --since=1.month.ago --until=3.weeks.ago
-```
+
+    ```
+    git log --since=1.month.ago --until=3.weeks.ago
+    ```
 ----------

doc/university/training/topics/rollback_commits.md

@@ -9,26 +9,30 @@ comments: false
 ## Undo Commits
 * Undo last commit putting everything back into the staging area.
-```
-git reset --soft HEAD^
-```
+
+    ```
+    git reset --soft HEAD^
+    ```
 * Add files and change message with:
-```
-git commit --amend -m "New Message"
-```
+
+    ```
+    git commit --amend -m "New Message"
+    ```
 ----------
 * Undo last and remove changes
-```
-git reset --hard HEAD^
-```
+
+    ```
+    git reset --hard HEAD^
+    ```
 * Same as last one but for two commits back
-```
-git reset --hard HEAD^^
-```
+
+    ```
+    git reset --hard HEAD^^
+    ```
 ** Don't reset after pushing **

doc/university/training/topics/stash.md

@@ -10,50 +10,52 @@ We use git stash to store our changes when they are not ready to be committed
 and we need to change to a different branch.
 * Stash
-```
-git stash save
-# or
-git stash
-# or with a message
-git stash save "this is a message to display on the list"
-```
+
+    ```
+    git stash save
+    # or
+    git stash
+    # or with a message
+    git stash save "this is a message to display on the list"
+    ```
 * Apply stash to keep working on it
-```
-git stash apply
-# or apply a specific one from out stack
-git stash apply stash@{3}
-```
+
+    ```
+    git stash apply
+    # or apply a specific one from out stack
+    git stash apply stash@{3}
+    ```
 ----------
 * Every time we save a stash it gets stacked so by using list we can see all our
 stashes.
-```
-git stash list
-# or for more information (log methods)
-git stash list --stat
-```
+    ```
+    git stash list
+    # or for more information (log methods)
+    git stash list --stat
+    ```
 * To clean our stack we need to manually remove them.
-```
-# drop top stash
-git stash drop
-# or
-git stash drop <name>
-# to clear all history we can use
-git stash clear
-```
+    ```
+    # drop top stash
+    git stash drop
+    # or
+    git stash drop <name>
+    # to clear all history we can use
+    git stash clear
+    ```
 ----------
 * Apply and drop on one command
-```
-  git stash pop
-```
+    ```
+      git stash pop
+    ```
 * If we meet conflicts we need to either reset or commit our changes.

doc/university/training/topics/unstage.md

@@ -10,26 +10,27 @@ comments: false
 * To remove files from stage use reset HEAD. Where HEAD is the last commit of the current branch.
-```bash
-git reset HEAD <file>
-```
+    ```bash
+    git reset HEAD <file>
+    ```
 * This will unstage the file but maintain the modifications. To revert the file back to the state it was in before the changes we can use:
-```bash
-git checkout -- <file>
-```
+    ```bash
+    git checkout -- <file>
+    ```
 ----------
 * To remove a file from disk and repo use 'git rm' and to rm a dir use the '-r' flag.
-```
-git rm '*.txt'
-git rm -r <dirname>
-```
+    ```
+    git rm '*.txt'
+    git rm -r <dirname>
+    ```
 * If we want to remove a file from the repository but keep it on disk, say we forgot to add it to our `.gitignore` file then use `--cache`.
-```
-git rm <filename> --cache
-```
+
+    ```
+    git rm <filename> --cache
+    ```

doc/update/8.17-to-9.0.md

@@ -150,48 +150,48 @@ Update your current configuration as follows, replacing with your storages names
 1. Update your `gitlab.yml`, from
-  ```yaml
-  repositories:
-    storages: # You must have at least a 'default' storage path.
-      default: /home/git/repositories
-      nfs: /mnt/nfs/repositories
-      cephfs: /mnt/cephfs/repositories
-  ```
-
-  to
-
-  ```yaml
-  repositories:
-    storages: # You must have at least a 'default' storage path.
-      default:
-        path: /home/git/repositories
-      nfs:
-        path: /mnt/nfs/repositories
-      cephfs:
-        path: /mnt/cephfs/repositories
-  ```
+    ```yaml
+    repositories:
+      storages: # You must have at least a 'default' storage path.
+        default: /home/git/repositories
+        nfs: /mnt/nfs/repositories
+        cephfs: /mnt/cephfs/repositories
+    ```
+
+    to
+
+    ```yaml
+    repositories:
+      storages: # You must have at least a 'default' storage path.
+        default:
+          path: /home/git/repositories
+        nfs:
+          path: /mnt/nfs/repositories
+        cephfs:
+          path: /mnt/cephfs/repositories
+    ```
 **For Omnibus installations**
 1. Update your `/etc/gitlab/gitlab.rb`, from
-  ```ruby
-  git_data_dirs({
-    "default" => "/var/opt/gitlab/git-data",
-    "nfs" => "/mnt/nfs/git-data",
-    "cephfs" => "/mnt/cephfs/git-data"
-  })
-  ```
-
-  to
-
-  ```ruby
-  git_data_dirs({
-    "default" => { "path" => "/var/opt/gitlab/git-data" },
-    "nfs" => { "path" => "/mnt/nfs/git-data" },
-    "cephfs" => { "path" => "/mnt/cephfs/git-data" }
-  })
-  ```
+    ```ruby
+    git_data_dirs({
+      "default" => "/var/opt/gitlab/git-data",
+      "nfs" => "/mnt/nfs/git-data",
+      "cephfs" => "/mnt/cephfs/git-data"
+    })
+    ```
+
+    to
+
+    ```ruby
+    git_data_dirs({
+      "default" => { "path" => "/var/opt/gitlab/git-data" },
+      "nfs" => { "path" => "/mnt/nfs/git-data" },
+      "cephfs" => { "path" => "/mnt/cephfs/git-data" }
+    })
+    ```
 #### Git configuration

doc/update/9.0-to-9.1.md

@@ -150,48 +150,48 @@ Update your current configuration as follows, replacing with your storages names
 1. Update your `gitlab.yml`, from
-  ```yaml
-  repositories:
-    storages: # You must have at least a 'default' storage path.
-      default: /home/git/repositories
-      nfs: /mnt/nfs/repositories
-      cephfs: /mnt/cephfs/repositories
-  ```
-
-  to
-
-  ```yaml
-  repositories:
-    storages: # You must have at least a 'default' storage path.
-      default:
-        path: /home/git/repositories
-      nfs:
-        path: /mnt/nfs/repositories
-      cephfs:
-        path: /mnt/cephfs/repositories
-  ```
+    ```yaml
+    repositories:
+      storages: # You must have at least a 'default' storage path.
+        default: /home/git/repositories
+        nfs: /mnt/nfs/repositories
+        cephfs: /mnt/cephfs/repositories
+    ```
+
+    to
+
+    ```yaml
+    repositories:
+      storages: # You must have at least a 'default' storage path.
+        default:
+          path: /home/git/repositories
+        nfs:
+          path: /mnt/nfs/repositories
+        cephfs:
+          path: /mnt/cephfs/repositories
+    ```
 **For Omnibus installations**
 1. Update your `/etc/gitlab/gitlab.rb`, from
-
-  ```ruby
-  git_data_dirs({
-    "default" => "/var/opt/gitlab/git-data",
-    "nfs" => "/mnt/nfs/git-data",
-    "cephfs" => "/mnt/cephfs/git-data"
-  })
-  ```
-
-  to
-
-  ```ruby
-  git_data_dirs({
-    "default" => { "path" => "/var/opt/gitlab/git-data" },
-    "nfs" => { "path" => "/mnt/nfs/git-data" },
-    "cephfs" => { "path" => "/mnt/cephfs/git-data" }
-  })
-  ```
+  
+    ```ruby
+    git_data_dirs({
+      "default" => "/var/opt/gitlab/git-data",
+      "nfs" => "/mnt/nfs/git-data",
+      "cephfs" => "/mnt/cephfs/git-data"
+    })
+    ```
+  
+    to
+  
+    ```ruby
+    git_data_dirs({
+      "default" => { "path" => "/var/opt/gitlab/git-data" },
+      "nfs" => { "path" => "/mnt/nfs/git-data" },
+      "cephfs" => { "path" => "/mnt/cephfs/git-data" }
+    })
+    ```
 #### Git configuration

doc/user/admin_area/monitoring/health_check.md

 # Health Check
->**Notes:**
-  - Liveness and readiness probes were [introduced][ce-10416] in GitLab 9.1.
-  - The `health_check` endpoint was [introduced][ce-3888] in GitLab 8.8 and will
-    be deprecated in GitLab 9.1. Read more in the [old behavior](#old-behavior)
-    section.
-  - [Access token](#access-token) has been deprecated in GitLab 9.4
-    in favor of [IP whitelist](#ip-whitelist)
+> **Notes:**
+>   - Liveness and readiness probes were [introduced][ce-10416] in GitLab 9.1.
+>   - The `health_check` endpoint was [introduced][ce-3888] in GitLab 8.8 and will
+>     be deprecated in GitLab 9.1. Read more in the [old behavior](#old-behavior)
+>     section.
+>   - [Access token](#access-token) has been deprecated in GitLab 9.4
+>     in favor of [IP whitelist](#ip-whitelist)
 GitLab provides liveness and readiness probes to indicate service health and
 reachability to required services. These probes report on the status of the

doc/user/award_emojis.md

 # Award emoji
->**Notes:**
-- First [introduced][1825] in GitLab 8.2.
-- GitLab 9.0 [introduced][ce-9570] the usage of native emojis if the platform
-  supports them and falls back to images or CSS sprites. This change greatly
-  improved the award emoji performance overall.
+> **Notes:**
+> - First [introduced][1825] in GitLab 8.2.
+> - GitLab 9.0 [introduced][ce-9570] the usage of native emojis if the platform
+>  supports them and falls back to images or CSS sprites. This change greatly
+>  improved the award emoji performance overall.
 When you're collaborating online, you get fewer opportunities for high-fives
 and thumbs-ups. Emoji can be awarded to issues, merge requests, snippets, and

doc/user/discussions/index.md

@@ -23,9 +23,9 @@ in the form of a resolvable or threaded discussion.
 ## Resolvable discussions
->**Notes:**
-- The main feature was [introduced][ce-5022] in GitLab 8.11.
-- Resolvable discussions can be added only to merge request diffs.
+> **Notes:**
+> - The main feature was [introduced][ce-5022] in GitLab 8.11.
+> - Resolvable discussions can be added only to merge request diffs.
 Discussion resolution helps keep track of progress during planning or code review.
 Resolving comments prevents you from forgetting to address feedback and lets you

doc/user/group/index.md

@@ -22,14 +22,14 @@ group and grant access to all their projects at once
 - Create a group, include members of your team, and make it easier to
 `@mention` all the team at once in issues and merge requests
   - Create a group for your company members, and create [subgroups](subgroups/index.md)
-  for each individual team. Let's say you create a group called `company-team`, and among others,
-      you created subgroups in this group for each individual team `backend-team`,
-      `frontend-team`, and `production-team`:
-        1. When you start a new implementation from an issue, you add a comment:
+    for each individual team. Let's say you create a group called `company-team`, and among others,
+    you created subgroups in this group for each individual team `backend-team`,
+    `frontend-team`, and `production-team`:
+     1. When you start a new implementation from an issue, you add a comment:
         _"`@company-team`, let's do it! `@company-team/backend-team` you're good to go!"_
-        1. When your backend team needs help from frontend, they add a comment:
+     1. When your backend team needs help from frontend, they add a comment:
         _"`@company-team/frontend-team` could you help us here please?"_
-        1. When the frontend team completes their implementation, they comment:
+     1. When the frontend team completes their implementation, they comment:
         _"`@company-team/backend-team`, it's done! Let's ship it `@company-team/production-team`!"_
 ## Namespaces
@@ -64,8 +64,8 @@ together in a single list view.
 ## Create a new group
 > **Notes:**
-- For a list of words that are not allowed to be used as group names see the
-  [reserved names](../reserved_names.md).
+> - For a list of words that are not allowed to be used as group names see the
+>   [reserved names](../reserved_names.md).
 You can create a group in GitLab from: