Remove consecutive blank lines from markdown files

For the sake of consistency, removes any extraneous
consecutive blank lines from the doc suite.

doc/administration/auth/authentiq.md

@@ -50,7 +50,6 @@ Authentiq will generate a Client ID and the accompanying Client Secret for you t
       }
     ```
-
 1. The `scope` is set to request the user's name, email (required and signed), and permission to send push notifications to sign in on subsequent visits.
 See [OmniAuth Authentiq strategy](https://github.com/AuthentiqID/omniauth-authentiq/wiki/Scopes,-callback-url-configuration-and-responses) for more information on scopes and modifiers.

doc/administration/auth/ldap.md

@@ -448,7 +448,6 @@ ldapsearch -H ldaps://$host:$port -D "$bind_dn" -y bind_dn_password.txt  -b "$ba
   port.
 - We are assuming the password for the bind_dn user is in bind_dn_password.txt.
-
 ### Invalid credentials when logging in
 - Make sure the user you are binding with has enough permissions to read the user's

doc/administration/auth/okta.md

@@ -140,7 +140,6 @@ Now that the Okta app is configured, it's time to enable it in GitLab.
       }
     ```
-
 1. [Reconfigure][reconf] or [restart] GitLab for Omnibus and installations
    from source respectively for the changes to take effect.

doc/administration/container_registry.md

@@ -542,7 +542,6 @@ Read more about the Container Registry notifications config options in the
 >**Note:**
 Multiple endpoints can be configured for the Container Registry.
-
 **Omnibus GitLab installations**
 To configure a notification endpoint in Omnibus:

doc/administration/high_availability/redis.md

@@ -855,7 +855,6 @@ To make sure your configuration is correct:
     You should see a different port after a few seconds delay
     (the failover/reconnect time).
-
 ## Changelog
 Changes to Redis HA over time.

doc/administration/integration/plantuml.md

@@ -52,7 +52,6 @@ http://localhost:8080/plantuml
 you can change these defaults by editing the `/etc/tomcat7/server.xml` file.
-
 ## GitLab
 You need to enable PlantUML integration from Settings under Admin Area. To do

doc/administration/operations/cleaning_up_redis_sessions.md

@@ -20,7 +20,6 @@ configuration settings if you have used the advanced Redis
 settings outlined in
 [Configuration Files Documentation](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/config/README.md).
-
 First we define a shell function with the proper Redis connection details.
 ```

doc/administration/repository_storage_types.md

@@ -41,7 +41,6 @@ Registry, etc.
 ## Hashed Storage
-
 Hashed Storage is the new storage behavior we rolled out with 10.0. Instead
 of coupling project URL and the folder structure where the repository will be
 stored on disk, we are coupling a hash, based on the project's ID. This makes

doc/administration/restart_gitlab.md

@@ -137,7 +137,6 @@ If you are using other init systems, like systemd, you can check the
 [GitLab Recipes][gl-recipes] repository for some unofficial services. These are
 **not** officially supported so use them at your own risk.
-
 [omnibus-dl]: https://about.gitlab.com/downloads/ "Download the Omnibus packages"
 [install]: ../install/installation.md "Documentation to install GitLab from source"
 [mailroom]: reply_by_email.md "Used for replying by email in GitLab issues and merge requests"

doc/api/commits.md

@@ -18,7 +18,6 @@ GET /projects/:id/repository/commits
 | `all` | boolean | no | Retrieve every commit from the repository |
 | `with_stats` | boolean | no | Stats about each commit will be added to the response |
-
 ```bash
 curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/projects/5/repository/commits"
 ```
@@ -81,7 +80,6 @@ POST /projects/:id/repository/commits
 | `author_name` | string | no | Specify the commit author's name |
 | `stats` | boolean | no | Include commit stats. Default is true |
-
 | `actions[]` Attribute | Type | Required | Description |
 | --------------------- | ---- | -------- | ----------- |
 | `action` | string | yes | The action to perform, `create`, `delete`, `move`, `update`, `chmod`|
@@ -601,7 +599,6 @@ GET /projects/:id/repository/commits/:sha/merge_requests
 | `id`      | integer/string | yes | The ID or [URL-encoded path of the project](README.md#namespaced-path-encoding) owned by the authenticated user
 | `sha`     | string  | yes   | The commit SHA
-
 ```bash
 curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/projects/5/repository/commits/af5b13261899fb2c0db30abdd0af8b07cb44fdc5/merge_requests"
 ```

doc/api/container_registry.md

@@ -16,7 +16,6 @@ GET /projects/:id/registry/repositories
 | --------- | ---- | -------- | ----------- |
 | `id`      | integer/string | yes | The ID or [URL-encoded path of the project](README.md#namespaced-path-encoding) owned by the authenticated user. |
-
 ```bash
 curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/projects/5/registry/repositories"
 ```

doc/api/discussions.md

@@ -641,7 +641,6 @@ Parameters:
 curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/projects/5/merge_requests/11/discussions/6a9c1750b37d513a43987b574953fceb50b03ce7?resolved=true
 ```
-
 ### Add note to existing merge request discussion
 Adds a new note to the discussion.

doc/api/group_milestones.md

@@ -48,7 +48,6 @@ Example Response:
 ]
 ```
-
 ## Get single milestone
 Gets a single group milestone.

doc/api/import.md

@@ -15,7 +15,6 @@ POST /import/github
 | `new_name`   | string | no      | New repo name     |
 | `target_namespace`   | string | yes      | Namespace to import repo into     |
-
 ```bash
 curl --request POST --header "PRIVATE-TOKEN: 9koXpg98eAheJpvBs5tK" --data "personal_access_token=abc123&repo_id=12345&target_namespace=root" https://gitlab.example.com/api/v4/import/github
 ```
@@ -30,4 +29,3 @@ Example response:
     "full_name": "Administrator / my-repo"
 }
 ```
-

doc/api/issues.md

@@ -168,7 +168,6 @@ GET /groups/:id/issues?my_reaction_emoji=star
 | `updated_after`     | datetime         | no         | Return issues updated on or after the given time                                                                              |
 | `updated_before`    | datetime         | no         | Return issues updated on or before the given time                                                                             |
-
 ```bash
 curl --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/groups/4/issues
 ```
@@ -568,7 +567,6 @@ PUT /projects/:id/issues/:issue_iid
 | `due_date`     | string  | no       | Date time string in the format YEAR-MONTH-DAY, e.g. `2016-03-11`                                           |
 | `discussion_locked` | boolean | no  | Flag indicating if the issue's discussion is locked. If the discussion is locked only project members can add or edit comments. |
-
 ```bash
 curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/projects/4/issues/85?state_event=close
 ```
@@ -822,7 +820,6 @@ Example response:
 **Note**: `assignee` column is deprecated, now we show it as a single-sized array `assignees` to conform to the GitLab EE API.
-
 **Note**: The `closed_by` attribute was [introduced in GitLab 10.6][ce-17042]. This value will only be present for issues which were closed after GitLab 10.6 and when the user account that closed the issue still exists.
 ## Unsubscribe from an issue
@@ -990,7 +987,6 @@ Example response:
 **Note**: `assignee` column is deprecated, now we show it as a single-sized array `assignees` to conform to the GitLab EE API.
-
 **Note**: The `closed_by` attribute was [introduced in GitLab 10.6][ce-17042]. This value will only be present for issues which were closed after GitLab 10.6 and when the user account that closed the issue still exists.
 ## Set a time estimate for an issue
@@ -1288,7 +1284,6 @@ Example response:
 ]
 ```
-
 ## Participants on issues
 ```
@@ -1327,7 +1322,6 @@ Example response:
 ]
 ```
-
 ## Comments on issues
 Comments are done via the [notes](notes.md) resource.

doc/api/labels.md

@@ -161,7 +161,6 @@ PUT /projects/:id/labels
 | `description`   | string  | no                                | The new description of the label |
 | `priority`    | integer | no       | The new priority of the label. Must be greater or equal than zero or `null` to remove the priority. |
-
 ```bash
 curl --request PUT --data "name=documentation&new_name=docs&color=#8E44AD&description=Documentation" --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/projects/1/labels"
 ```

doc/api/merge_requests.md

@@ -160,7 +160,6 @@ will be the same. In the case of a merge request from a fork,
 `target_project_id` and `project_id` will be the same and
 `source_project_id` will be the fork project's ID.
-
 Parameters:
 | Attribute           | Type           | Required | Description                                                                                                                    |
@@ -531,7 +530,6 @@ Parameters:
 - `id` (required) - The ID or [URL-encoded path of the project](README.md#namespaced-path-encoding) owned by the authenticated user
 - `merge_request_iid` (required) - The internal ID of the merge request
-
 ```json
 [
   {
@@ -566,7 +564,6 @@ Parameters:
 - `id` (required) - The ID or [URL-encoded path of the project](README.md#namespaced-path-encoding) owned by the authenticated user
 - `merge_request_iid` (required) - The internal ID of the merge request
-
 ```json
 [
   {

doc/api/oauth2.md

@@ -206,4 +206,3 @@ or you can put the token to the Authorization header:
 ```
 curl --header "Authorization: Bearer OAUTH-TOKEN" https://gitlab.example.com/api/v4/user
 ```
-

doc/api/project_snippets.md

@@ -124,7 +124,6 @@ Parameters:
 > **Notes:**
 > [Introduced][ce-29508] in GitLab 9.4.
-
 Available only for admins.
 ```

doc/api/project_templates.md

@@ -101,7 +101,6 @@ GET /projects/:id/templates/:type/:key
 Example response (Dockerfile):
-
 ```json
 {
   "name": "Binary",