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.

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.
4121c636 · Marcel Amirault · Evan Read · e8fd34b1 · 4121c636 · 4121c636
Commit 4121c636 authored Jul 15, 2019 by Marcel Amirault Committed by Evan Read Jul 15, 2019
27 changed files
--- a/doc/administration/geo/replication/external_database.md
+++ b/doc/administration/geo/replication/external_database.md
@@ -25,7 +25,6 @@ developed and tested. We aim to be compatible with most external

   This command will use your defined `external_url` in `/etc/gitlab/gitlab.rb`.

-
 ### Configure the external database to be replicated

 To set up an external database, you can either:

--- a/doc/administration/housekeeping.md
+++ b/doc/administration/housekeeping.md
@@ -2,7 +2,6 @@

 > [Introduced][ce-2371] in GitLab 8.4.

---
 ## Automatic housekeeping

 GitLab automatically runs `git gc` and `git repack` on repositories
@@ -32,8 +31,6 @@ the `pushes_since_gc` value is 200 a `git gc` will be run.

 You can find this option under your project's **Settings > General > Advanced**.

---
-
 ![Housekeeping settings](img/housekeeping_settings.png)

 [ce-2371]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2371 "Housekeeping merge request"

--- a/doc/administration/job_artifacts.md
+++ b/doc/administration/job_artifacts.md
@@ -13,8 +13,6 @@ if you want to know how to disable it.

 To disable artifacts site-wide, follow the steps below.

---
-
 **In Omnibus installations:**

 1. Edit `/etc/gitlab/gitlab.rb` and add the following line:
@@ -25,8 +23,6 @@ To disable artifacts site-wide, follow the steps below.

 1. Save the file and [reconfigure GitLab][] for the changes to take effect.

---
-
 **In installations from source:**

 1. Edit `/home/git/gitlab/config/gitlab.yml` and add or amend the following lines:
@@ -49,8 +45,6 @@ this is done when the job succeeds, but can also be done on failure, or always,
 To change the location where the artifacts are stored locally, follow the steps
 below.

---
-
 **In Omnibus installations:**

 _The artifacts are stored by default in
@@ -65,8 +59,6 @@ _The artifacts are stored by default in

 1. Save the file and [reconfigure GitLab][] for the changes to take effect.

---
-
 **In installations from source:**

 _The artifacts are stored by default in
@@ -167,8 +159,6 @@ _The artifacts are stored by default in
   gitlab-rake gitlab:artifacts:migrate
   ```

---
-
 **In installations from source:**

 _The artifacts are stored by default in
@@ -207,8 +197,6 @@ right after that date passes. Artifacts are cleaned up by the
 To change the default schedule on which the artifacts are expired, follow the
 steps below.

---
-
 **In Omnibus installations:**

 1. Edit `/etc/gitlab/gitlab.rb` and comment out or add the following line
@@ -219,8 +207,6 @@ steps below.

 1. Save the file and [reconfigure GitLab][] for the changes to take effect.

---
-
 **In installations from source:**

 1. Edit `/home/git/gitlab/config/gitlab.yml` and add or amend the following
@@ -240,8 +226,6 @@ steps below.
 To disable [the dependencies validation](../ci/yaml/README.md#when-a-dependent-job-will-fail),
 you can flip the feature flag from a Rails console.

---
-
 **In Omnibus installations:**

 1. Enter the Rails console:
@@ -256,8 +240,6 @@ you can flip the feature flag from a Rails console.
   Feature.enable('ci_disable_validates_dependencies')
   ```

---
-
 **In installations from source:**

 1. Enter the Rails console:

--- a/doc/administration/monitoring/performance/gitlab_configuration.md
+++ b/doc/administration/monitoring/performance/gitlab_configuration.md
@@ -8,12 +8,8 @@ The minimum required settings you need to set are the InfluxDB host and port.
 Make sure _Enable InfluxDB Metrics_ is checked and hit **Save** to save the
 changes.

---
-
 ![GitLab Performance Monitoring Admin Settings](img/metrics_gitlab_configuration_settings.png)

---
-
 Finally, a restart of all GitLab processes is required for the changes to take
 effect:

@@ -30,8 +26,6 @@ sudo service gitlab restart
 When any migrations are pending, the metrics are disabled until the migrations
 have been performed.

---
-
 Read more on:

 - [Introduction to GitLab Performance Monitoring](introduction.md)

--- a/doc/administration/monitoring/performance/performance_bar.md
+++ b/doc/administration/monitoring/performance/performance_bar.md
@@ -40,10 +40,6 @@ display it.

 You can toggle the Bar using the same shortcut.

---
-
 ![GitLab Performance Bar Admin Settings](img/performance_bar_configuration_settings.png)

---
-
 [Gitaly]: ../../gitaly/index.md
--- a/doc/administration/repository_storage_paths.md
+++ b/doc/administration/repository_storage_paths.md
@@ -55,8 +55,6 @@ storage2:
 > don't specify the full repository path but the parent path), but not for source
 > installations.

---
-
 Now that you've read that big fat warning above, let's edit the configuration
 files and add the full paths of the alternative repository storage paths. In
 the example below, we add two more mountpoints that are named `nfs` and `cephfs`
@@ -90,8 +88,6 @@ are upgrading from a version prior to 8.10, make sure to add the configuration
 as described in the step above. After you make the changes and confirm they are
 working, you can remove the `repos_path` line.

---
-
 **For Omnibus installations**

 1. Edit `/etc/gitlab/gitlab.rb` by appending the rest of the paths to the

--- a/doc/administration/uploads.md
+++ b/doc/administration/uploads.md
@@ -10,8 +10,6 @@ This is the default configuration
 To change the location where the uploads are stored locally, follow the steps
 below.

---
-
 **In Omnibus installations:**

 NOTE: **Note:**
@@ -29,8 +27,6 @@ _The uploads are stored by default in `/var/opt/gitlab/gitlab-rails/uploads`._

 1. Save the file and [reconfigure GitLab][] for the changes to take effect.

---
-
 **In installations from source:**

 _The uploads are stored by default in
@@ -121,8 +117,6 @@ _The uploads are stored by default in
 1. Save the file and [reconfigure GitLab][] for the changes to take effect.
 1. Migrate any existing local uploads to the object storage using [`gitlab:uploads:migrate` rake task](raketasks/uploads/migrate.md).

---
-
 **In installations from source:**

 _The uploads are stored by default in

--- a/doc/api/README.md
+++ b/doc/api/README.md
@@ -321,8 +321,6 @@ By default, impersonation is enabled. To disable impersonation:

 To re-enable impersonation, remove this configuration and reconfigure GitLab.

---
-
 **For installations from source**

 1. Edit `config/gitlab.yml`:
@@ -381,8 +379,6 @@ returned with status code `404`:
 }
 ```

---
-
 Example of a valid API call and a request using cURL with sudo request,
 providing a username:


--- a/doc/api/issues.md
+++ b/doc/api/issues.md
@@ -357,7 +357,6 @@ GET /projects/:id/issues?confidential=true
 | `updated_before`    | datetime         | no         | Return issues updated on or before the given time                                                                             |
 | `confidential`     | Boolean          | no         | Filter confidential or public issues.                                                                                         |

-
 ```bash
 curl --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/projects/4/issues
 ```

--- a/doc/api/system_hooks.md
+++ b/doc/api/system_hooks.md
@@ -11,8 +11,6 @@ Read more about [system hooks](../system_hooks/system_hooks.md).

 Get a list of all system hooks.

---
-
 ```
 GET /hooks
 ```
@@ -44,8 +42,6 @@ Example response:

 Add a new system hook.

---
-
 ```
 POST /hooks
 ```
@@ -116,8 +112,6 @@ Example response:

 Deletes a system hook.

---
-
 ```
 DELETE /hooks/:id
 ```
@@ -130,4 +124,4 @@ Example request:

 ```bash
 curl --request DELETE --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/hooks/2
-```
\ No newline at end of file
+```
--- a/doc/development/fe_guide/index.md
+++ b/doc/development/fe_guide/index.md
@@ -17,8 +17,6 @@ Working with our frontend assets requires Node (v8.10.0 or greater) and Yarn

 For our currently-supported browsers, see our [requirements][requirements].

---
-
 ## Initiatives

 Current high-level frontend goals are listed on [Frontend Epics](https://gitlab.com/groups/gitlab-org/-/epics?label_name%5B%5D=frontend).
@@ -77,8 +75,6 @@ How we use Snowplow to track custom events.

 Read the [frontend's FAQ](frontend_faq.md) for common small pieces of helpful information.

---
-
 ## Style Guides

 ### [JavaScript Style Guide](style_guide_js.md)
@@ -91,20 +87,14 @@ changes.

 Our SCSS conventions which are enforced through [scss-lint][scss-lint].

---
-
 ## [Performance](performance.md)

 Best practices for monitoring and maximizing frontend performance.

---
-
 ## [Security](security.md)

 Frontend security practices.

---
-
 ## [Accessibility](accessibility.md)

 Our accessibility standards and resources.

--- a/doc/development/new_fe_guide/index.md
+++ b/doc/development/new_fe_guide/index.md
@@ -19,7 +19,6 @@ Learn about all the internal JavaScript modules that make up our frontend.

 Style guides to keep our code consistent.

-
 ## [Tips](tips.md)

 Tips from our frontend team to develop more efficiently and effectively.
--- a/doc/development/testing_guide/index.md
+++ b/doc/development/testing_guide/index.md
@@ -22,62 +22,44 @@ automated testing means, and what are its principles:
 - [Five Factor Testing](https://www.devmynd.com/blog/five-factor-testing): Why do we need tests?
 - [Principles of Automated Testing](http://www.lihaoyi.com/post/PrinciplesofAutomatedTesting.html): Levels of testing. Prioritize tests. Cost of tests.

---
-
 ## [Testing levels](testing_levels.md)

 Learn about the different testing levels, and how to decide at what level your
 changes should be tested.

---
-
 ## [Testing best practices](best_practices.md)

 Everything you should know about how to write good tests: Test Design, RSpec, FactoryBot,
 system tests, parameterized tests etc.

---
-
 ## [Frontend testing standards and style guidelines](frontend_testing.md)

 Everything you should know about how to write good Frontend tests: Karma,
 testing promises, stubbing etc.

---
-
 ## [Flaky tests](flaky_tests.md)

 What are flaky tests, the different kind of flaky tests we encountered, and what
 we do about them.

---
-
 ## [GitLab tests in the Continuous Integration (CI) context](ci.md)

 How GitLab test suite is run in the CI context: setup, caches, artifacts,
 parallelization, monitoring.

---
-
 ## [Review apps](review_apps.md)

 How review apps are set up for GitLab CE/EE and how to use them.

---
-
 ## [Testing Rake tasks](testing_rake_tasks.md)

 Everything you should know about how to test Rake tasks.

---
-
 ## [End-to-end tests](end_to_end/index.md)

 Everything you should know about how to run end-to-end tests using
 [GitLab QA][gitlab-qa] testing framework.

---
-
 [Return to Development documentation](../README.md)

 [RSpec]: https://github.com/rspec/rspec-rails#feature-specs

--- a/doc/integration/oauth_provider.md
+++ b/doc/integration/oauth_provider.md
@@ -25,8 +25,6 @@ can be used for authentication to your GitLab instance
 The 'GitLab Importer' feature is also using the OAuth protocol to give access
 to repositories without sharing user credentials to your GitLab.com account.

---
-
 GitLab supports two ways of adding a new OAuth2 application to an instance. You
 can either add an application as a regular user or add it in the admin area.
 What this means is that GitLab can actually have instance-wide and a user-wide
@@ -41,24 +39,18 @@ In order to add a new application via your profile, navigate to

 ![New OAuth application](img/oauth_provider_user_wide_applications.png)

---
-
 In the application form, enter a **Name** (arbitrary), and make sure to set up
 correctly the **Redirect URI** which is the URL where users will be sent after
 they authorize with GitLab.

 ![New OAuth application form](img/oauth_provider_application_form.png)

---
-
 When you hit **Submit** you will be provided with the application ID and
 the application secret which you can then use with your application that
 connects to GitLab.

 ![OAuth application ID and secret](img/oauth_provider_application_id_secret.png)

---
-
 ## OAuth applications in the admin area

 To create an application that does not belong to a certain user, you can create
@@ -69,8 +61,6 @@ it from the admin area.
 You're also able to mark an application as _trusted_ when creating it through the admin area. By doing that,
 the user authorization step is automatically skipped for this application.

---
-
 ## Authorized applications

 Every application you authorized to use your GitLab credentials will be shown
@@ -78,8 +68,6 @@ in the **Authorized applications** section under **Profile Settings > Applicatio

 ![Authorized_applications](img/oauth_provider_authorized_application.png)

---
-
 GitLab's OAuth applications support scopes, which allow various actions that any given
 application can perform such as `read_user` and `api`. There are many more scopes
 available.

--- a/doc/raketasks/backup_restore.md
+++ b/doc/raketasks/backup_restore.md
@@ -315,8 +315,6 @@ if you see `411 Length Required` errors after attempting to upload, you may
 need to downgrade the `aws_signature_version` value from the default value to
 2 [due to this issue](https://github.com/fog/fog-aws/issues/428).

---
-
 For installations from source:

 1. Edit `home/git/gitlab/config/gitlab.yml`:
@@ -428,8 +426,6 @@ For Omnibus GitLab packages:

 1. [Reconfigure GitLab] for the changes to take effect

---
-
 For installations from source:

 1. Edit `home/git/gitlab/config/gitlab.yml`:
@@ -490,8 +486,6 @@ For Omnibus GitLab packages:

 1. [Reconfigure GitLab] for the changes to take effect.

---
-
 For installations from source:

 1. Edit `home/git/gitlab/config/gitlab.yml`:
@@ -527,8 +521,6 @@ For Omnibus GitLab packages:

 1. [Reconfigure GitLab] for the changes to take effect.

---
-
 For installations from source:

 1. Edit `/home/git/gitlab/config/gitlab.yml`:
@@ -580,8 +572,6 @@ There, add the following line to schedule the backup for everyday at 2 AM:
 You may also want to set a limited lifetime for backups to prevent regular
 backups using all your disk space.

---
-
 For installations from source:

 1. Edit `home/git/gitlab/config/gitlab.yml`:
@@ -815,6 +805,7 @@ will have all your repositories, but not any other data.
 ## Troubleshooting

 ### Restoring database backup using omnibus packages outputs warnings
+
 If you are using backup restore procedures you might encounter the following warnings:

 ```

--- a/doc/security/unlock_user.md
+++ b/doc/security/unlock_user.md
 ---
 type: howto
 ---
+
 # How to unlock a locked user

 To unlock a locked user, first log into your server with root privileges.

 Start a Ruby on Rails console with this command:

-
 ```bash
 gitlab-rails console production
 ```

--- a/doc/topics/autodevops/index.md
+++ b/doc/topics/autodevops/index.md
@@ -109,10 +109,10 @@ To make full use of Auto DevOps, you will need:
   To enable deployments, you will need Kubernetes 1.5+. You need a [Kubernetes cluster][kubernetes-clusters]
   for the project, or a Kubernetes [default service template](../../user/project/integrations/services_templates.md)
   for the entire GitLab installation.
-    1. **A load balancer** - You can use NGINX ingress by deploying it to your
-       Kubernetes cluster using the
-       [`nginx-ingress`](https://github.com/kubernetes/charts/tree/master/stable/nginx-ingress)
-       Helm chart.
+   1. **A load balancer** - You can use NGINX ingress by deploying it to your
+      Kubernetes cluster using the
+      [`nginx-ingress`](https://github.com/kubernetes/charts/tree/master/stable/nginx-ingress)
+      Helm chart.
 1. **Prometheus** (needed for Auto Monitoring) - To enable Auto Monitoring, you
   will need Prometheus installed somewhere (inside or outside your cluster) and
   configured to scrape your Kubernetes cluster. To get response metrics
@@ -168,7 +168,6 @@ From GitLab 11.8, `KUBE_INGRESS_BASE_DOMAIN` replaces `AUTO_DEVOPS_DOMAIN`.
 Support for `AUTO_DEVOPS_DOMAIN` was [removed in GitLab
 12.0](https://gitlab.com/gitlab-org/gitlab-ce/issues/56959).

-
 ## Using multiple Kubernetes clusters **(PREMIUM)**

 When using Auto DevOps, you may want to deploy different environments to
@@ -202,7 +201,7 @@ To add a different cluster for each environment:
 1. Navigate to your project's **Operations > Kubernetes** and create the Kubernetes clusters
   with their respective environment scope as described from the table above.

-    ![Auto DevOps multiple clusters](img/autodevops_multiple_clusters.png)
+   ![Auto DevOps multiple clusters](img/autodevops_multiple_clusters.png)

 1. After the clusters are created, navigate to each one and install Helm Tiller
   and Ingress. Wait for the Ingress IP address to be assigned.

--- 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.


--- 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.
--- 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.


--- 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:

 ```

--- 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


--- 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

--- 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


--- 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/
--- a/doc/workflow/file_finder.md
+++ b/doc/workflow/file_finder.md
@@ -2,8 +2,6 @@

 > [Introduced][gh-9889] in GitLab 8.4.

---
-
 The file finder feature allows you to quickly shortcut your way when you are
 searching for a file in a repository using the GitLab UI.

@@ -12,8 +10,6 @@ project.

 ![Find file button](img/file_finder_find_button.png)

---
-
 For those who prefer to keep their fingers on the keyboard, there is a
 [shortcut button](shortcuts.md) as well, which you can invoke from _anywhere_
 in a project.

--- a/doc/workflow/todos.md
+++ b/doc/workflow/todos.md
@@ -12,8 +12,6 @@ in a simple dashboard.

 ![To Do screenshot showing a list of items to check on](img/todos_index.png)

---
-
 You can quickly access your To-Do List by clicking the checkmark icon next to the
 search bar in the top navigation. If the count is:

@@ -31,15 +29,15 @@ A To Do displays on your To-Do List when:

 - An issue or merge request is assigned to you
 - You are `@mentioned` in the description or comment of an:
-    - Issue
-    - Merge Request
-    - Epic **(ULTIMATE)**
+  - Issue
+  - Merge Request
+  - Epic **(ULTIMATE)**
 - You are `@mentioned` in a comment on a commit
 - A job in the CI pipeline running for your merge request failed, but this
  job is not allowed to fail
 - An open merge request becomes unmergeable due to conflict, and you are either: 
-    - The author 
-    - Have set it to automatically merge once the pipeline succeeds
+  - The author 
+  - Have set it to automatically merge once the pipeline succeeds

 To-do triggers are not affected by [GitLab Notification Email settings](notifications.md).

@@ -94,8 +92,6 @@ Actions that dismiss To-Do items include:
 - Adding/removing a label
 - Commenting on the issue

---
-
 Your To-Do List is personal, and items are only marked as done if the action comes from
 you. If you close the issue or merge request, your To Do is automatically
 marked as done.
@@ -108,8 +104,6 @@ To prevent other users from closing issues without you being notified, if someon

 There is just one To Do for each of these, so mentioning a user a hundred times in an issue will only trigger one To Do.

---
-
 If no action is needed, you can manually mark the To Do as done by clicking the
 corresponding **Done** button, and it will disappear from your To-Do List.