Remove extra blank lines from docs

Removing extra blank lines in docs that serve
no purpose, as well as some --- lines that also
are not needed.

8 files changed, 31 insertions, 76 deletions

diff --git a/doc/user/application_security/license_management/index.md b/doc/user/application_security/license_management/index.md
index a2a9612286a..b0eb753938b 100644
--- a/doc/user/application_security/license_management/index.md
+++ b/doc/user/application_security/license_management/index.md
@@ -196,11 +196,12 @@ To approve or blacklist a license:
 1. Click the **Add a license** button.
 
    ![License Management Add License](img/license_management_add_license.png)
+
 1. In the **License name** dropdown, either:
-    - Select one of the available licenses. You can search for licenses in the field
-   at the top of the list.
-    - Enter arbitrary text in the field at the top of the list. This will cause the text to be
-    added as a license name to the list.
+   - Select one of the available licenses. You can search for licenses in the field
+     at the top of the list.
+   - Enter arbitrary text in the field at the top of the list. This will cause the text to be
+     added as a license name to the list.
 1. Select the **Approve** or **Blacklist** radio button to approve or blacklist respectively
    the selected license.
 
diff --git a/doc/user/project/issues/csv_export.md b/doc/user/project/issues/csv_export.md
index 0b7a7af5927..d3f53c09fb3 100644
--- a/doc/user/project/issues/csv_export.md
+++ b/doc/user/project/issues/csv_export.md
@@ -48,7 +48,6 @@ Exported issues are always sorted by `Issue ID`.
 
 Data will be encoded with a comma as the column delimiter, with `"` used to quote fields if needed, and newlines to separate rows. The first row will be the headers, which are listed in the following table along with a description of the values:
 
-
 | Column  | Description |
 |---------|-------------|
 | Issue ID | Issue `iid` |
@@ -71,7 +70,6 @@ Data will be encoded with a comma as the column delimiter, with `"` used to quot
 | Time Estimate | [Time estimate](../../../workflow/time_tracking.md#estimates) in seconds |
 | Time Spent | [Time spent](../../../workflow/time_tracking.md#time-spent) in seconds |
 
-
 ## Limitations
 
 As the issues will be sent as an email attachment, there is a limit on how much data can be exported. Currently this limit is 20MB to ensure successful delivery across a range of email providers. If this limit is reached we suggest narrowing the search before export, perhaps by exporting open and closed issues separately.
diff --git a/doc/user/project/members/index.md b/doc/user/project/members/index.md
index 2a490e3fd7f..e343fd45488 100644
--- a/doc/user/project/members/index.md
+++ b/doc/user/project/members/index.md
@@ -10,8 +10,6 @@ or import a new user to your project.
 To view, edit, add, and remove project's members, go to your
 project's **Settings > Members**.
 
----
-
 ## Add a user
 
 Right next to **People**, start typing the name or username of the user you
@@ -19,22 +17,16 @@ want to add.
 
 ![Search for people](img/add_user_search_people.png)
 
----
-
 Select the user and the [permission level](../../permissions.md)
 that you'd like to give the user. Note that you can select more than one user.
 
 ![Give user permissions](img/add_user_give_permissions.png)
 
----
-
 Once done, hit **Add users to project** and they will be immediately added to
 your project with the permissions you gave them above.
 
 ![List members](img/add_user_list_members.png)
 
----
-
 From there on, you can either remove an existing user or change their access
 level to the project.
 
@@ -47,8 +39,6 @@ In the dropdown menu, you can see only the projects you are Maintainer on.
 
 ![Import members from another project](img/add_user_import_members_from_another_project.png)
 
----
-
 Select the one you want and hit **Import project members**. A flash message
 notifying you that the import was successful will appear, and the new members
 are now in the project's members list. Notice that the permissions that they
@@ -56,8 +46,6 @@ had on the project you imported from are retained.
 
 ![Members list of new members](img/add_user_imported_members.png)
 
----
-
 ## Invite people using their e-mail address
 
 If a user you want to give access to doesn't have an account on your GitLab
@@ -66,23 +54,17 @@ user search field.
 
 ![Invite user by mail](img/add_user_email_search.png)
 
----
-
 As you can imagine, you can mix inviting multiple people and adding existing
 GitLab users to the project.
 
 ![Invite user by mail ready to submit](img/add_user_email_ready.png)
 
----
-
 Once done, hit **Add users to project** and watch that there is a new member
 with the e-mail address we used above. From there on, you can resend the
 invitation, change their access level, or even delete them.
 
 ![Invite user members list](img/add_user_email_accept.png)
 
----
-
 Once the user accepts the invitation, they will be prompted to create a new
 GitLab account using the same e-mail address the invitation was sent to.
 
@@ -97,15 +79,11 @@ side of your screen.
 
 ![Request access button](img/request_access_button.png)
 
----
-
 Project owners & maintainers will be notified of your request and will be able to approve or
 decline it on the members page.
 
 ![Manage access requests](img/access_requests_management.png)
 
----
-
 If you change your mind before your request is approved, just click the
 **Withdraw Access Request** button.
 
diff --git a/doc/user/project/new_ci_build_permissions_model.md b/doc/user/project/new_ci_build_permissions_model.md
index d35a8568394..494dd539da7 100644
--- a/doc/user/project/new_ci_build_permissions_model.md
+++ b/doc/user/project/new_ci_build_permissions_model.md
@@ -6,8 +6,6 @@ GitLab 8.12 has a completely redesigned [job permissions] system. You can find
 all discussion and all our concerns when choosing the current approach in issue
 [#18994](https://gitlab.com/gitlab-org/gitlab-ce/issues/18994).
 
----
-
 Jobs permissions should be tightly integrated with the permissions of a user
 who is triggering a job.
 
@@ -108,8 +106,6 @@ and to checkout project sources.
 It could also be used with the GitLab Container Registry for that project,
 allowing pulling and pushing Docker images from within the CI job.
 
----
-
 GitLab would create a special checkout URL like:
 
 ```
diff --git a/doc/user/project/pipelines/job_artifacts.md b/doc/user/project/pipelines/job_artifacts.md
index 1966b136e9d..2411744c874 100644
--- a/doc/user/project/pipelines/job_artifacts.md
+++ b/doc/user/project/pipelines/job_artifacts.md
@@ -67,8 +67,6 @@ artifacts in case you changed your mind and want to keep them.
 
 ![Job artifacts browser button](img/job_artifacts_browser_button.png)
 
----
-
 The archive browser shows the name and the actual file size of each file in the
 archive. If your artifacts contained directories, then you are also able to
 browse inside them.
@@ -80,8 +78,6 @@ one HTML file that you can view directly online when
 
 ![Job artifacts browser](img/job_artifacts_browser.png)
 
----
-
 ## Downloading artifacts
 
 If you need to download the whole archive, there are buttons in various places
@@ -90,22 +86,22 @@ inside GitLab that make that possible.
 1. While on the pipelines page, you can see the download icon for each job's
    artifacts archive in the right corner:
 
-    ![Job artifacts in Pipelines page](img/job_artifacts_pipelines_page.png)
+   ![Job artifacts in Pipelines page](img/job_artifacts_pipelines_page.png)
 
 1. While on the **Jobs** page, you can see the download icon for each job's
    artifacts archive in the right corner:
 
-    ![Job artifacts in Builds page](img/job_artifacts_builds_page.png)
+   ![Job artifacts in Builds page](img/job_artifacts_builds_page.png)
 
 1. While inside a specific job, you are presented with a download button
    along with the one that browses the archive:
 
-    ![Job artifacts browser button](img/job_artifacts_browser_button.png)
+   ![Job artifacts browser button](img/job_artifacts_browser_button.png)
 
 1. And finally, when browsing an archive you can see the download button at
    the top right corner:
 
-    ![Job artifacts browser](img/job_artifacts_browser.png)
+   ![Job artifacts browser](img/job_artifacts_browser.png)
 
 ## Downloading the latest artifacts
 
diff --git a/doc/user/project/repository/web_editor.md b/doc/user/project/repository/web_editor.md
index 253e5374f52..0116f0fe7ca 100644
--- a/doc/user/project/repository/web_editor.md
+++ b/doc/user/project/repository/web_editor.md
@@ -13,8 +13,6 @@ Choose **New file** from the dropdown.
 
 ![New file dropdown menu](img/web_editor_new_file_dropdown.png)
 
----
-
 Enter a file name in the **File name** box. Then, add file content in the editor
 area. Add a descriptive commit message and choose a branch. The branch field
 will default to the branch you were viewing in the file browser. If you enter
@@ -59,8 +57,6 @@ selector. Choose **Upload file** from the dropdown.
 
 ![Upload file dropdown menu](img/web_editor_upload_file_dropdown.png)
 
----
-
 Once the upload dialog pops up there are two ways to upload your file. Either
 drag and drop a file on the pop up or use the **click to upload** link. A file
 preview will appear once you have selected a file to upload.
@@ -80,8 +76,6 @@ Choose **New directory** from the dropdown.
 
 ![New directory dropdown](img/web_editor_new_directory_dropdown.png)
 
----
-
 In the new directory dialog enter a directory name, a commit message and choose
 the target branch. Click **Create directory** to finish.
 
@@ -129,8 +123,6 @@ choose **New branch** from the dropdown.
 
 ![New branch dropdown](img/web_editor_new_branch_dropdown.png)
 
----
-
 Enter a new **Branch name**. Optionally, change the **Create from** field
 to choose which branch, tag or commit SHA this new branch will originate from.
 This field will autocomplete if you start typing an existing branch or tag.
@@ -139,8 +131,6 @@ branch.
 
 ![New branch page](img/web_editor_new_branch_page.png)
 
----
-
 You can now make changes to any files, as needed. When you're ready to merge
 the changes back to master you can use the widget at the top of the screen.
 This widget only appears for a period of time after you create the branch or
@@ -156,8 +146,6 @@ SHA. From a project's files page, choose **New tag** from the dropdown.
 
 ![New tag dropdown](img/web_editor_new_tag_dropdown.png)
 
----
-
 Give the tag a name such as `v1.0.0`. Choose the branch or SHA from which you
 would like to create this new tag. You can optionally add a message and
 release notes. The release notes section supports markdown format and you can
diff --git a/doc/user/project/service_desk.md b/doc/user/project/service_desk.md
index f899120f0c2..645b9bffcc1 100644
--- a/doc/user/project/service_desk.md
+++ b/doc/user/project/service_desk.md
@@ -53,36 +53,35 @@ Service Desk is enabled on GitLab.com. If you're a
 [Silver subscriber](https://about.gitlab.com/gitlab-com/),
 you can skip the step 1 below; you only need to enable it per project.
 
-1.   [Set up incoming email](../../administration/incoming_email.md#set-it-up) for the GitLab instance. This must
-     support [email sub-addressing](../../administration/incoming_email.md#email-sub-addressing).
-2.   Navigate to your project's **Settings** and scroll down to the **Service Desk**
-     section.
-3.   If you have the correct access and an Premium license,
-     you will see an option to set up Service Desk:
+1. [Set up incoming email](../../administration/incoming_email.md#set-it-up) for the GitLab instance. This must
+   support [email sub-addressing](../../administration/incoming_email.md#email-sub-addressing).
+1. Navigate to your project's **Settings** and scroll down to the **Service Desk**
+   section.
+1. If you have the correct access and an Premium license,
+   you will see an option to set up Service Desk:
 
-     ![Activate Service Desk option](img/service_desk_disabled.png)
+   ![Activate Service Desk option](img/service_desk_disabled.png)
 
-4.   Checking that box will enable Service Desk for the project, and show a
-     unique email address to email issues to the project. These issues will be
-     [confidential](issues/confidential_issues.md), so they will only be visible to project members.
+1. Checking that box will enable Service Desk for the project, and show a
+   unique email address to email issues to the project. These issues will be
+   [confidential](issues/confidential_issues.md), so they will only be visible to project members.
 
-     **Warning**: this email address can be used by anyone to create an issue on
-     this project, whether or not they have access to your GitLab instance.
-     We recommend **putting this behind an alias** so that it can be changed if
-     needed, and **[enabling Akismet](../../integration/akismet.md)** on your GitLab instance to add spam
-     checking to this service.  Unblocked email spam would result in many spam
-     issues being created, and may disrupt your GitLab service.
+   **Warning**: this email address can be used by anyone to create an issue on
+   this project, whether or not they have access to your GitLab instance.
+   We recommend **putting this behind an alias** so that it can be changed if
+   needed, and **[enabling Akismet](../../integration/akismet.md)** on your GitLab instance to add spam
+   checking to this service.  Unblocked email spam would result in many spam
+   issues being created, and may disrupt your GitLab service.
 
-     ![Service Desk enabled](img/service_desk_enabled.png)
+   ![Service Desk enabled](img/service_desk_enabled.png)
 
-     _In GitLab 11.7, we updated the format of the generated email address.
-     However the older format is still supported, allowing existing aliases
-     or contacts to continue working._
+   _In GitLab 11.7, we updated the format of the generated email address.
+   However the older format is still supported, allowing existing aliases
+   or contacts to continue working._
 
+1. Service Desk is now enabled for this project! You should be able to access it from your project's navigation **Issue submenu**:
 
-5.   Service Desk is now enabled for this project! You should be able to access it from your project's navigation **Issue submenu**:
-
-     ![Service Desk Navigation Item](img/service_desk_nav_item.png)
+   ![Service Desk Navigation Item](img/service_desk_nav_item.png)
 
 ## Using Service Desk
 
diff --git a/doc/user/project/web_ide/index.md b/doc/user/project/web_ide/index.md
index 3d92508ad04..9bf400e7dff 100644
--- a/doc/user/project/web_ide/index.md
+++ b/doc/user/project/web_ide/index.md
@@ -295,6 +295,5 @@ active terminal at a time.
   connect to the runner. Please try to stop and restart the terminal. If the
   problem persists, double check your runner configuration.
 
-
 [ce]: https://about.gitlab.com/pricing/
 [ee]: https://about.gitlab.com/pricing/