Resolve "CE documentation is not CommonMark compliant"

4 files changed, 37 insertions, 36 deletions

diff --git a/doc/integration/azure.md b/doc/integration/azure.md
index f3c9c498634..634dd952448 100644
--- a/doc/integration/azure.md
+++ b/doc/integration/azure.md
@@ -2,7 +2,7 @@
 
 To enable the Microsoft Azure OAuth2 OmniAuth provider you must register your application with Azure. Azure will generate a client ID and secret key for you to use.
 
-1.  Sign in to the [Azure Management Portal](https://manage.windowsazure.com>).
+1.  Sign in to the [Azure Management Portal](https://manage.windowsazure.com).
 
 1.  Select "Active Directory" on the left and choose the directory you want to use to register GitLab.
 
diff --git a/doc/integration/oauth2_generic.md b/doc/integration/oauth2_generic.md
index e71706fef7d..3e72589ce12 100644
--- a/doc/integration/oauth2_generic.md
+++ b/doc/integration/oauth2_generic.md
@@ -24,11 +24,11 @@ This strategy is designed to allow configuration of the simple OmniAuth SSO proc
 
 1. Register your application in the OAuth2 provider you wish to authenticate with.
 
-   The redirect URI you provide when registering the application should be:
+    The redirect URI you provide when registering the application should be:
 
-   ```
-   http://your-gitlab.host.com/users/auth/oauth2_generic/callback
-   ```
+    ```
+    http://your-gitlab.host.com/users/auth/oauth2_generic/callback
+    ```
 
 1. You should now be able to get a Client ID and Client Secret.
    Where this shows up will differ for each provider.
@@ -36,18 +36,18 @@ This strategy is designed to allow configuration of the simple OmniAuth SSO proc
 
 1. On your GitLab server, open the configuration file.
 
-   For Omnibus package:
+    For Omnibus package:
 
-   ```sh
-   sudo editor /etc/gitlab/gitlab.rb
-   ```
+    ```sh
+    sudo editor /etc/gitlab/gitlab.rb
+    ```
 
-   For installations from source:
+    For installations from source:
 
-   ```sh
-   cd /home/git/gitlab
-   sudo -u git -H editor config/gitlab.yml
-   ```
+    ```sh
+    cd /home/git/gitlab
+    sudo -u git -H editor config/gitlab.yml
+    ```
 
 1. See [Initial OmniAuth Configuration](omniauth.md#initial-omniauth-configuration) for initial settings
 
diff --git a/doc/integration/omniauth.md b/doc/integration/omniauth.md
index 82e8fbdb93e..361769c4e25 100644
--- a/doc/integration/omniauth.md
+++ b/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**
+**For installations from source**
 
- ```yaml
-   omniauth:
-     sync_profile_from_provider: ['twitter', 'google_oauth2']
-     sync_profile_attributes: ['email', 'location']
- ```
+```yaml
+  omniauth:
+    sync_profile_from_provider: ['twitter', 'google_oauth2']
+    sync_profile_attributes: ['email', 'location']
+```
diff --git a/doc/integration/saml.md b/doc/integration/saml.md
index 25f396bc9c4..e2eea57d694 100644
--- a/doc/integration/saml.md
+++ b/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