Merge branch 'docs-image-alignment-2' into 'master'

Fix markdown spacing in various docs (part 4)

See merge request gitlab-org/gitlab-ce!31710

Author: axilleas

doc/user/group/index.md

@@ -91,11 +91,11 @@ To create a new Group, either:
 
 - In the top menu, click **Groups** and then **Your Groups**, and click the green button **New group**.
 
-    ![new group from groups page](img/new_group_from_groups.png)
+  ![new group from groups page](img/new_group_from_groups.png)
 
 - Or, in the top menu, expand the `plus` sign and choose **New group**.
 
-    ![new group from elsewhere](img/new_group_from_other_pages.png)
+  ![new group from elsewhere](img/new_group_from_other_pages.png)
 
 Add the following information:
 
@@ -104,15 +104,15 @@ Add the following information:
 1. The **Group name** will automatically populate the URL. Optionally, you can change it.
    This is the name that displays in group views.
    The name can contain only:
-     - Alphanumeric characters
-     - Underscores
-     - Dashes and dots
-     - Spaces
+   - Alphanumeric characters
+   - Underscores
+   - Dashes and dots
+   - Spaces
 1. The **Group URL** is the namespace under which your projects will be hosted.
    The URL can contain only:
-     - Alphanumeric characters
-     - Underscores
-     - Dashes and dots (it cannot start with dashes or end in a dot)
+   - Alphanumeric characters
+   - Underscores
+   - Dashes and dots (it cannot start with dashes or end in a dot)
 1. Optionally, you can add a brief description to tell others
    what this group is about.
 1. Optionally, choose an avatar for your group.
@@ -166,12 +166,12 @@ There are two different ways to add a new project to a group:
 
 - Select a group, and then click **New project**. You can then continue [creating your project](../../gitlab-basics/create-project.md).
 
-    ![New project](img/create_new_project_from_group.png)
+  ![New project](img/create_new_project_from_group.png)
 
 - While you are creating a project, select a group namespace
   you've already created from the dropdown menu.
 
-    ![Select group](img/select_group_dropdown.png)
+  ![Select group](img/select_group_dropdown.png)
 
 ### Default project-creation level
 

doc/user/group/saml_sso/scim_setup.md

@@ -90,11 +90,11 @@ You can then test the connection by clicking on **Test Connection**. If the conn
 1. Create a new mapping by clicking **Add New Mapping** then set **Source attribute** to `objectId`, and **Target attribute** to `externalId`.
 1. Click the `userPrincipalName` mapping and change **Match objects using this attribute** to `No`.
 
-    Save your changes and you should have the following configuration:
+   Save your changes and you should have the following configuration:
 
    ![Azure's attribute mapping configuration](img/scim_attribute_mapping.png)
 
-    NOTE: **Note:** If you used a unique identifier **other than** `objectId`, be sure to map it instead to both `id` and `externalId`.
+   NOTE: **Note:** If you used a unique identifier **other than** `objectId`, be sure to map it instead to both `id` and `externalId`.
 
 1. Below the mapping list click on **Show advanced options > Edit attribute list for AppName**.
 1. Leave the `id` as the primary and only required field.
@@ -108,7 +108,7 @@ You can then test the connection by clicking on **Test Connection**. If the conn
 1. Save all the screens and, in the **Provisioning** step, set
    the `Provisioning Status` to `On`.
 
-    ![Provisioning status toggle switch](img/scim_provisioning_status.png)
+   ![Provisioning status toggle switch](img/scim_provisioning_status.png)
 
    NOTE: **Note:**
    You can control what is actually synced by selecting the `Scope`. For example,

doc/user/project/file_lock.md

@@ -40,7 +40,7 @@ To lock a file:
 1. Pick the file you want to lock.
 1. Click the "Lock" button.
 
-    ![Locking file](img/file_lock.png)
+   ![Locking file](img/file_lock.png)
 
 To lock an entire directory, look for the "Lock" link next to "History".
 

doc/user/project/import/bitbucket.md

@@ -49,17 +49,17 @@ namespace that started the import process.
 
 1. Click on the "Bitbucket Cloud" button.
 
-    ![Bitbucket](img/import_projects_from_new_project_page.png)
+   ![Bitbucket](img/import_projects_from_new_project_page.png)
 
 1. Grant GitLab access to your Bitbucket account
 
-    ![Grant access](img/bitbucket_import_grant_access.png)
+   ![Grant access](img/bitbucket_import_grant_access.png)
 
 1. Click on the projects that you'd like to import or **Import all projects**.
    You can also select the namespace under which each project will be
    imported.
 
-    ![Import projects](img/bitbucket_import_select_project.png)
+   ![Import projects](img/bitbucket_import_select_project.png)
 
 [bb-import]: ../../../integration/bitbucket.md
 [social sign-in]: ../../profile/account/social_sign_in.md

doc/user/project/import/bitbucket_server.md

@@ -59,16 +59,16 @@ namespace that started the import process.
 1. Sign in to GitLab and go to your dashboard.
 1. Click on **New project**.
 1. Click on the "Bitbucket Server" button. If the button is not present, enable the importer in
-    **Admin > Application Settings > Visibility and access controls > Import sources**.
+   **Admin > Application Settings > Visibility and access controls > Import sources**.
 
-    ![Bitbucket](img/import_projects_from_new_project_page.png)
+   ![Bitbucket](img/import_projects_from_new_project_page.png)
 
 1. Enter your Bitbucket Server credentials.
 
-    ![Grant access](img/bitbucket_server_import_credentials.png)
+   ![Grant access](img/bitbucket_server_import_credentials.png)
 
 1. Click on the projects that you'd like to import or **Import all projects**.
    You can also select the namespace under which each project will be
    imported.
 
-    ![Import projects](img/bitbucket_server_import_select_project.png)
+   ![Import projects](img/bitbucket_server_import_select_project.png)

doc/user/project/import/gemnasium.md

@@ -5,13 +5,17 @@ instance or GitLab.com.
 
 ## Why is Gemnasium.com closed?
 
-Gemnasium has been [acquired by GitLab](https://about.gitlab.com/press/releases/2018-01-30-gemnasium-acquisition.html)
+Gemnasium was [acquired by GitLab](https://about.gitlab.com/press/releases/2018-01-30-gemnasium-acquisition.html)
 in January 2018. Since May 15, 2018, the services provided by Gemnasium are no longer available.
 The team behind Gemnasium has joined GitLab as the new Security Products team
-and is working on a wider range of tools than just Dependency Scanning:
-[SAST](../../application_security/sast/index.md),
-[DAST](../../application_security/dast/index.md),
-[Container Scanning](../../application_security/container_scanning/index.md) and more.
+and is working on a [wide range of tools](../../application_security/index.md),
+including:
+
+- [Dependency Scanning](../../application_security/dependency_scanning/index.md)
+- [SAST](../../application_security/sast/index.md)
+- [DAST](../../application_security/dast/index.md)
+- [Container Scanning](../../application_security/container_scanning/index.md)
+
 If you want to continue monitoring your dependencies, see the
 [Migrating to GitLab](#migrating-to-gitlab) section below.
 
@@ -57,44 +61,44 @@ back to both GitLab and GitHub when completed.
 
 1. Create a new project, and select the "CI/CD for external repo" tab:
 
-    ![Create new Project](img/gemnasium/create_project.png)
+   ![Create new Project](img/gemnasium/create_project.png)
 
 1. Use the "GitHub" button to connect your repositories.
 
-    ![Connect from GitHub](img/gemnasium/connect_github.png)
+   ![Connect from GitHub](img/gemnasium/connect_github.png)
 
 1. Select the project(s) to be set up with GitLab CI/CD and chose "Connect".
 
-    ![Select projects](img/gemnasium/select_project.png)
+   ![Select projects](img/gemnasium/select_project.png)
 
-    Once the configuration is done, you may click on your new
-    project on GitLab.
+   Once the configuration is done, you may click on your new
+   project on GitLab.
 
-    ![click on connected project](img/gemnasium/project_connected.png)
+   ![click on connected project](img/gemnasium/project_connected.png)
 
-    Your project is now mirrored on GitLab, where the Runners will be able to access
-    your source code and run your tests.
+   Your project is now mirrored on GitLab, where the Runners will be able to access
+   your source code and run your tests.
 
-    Optional step: If you set this up on GitLab.com, make sure the project is
-    public (in the project settings) if your GitHub project is public, since
-    the security feature is available only for [GitLab Ultimate](https://about.gitlab.com/pricing).
+   Optional step: If you set this up on GitLab.com, make sure the project is
+   public (in the project settings) if your GitHub project is public, since
+   the security feature is available only for [GitLab Ultimate](https://about.gitlab.com/pricing).
 
 1. To set up the dependency scanning job, corresponding to what Gemnasium was
    doing, you must create a `.gitlab-ci.yml` file, or update it according to
    the [dependency scanning docs](../../application_security/dependency_scanning/index.md).
    The mirroring is pull-only by default, so you may create or update the file on
    GitHub:
 
-    ![Edit gitlab-ci.yml file](img/gemnasium/edit_gitlab-ci.png)
+   ![Edit gitlab-ci.yml file](img/gemnasium/edit_gitlab-ci.png)
 
 1. Once your file has been committed, a new pipeline will be automatically
    triggered if your file is valid:
 
-    ![pipeline](img/gemnasium/pipeline.png)
+   ![pipeline](img/gemnasium/pipeline.png)
 
 1. The result of the job will be visible directly from the pipeline view:
 
-    ![security report](img/gemnasium/report.png)
+   ![security report](img/gemnasium/report.png)
 
 NOTE: **Note:**
 If you don't commit very often to your project, you may want to use

doc/user/project/import/manifest.md

@@ -1,7 +1,6 @@
 # Import multiple repositories by uploading a manifest file
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/28811) in
-GitLab 11.2.
+> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/28811) in GitLab 11.2.
 
 GitLab allows you to import all the required Git repositories
 based on a manifest file like the one used by the
@@ -56,4 +55,4 @@ You can start the import with:
    to the import status page with projects list based on the manifest file.
 1. Check the list and click **Import all repositories** to start the import.
 
-    ![Manifest status](img/manifest_status.png)
+   ![Manifest status](img/manifest_status.png)

doc/user/project/integrations/mattermost_slash_commands.md

@@ -40,17 +40,13 @@ the administrator console.
 1. Log in with an account that has admin privileges and navigate to the system
    console.
 
-    ![Mattermost go to console](img/mattermost_goto_console.png)
-
-    ---
+   ![Mattermost go to console](img/mattermost_goto_console.png)
 
 1. Click **Custom integrations** and set **Enable Custom Slash Commands**,
    **Enable custom integrations to override usernames**, and **Override
    custom integrations to override profile picture icons** to true
 
-    ![Mattermost console](img/mattermost_console_integrations.png)
-
-    ---
+   ![Mattermost console](img/mattermost_console_integrations.png)
 
 1. Click **Save** at the bottom to save the changes.
 
@@ -62,14 +58,12 @@ the administrator console.
    A screen will appear with all the values you need to copy in Mattermost as
    described in the next step. Leave the window open.
 
-    >**Note:**
-    GitLab will propose some values for the Mattermost settings. The only one
-    required to copy-paste as-is is the **Request URL**, all the others are just
-    suggestions.
-
-    ![Mattermost setup instructions](img/mattermost_config_help.png)
+   NOTE: **Note:**
+   GitLab will propose some values for the Mattermost settings. The only one
+   required to copy-paste as-is is the **Request URL**, all the others are just
+   suggestions.
 
-    ---
+   ![Mattermost setup instructions](img/mattermost_config_help.png)
 
 1. Proceed to the next step and create a slash command in Mattermost with the
    above values.
@@ -83,44 +77,38 @@ in a new slash command.
 1. Back to Mattermost, under your team page settings, you should see the
    **Integrations** option.
 
-    ![Mattermost team integrations](img/mattermost_team_integrations.png)
-
-    ---
+   ![Mattermost team integrations](img/mattermost_team_integrations.png)
 
 1. Go to the **Slash Commands** integration and add a new one by clicking the
    **Add Slash Command** button.
 
-    ![Mattermost add command](img/mattermost_add_slash_command.png)
-
-    ---
+   ![Mattermost add command](img/mattermost_add_slash_command.png)
 
 1. Fill in the options for the custom command as described in
    [step 2](#step-2-open-the-mattermost-slash-commands-service-in-gitlab).
 
-    >**Note:**
-    If you plan on connecting multiple projects, pick a slash command trigger
-    word that relates to your projects such as `/gitlab-project-name` or even
-    just `/project-name`. Only use `/gitlab` if you will only connect a single
-    project to your Mattermost team.
+   NOTE: **Note:**
+   If you plan on connecting multiple projects, pick a slash command trigger
+   word that relates to your projects such as `/gitlab-project-name` or even
+   just `/project-name`. Only use `/gitlab` if you will only connect a single
+   project to your Mattermost team.
 
-    ![Mattermost add command configuration](img/mattermost_slash_command_configuration.png)
+   ![Mattermost add command configuration](img/mattermost_slash_command_configuration.png)
 
 1. After you set up all the values, copy the token (we will use it below) and
    click **Done**.
 
-    ![Mattermost slash command token](img/mattermost_slash_command_token.png)
+   ![Mattermost slash command token](img/mattermost_slash_command_token.png)
 
 ### Step 4. Copy the Mattermost token into the Mattermost slash command service
 
 1. In GitLab, paste the Mattermost token you copied in the previous step and
    check the **Active** checkbox.
 
-    ![Mattermost copy token to GitLab](img/mattermost_gitlab_token.png)
+   ![Mattermost copy token to GitLab](img/mattermost_gitlab_token.png)
 
 1. Click **Save changes** for the changes to take effect.
 
----
-
 You are now set to start using slash commands in Mattermost that talk to the
 GitLab project you configured.
 

doc/user/project/integrations/redmine.md

@@ -5,18 +5,18 @@
    the **Redmine** service, and fill in the required details on the page as described
    in the table below.
 
-    | Field | Description |
-    | ----- | ----------- |
-    | `description`   | A name for the issue tracker (to differentiate between instances, for example) |
-    | `project_url`   | The URL to the project in Redmine which is being linked to this GitLab project |
-    | `issues_url`    | The URL to the issue in Redmine project that is linked to this GitLab project. Note that the `issues_url` requires `:id` in the URL. This ID is used by GitLab as a placeholder to replace the issue number. |
-    | `new_issue_url` | This is the URL to create a new issue in Redmine for the project linked to this GitLab project. **This is currently not being used and will be removed in a future release.** |
+   | Field | Description |
+   | ----- | ----------- |
+   | `description`   | A name for the issue tracker (to differentiate between instances, for example) |
+   | `project_url`   | The URL to the project in Redmine which is being linked to this GitLab project |
+   | `issues_url`    | The URL to the issue in Redmine project that is linked to this GitLab project. Note that the `issues_url` requires `:id` in the URL. This ID is used by GitLab as a placeholder to replace the issue number. |
+   | `new_issue_url` | This is the URL to create a new issue in Redmine for the project linked to this GitLab project. **This is currently not being used and will be removed in a future release.** |
 
-    Once you have configured and enabled Redmine you'll see the Redmine link on the GitLab project pages that takes you to the appropriate Redmine project.
+   Once you have configured and enabled Redmine you'll see the Redmine link on the GitLab project pages that takes you to the appropriate Redmine project.
 
-    As an example, below is a configuration for a project named gitlab-ci.
+   As an example, below is a configuration for a project named gitlab-ci.
 
-    ![Redmine configuration](img/redmine_configuration.png)
+   ![Redmine configuration](img/redmine_configuration.png)
 
 1. To disable the internal issue tracking system in a project, navigate to the General page, expand the [permissions](../settings/index.md#sharing-and-permissions) section and switch the **Issues** toggle to disabled.
 

doc/user/project/members/share_project_with_groups.md

@@ -20,18 +20,18 @@ To share 'Project Acme' with the 'Engineering' group:
 
 1. For 'Project Acme' use the left navigation menu to go to **Settings > Members**
 
-    ![share project with groups](img/share_project_with_groups.png)
+   ![share project with groups](img/share_project_with_groups.png)
 
 1. Select the 'Share with group' tab
 1. Add the 'Engineering' group with the maximum access level of your choice
 1. Click **Share** to share it
 
-    ![share project with groups tab](img/share_project_with_groups_tab.png)
+   ![share project with groups tab](img/share_project_with_groups_tab.png)
 
 1. After sharing 'Project Acme' with 'Engineering', the project will be listed
    on the group dashboard
 
-    !['Project Acme' is listed as a shared project for 'Engineering'](img/other_group_sees_shared_project.png)
+   !['Project Acme' is listed as a shared project for 'Engineering'](img/other_group_sees_shared_project.png)
 
 Note that you can only share a project with: