Remove trailing whitespace in docs

Remove unneeded trailing whitespace in lines in
/security /workflow /user docs

11 files changed, 89 insertions, 90 deletions

diff --git a/doc/user/admin_area/settings/account_and_limit_settings.md b/doc/user/admin_area/settings/account_and_limit_settings.md
index 9968b7349dc..7fbb4d84cfc 100644
--- a/doc/user/admin_area/settings/account_and_limit_settings.md
+++ b/doc/user/admin_area/settings/account_and_limit_settings.md
@@ -41,7 +41,7 @@ These settings can be found within:
   - The path `/admin/application_settings`.
 
 The first push of a new project, including LFS objects, will be checked for size
-and **will** be rejected if the sum of their sizes exceeds the maximum allowed 
+and **will** be rejected if the sum of their sizes exceeds the maximum allowed
 repository size.
 
 **Note:** The repository size limit includes repository files and LFS, and does not include artifacts.
diff --git a/doc/user/project/clusters/runbooks/index.md b/doc/user/project/clusters/runbooks/index.md
index c67b12fb91a..c021d059d30 100644
--- a/doc/user/project/clusters/runbooks/index.md
+++ b/doc/user/project/clusters/runbooks/index.md
@@ -1,28 +1,27 @@
 # Runbooks
 
-Runbooks are a collection of documented procedures that explain how to 
-carry out a particular process, be it starting, stopping, debugging, 
+Runbooks are a collection of documented procedures that explain how to
+carry out a particular process, be it starting, stopping, debugging,
 or troubleshooting a particular system.
 
 Using [Jupyter Notebooks](https://jupyter.org/) and the [Rubix library](https://github.com/Nurtch/rubix),
 users can get started writing their own executable runbooks.
 
-
 ## Overview
 
-Historically, runbooks took the form of a decision tree or a detailed 
-step-by-step guide depending on the condition or system. 
+Historically, runbooks took the form of a decision tree or a detailed
+step-by-step guide depending on the condition or system.
 
-Modern implementations have introduced the concept of an "executable 
-runbooks", where, along with a well-defined process, operators can execute 
+Modern implementations have introduced the concept of an "executable
+runbooks", where, along with a well-defined process, operators can execute
 pre-written code blocks or database queries against a given environment.
 
 ## Executable Runbooks
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/45912) in GitLab 11.4.
 
-The JupyterHub app offered via GitLab’s Kubernetes integration now ships 
-with Nurtch’s Rubix library, providing a simple way to create DevOps 
+The JupyterHub app offered via GitLab’s Kubernetes integration now ships
+with Nurtch’s Rubix library, providing a simple way to create DevOps
 runbooks. A sample runbook is provided, showcasing common operations. While Rubix makes it
 simple to create common Kubernetes and AWS workflows, you can also create them manually without
 Rubix.
@@ -35,33 +34,33 @@ for an overview of how this is accomplished in GitLab!**
 
 To create an executable runbook, you will need:
 
-1. **Kubernetes** - A Kubernetes cluster is required to deploy the rest of the applications. 
+1. **Kubernetes** - A Kubernetes cluster is required to deploy the rest of the applications.
     The simplest way to get started is to add a cluster using [GitLab's GKE integration](../index.md#adding-and-creating-a-new-gke-cluster-via-gitlab).
-1. **Helm Tiller** - Helm is a package manager for Kubernetes and is required to install 
-    all the other applications. It is installed in its own pod inside the cluster which 
+1. **Helm Tiller** - Helm is a package manager for Kubernetes and is required to install
+    all the other applications. It is installed in its own pod inside the cluster which
     can run the helm CLI in a safe environment.
-1. **Ingress** - Ingress can provide load balancing, SSL termination, and name-based 
+1. **Ingress** - Ingress can provide load balancing, SSL termination, and name-based
     virtual hosting. It acts as a web proxy for your applications.
-1. **JupyterHub** - [JupyterHub](https://jupyterhub.readthedocs.io/) is a multi-user service for managing notebooks across 
-    a team. Jupyter Notebooks provide a web-based interactive programming environment 
+1. **JupyterHub** - [JupyterHub](https://jupyterhub.readthedocs.io/) is a multi-user service for managing notebooks across
+    a team. Jupyter Notebooks provide a web-based interactive programming environment
     used for data analysis, visualization, and machine learning.
 
 ## Nurtch
 
-Nurtch is the company behind the [Rubix library](https://github.com/Nurtch/rubix). Rubix is 
-an open-source python library that makes it easy to perform common DevOps tasks inside Jupyter Notebooks. 
-Tasks such as plotting Cloudwatch metrics and rolling your ECS/Kubernetes app are simplified 
-down to a couple of lines of code. See the [Nurtch Documentation](http://docs.nurtch.com/en/latest) 
+Nurtch is the company behind the [Rubix library](https://github.com/Nurtch/rubix). Rubix is
+an open-source python library that makes it easy to perform common DevOps tasks inside Jupyter Notebooks.
+Tasks such as plotting Cloudwatch metrics and rolling your ECS/Kubernetes app are simplified
+down to a couple of lines of code. See the [Nurtch Documentation](http://docs.nurtch.com/en/latest)
 for more information.
 
 ## Configure an executable runbook with GitLab
 
-Follow this step-by-step guide to configure an executable runbook in GitLab using 
+Follow this step-by-step guide to configure an executable runbook in GitLab using
 the components outlined above and the preloaded demo runbook.
 
 ### 1. Add a Kubernetes cluster
 
-Follow the steps outlined in [Adding and creating a new GKE cluster via GitLab](../index.md#adding-and-creating-a-new-gke-cluster-via-gitlab) 
+Follow the steps outlined in [Adding and creating a new GKE cluster via GitLab](../index.md#adding-and-creating-a-new-gke-cluster-via-gitlab)
 to add a Kubernetes cluster to your project.
 
 ### 2. Install Helm Tiller, Ingress, and JupyterHub
@@ -80,13 +79,13 @@ Once Ingress has been installed successfully, click the **Install** button next
 
 ### 3. Login to JupyterHub and start the server
 
-Once JupyterHub has been installed successfully, navigate to the displayed **Jupyter Hostname** URL and click 
-**Sign in with GitLab**. Authentication is automatically enabled for any user of the GitLab instance via OAuth2. This 
+Once JupyterHub has been installed successfully, navigate to the displayed **Jupyter Hostname** URL and click
+**Sign in with GitLab**. Authentication is automatically enabled for any user of the GitLab instance via OAuth2. This
 will redirect to GitLab in order to authorize JupyterHub to use your GitLab account. Click **Authorize**.
 
 ![authorize jupyter](img/authorize-jupyter.png)
 
-Once the application has been authorized you will taken back to the JupyterHub application. Click **Start My Server**. 
+Once the application has been authorized you will taken back to the JupyterHub application. Click **Start My Server**.
 The server will take a couple of seconds to start.
 
 ### 4. Configure access
@@ -103,7 +102,7 @@ Double-click the "Nurtch-DevOps-Demo.ipynb" runbook.
 
 ![sample runbook](img/sample-runbook.png)
 
-The contents on the runbook will be displayed on the right side of the screen. Under the "Setup" section, you will find 
+The contents on the runbook will be displayed on the right side of the screen. Under the "Setup" section, you will find
 entries for both your `PRIVATE_TOKEN` and your `PROJECT_ID`. Enter both these values, conserving the single quotes as follows:
 
 ```sql
@@ -111,7 +110,7 @@ PRIVATE_TOKEN = 'n671WNGecHugsdEDPsyo'
 PROJECT_ID = '1234567'
 ```
 
-Update the `VARIABLE_NAME` on the last line of this section to match the name of the variable you are using for your 
+Update the `VARIABLE_NAME` on the last line of this section to match the name of the variable you are using for your
 access token. In this example our variable name is `PRIVATE_TOKEN`.
 
 ```sql
@@ -120,8 +119,8 @@ VARIABLE_VALUE = project.variables.get('PRIVATE_TOKEN').value
 
 ### 5. Configure an operation
 
-For this example we'll use the "**Run SQL queries in Notebook**" section in the sample runbook to query 
-a postgres database. The first 4 lines of the section define the variables that are required for this query to function. 
+For this example we'll use the "**Run SQL queries in Notebook**" section in the sample runbook to query
+a postgres database. The first 4 lines of the section define the variables that are required for this query to function.
 
 ```sql
 %env DB_USER={project.variables.get('DB_USER').value}
@@ -134,10 +133,10 @@ Create the matching variables in your project's **Settings >> CI/CD >> Variables
 
 ![gitlab variables](img/gitlab-variables.png)
 
-Back in Jupyter, click the "Run SQL queries in Notebook" heading and the click *Run*. The results will be 
+Back in Jupyter, click the "Run SQL queries in Notebook" heading and the click *Run*. The results will be
 displayed in-line as follows:
 
 ![postgres query](img/postgres-query.png)
 
-You can try other operations such as running shell scripts or interacting with a Kubernetes cluster. Visit the 
-[Nurtch Documentation](http://docs.nurtch.com/) for more information.
\ No newline at end of file
+You can try other operations such as running shell scripts or interacting with a Kubernetes cluster. Visit the
+[Nurtch Documentation](http://docs.nurtch.com/) for more information.
diff --git a/doc/user/project/import/index.md b/doc/user/project/import/index.md
index 334be713aa5..9d7463416d8 100644
--- a/doc/user/project/import/index.md
+++ b/doc/user/project/import/index.md
@@ -34,7 +34,7 @@ This approach assumes all users from the self-hosted instance have already been
 If the users haven't been migrated yet, the user conducting the import
 will take the place of all references to the missing user(s).
 
-If you need to migrate all data over, you can leverage our [api](../../../api/README.md) to migrate from self-hosted to GitLab.com. 
+If you need to migrate all data over, you can leverage our [api](../../../api/README.md) to migrate from self-hosted to GitLab.com.
 The order of assets to migrate from a self-hosted instance to GitLab is the following:
 
 1. [Users](../../../api/users.md)
@@ -54,5 +54,5 @@ perhaps from an old server to a new server for example, is to
 [back up the project](../../../raketasks/backup_restore.md),
 then restore it on the new server.
 
-In the event of merging two GitLab instances together (for example, both instances have existing data on them and one can't be wiped), 
+In the event of merging two GitLab instances together (for example, both instances have existing data on them and one can't be wiped),
 refer to the instructions in [Migrating from self-hosted GitLab to GitLab.com](#migrating-from-self-hosted-gitlab-to-gitlabcom).
diff --git a/doc/user/project/integrations/custom_issue_tracker.md b/doc/user/project/integrations/custom_issue_tracker.md
index 23f1ce7a15a..7c7263704f9 100644
--- a/doc/user/project/integrations/custom_issue_tracker.md
+++ b/doc/user/project/integrations/custom_issue_tracker.md
@@ -17,6 +17,6 @@ Once you have configured and enabled Custom Issue Tracker Service you'll see a l
 
 ## Referencing issues
 
-- Issues are referenced with `ANYTHING-<ID>`, where `ANYTHING` can be any string and `<ID>` is a number used in the target project of the custom integration (example `PROJECT-143`). 
+- Issues are referenced with `ANYTHING-<ID>`, where `ANYTHING` can be any string and `<ID>` is a number used in the target project of the custom integration (example `PROJECT-143`).
 - `ANYTHING` is a placeholder to differentiate against GitLab issues, which are referenced with `#<ID>`. You can use a project name or project key to replace it for example.
-- So with the example above, `PROJECT-143` would refer to `https://customissuetracker.com/project-name/143`.
\ No newline at end of file
+- So with the example above, `PROJECT-143` would refer to `https://customissuetracker.com/project-name/143`.
diff --git a/doc/user/project/integrations/jira_server_configuration.md b/doc/user/project/integrations/jira_server_configuration.md
index 32991714973..5116cbfe9ac 100644
--- a/doc/user/project/integrations/jira_server_configuration.md
+++ b/doc/user/project/integrations/jira_server_configuration.md
@@ -13,46 +13,46 @@ access to your Jira projects. This is covered in the process below.
 1. Log in to your Jira instance as an administrator and under **Jira Administration**
    go to **User Management** to create a new user.
 
-     ![Jira user management link](img/jira_user_management_link.png)
+   ![Jira user management link](img/jira_user_management_link.png)
 
 1. The next step is to create a new user (e.g., `gitlab`) who has write access
    to projects in Jira. Enter the user's name and a _valid_ e-mail address
    since Jira sends a verification e-mail to set up the password.
    _**Note:** Jira creates the username automatically by using the e-mail
    prefix. You can change it later, if needed. Our integration does not support SSO (such as SAML). You will need to create
-    an HTTP basic authentication password. You can do this by visiting the user
-    profile, looking up the username, and setting a password._
+   an HTTP basic authentication password. You can do this by visiting the user
+   profile, looking up the username, and setting a password._
 
-     ![Jira create new user](img/jira_create_new_user.png)
+   ![Jira create new user](img/jira_create_new_user.png)
 
 1. Create a `gitlab-developers` group. (We will give this group write access to Jira
    projects in a later step). Go to the **Groups** tab on the left, and select **Add group**.
 
-     ![Jira create new user](img/jira_create_new_group.png)
+   ![Jira create new user](img/jira_create_new_group.png)
 
-     Give it a name and click **Add group**.
+   Give it a name and click **Add group**.
 
 1. Add the `gitlab` user to the `gitlab-developers` group by clicking **Edit members**.
    The `gitlab-developers` group should be listed in the leftmost box as a selected group.
    Under **Add members to selected group(s)**, enter `gitlab`.
 
-     ![Jira add user to group](img/jira_add_user_to_group.png)
-     
+   ![Jira add user to group](img/jira_add_user_to_group.png)
+
    Click **Add selected users** and `gitlab` should appear in the **Group member(s)** box.
    This membership is saved automatically.
-   
-     ![Jira added user to group](img/jira_added_user_to_group.png)
+
+   ![Jira added user to group](img/jira_added_user_to_group.png)
 
 1. To give the newly-created group 'write' access, you need to create a **Permission Scheme**.
    To do this, click the gear icon and select **Issues**. Then click **Permission Schemes**.
    Click **Add Permission Scheme** and enter a **Name** and, optionally, a **Description**.
-    
+
 1. Once your permission scheme is created, you'll be taken back to the permissions scheme list.
-   Locate your new permissions scheme and click **Permissions**. Next to **Administer Projects**, 
+   Locate your new permissions scheme and click **Permissions**. Next to **Administer Projects**,
    click **Edit**. In the resulting dialog box, select **Group** and select `gitlab-developers`
    from the dropdown.
 
-     ![Jira group access](img/jira_group_access.png)
+   ![Jira group access](img/jira_group_access.png)
 
 The Jira configuration is complete. Write down the new Jira username and its
 password as they will be needed when [configuring GitLab in the next section](jira.md#configuring-gitlab).
diff --git a/doc/user/project/issues/crosslinking_issues.md b/doc/user/project/issues/crosslinking_issues.md
index 93dc2a2e4ca..ec9eb7b62bb 100644
--- a/doc/user/project/issues/crosslinking_issues.md
+++ b/doc/user/project/issues/crosslinking_issues.md
@@ -47,7 +47,7 @@ display in both issues. The same is valid when mentioning issues in [merge reque
 ## From Merge Requests
 
 Mentioning issues in merge request comments works exactly the same way as
-they do for [related issues](#from-related-issues). 
+they do for [related issues](#from-related-issues).
 
 When you mention an issue in a merge request description, it will simply
 [link the issue and merge request together](#from-related-issues). Additionally,
diff --git a/doc/user/project/issues/issue_data_and_actions.md b/doc/user/project/issues/issue_data_and_actions.md
index 9c4d0de46d3..b15a05f40bb 100644
--- a/doc/user/project/issues/issue_data_and_actions.md
+++ b/doc/user/project/issues/issue_data_and_actions.md
@@ -210,7 +210,7 @@ and selecting either **Show comments only**, which only shows discussions and hi
 updates to the issue, or **Show history only**, which hides discussions and only shows updates.
 
 - You can mention a user or a group present in your GitLab instance with
-  `@username` or `@groupname` and they will be notified via To-Do items 
+  `@username` or `@groupname` and they will be notified via To-Do items
   and email, unless they have [disabled all notifications](#13-notifications)
   in their profile settings.
 - Mentions for yourself (the current logged in user), will be highlighted
diff --git a/doc/user/project/milestones/index.md b/doc/user/project/milestones/index.md
index b0745b1e2c5..142462e1879 100644
--- a/doc/user/project/milestones/index.md
+++ b/doc/user/project/milestones/index.md
@@ -14,12 +14,12 @@ the start and end of your Agile sprint.
 Set the milestone title to the name of your Agile sprint,
 such as `November 2018 sprint`.
 Add an issue to your Agile sprint by associating
-the milestone to the issue.  
+the milestone to the issue.
 
 ## Milestones as releases
 
 Milestones can be used as releases.
-Set the milestone due date to represent the release date of your release. 
+Set the milestone due date to represent the release date of your release.
 (And leave the milestone start date blank.)
 Set the milestone title to the version of your release,
 such as `Version 9.4`.
diff --git a/doc/user/project/pipelines/settings.md b/doc/user/project/pipelines/settings.md
index 24e15a37a40..e60da6a3e59 100644
--- a/doc/user/project/pipelines/settings.md
+++ b/doc/user/project/pipelines/settings.md
@@ -25,10 +25,10 @@ in `.gitlab-ci.yml`.
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28919) in GitLab 12.0.
 
 NOTE: **Note**:
-As of GitLab 12.0, newly created projects will automatically have a default 
+As of GitLab 12.0, newly created projects will automatically have a default
 `git depth` value of `50`.
 
-It is possible to limit the number of changes that GitLab CI/CD will fetch when cloning 
+It is possible to limit the number of changes that GitLab CI/CD will fetch when cloning
 a repository. Setting a limit to `git depth` can speed up Pipelines execution. Maximum
 allowed value is `1000`.
 
diff --git a/doc/user/project/settings/import_export.md b/doc/user/project/settings/import_export.md
index 98bcc7cc09f..7241df613eb 100644
--- a/doc/user/project/settings/import_export.md
+++ b/doc/user/project/settings/import_export.md
@@ -2,33 +2,33 @@
 
 >**Notes:**
 >
->  - [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/3050) in GitLab 8.9.
->  - Importing will not be possible if the import instance version differs from
->    that of the exporter.
->  - For GitLab admins, please read through 
->    [Project import/export administration](../../../administration/raketasks/project_import_export.md).
->  - For existing installations, the project import option has to be enabled in
->    application settings (`/admin/application_settings`) under 'Import sources'.
->    Ask your administrator if you don't see the **GitLab export** button when
->    creating a new project.
->  - Starting with GitLab 10.0, administrators can disable the project export option
->    on the GitLab instance in application settings (`/admin/application_settings`)
->    under 'Visibility and Access Controls'.
->  - You can find some useful raketasks if you are an administrator in the
->    [import_export](../../../administration/raketasks/project_import_export.md) raketask.
->  - The exports are stored in a temporary [shared directory](../../../development/shared_files.md) 
->    and are deleted every 24 hours by a specific worker.
->  - Group members will get exported as project members, as long as the user has
->    maintainer or admin access to the group where the exported project lives. An admin
->    in the import side is required to map the users, based on email or username.
->    Otherwise, a supplementary comment is left to mention the original author and
->    the MRs, notes or issues will be owned by the importer.
->  - Project members with owner access will get imported as maintainers.
->  - Control project Import/Export with the [API](../../../api/project_import_export.md).
->  - If an imported project contains merge requests originated from forks, 
->    then new branches associated with such merge requests will be created 
->    within a project during the import/export. Thus, the number of branches 
->    in the exported project could be bigger than in the original project.
+> - [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/3050) in GitLab 8.9.
+> - Importing will not be possible if the import instance version differs from
+>   that of the exporter.
+> - For GitLab admins, please read through
+>   [Project import/export administration](../../../administration/raketasks/project_import_export.md).
+> - For existing installations, the project import option has to be enabled in
+>   application settings (`/admin/application_settings`) under 'Import sources'.
+>   Ask your administrator if you don't see the **GitLab export** button when
+>   creating a new project.
+> - Starting with GitLab 10.0, administrators can disable the project export option
+>   on the GitLab instance in application settings (`/admin/application_settings`)
+>   under 'Visibility and Access Controls'.
+> - You can find some useful raketasks if you are an administrator in the
+>   [import_export](../../../administration/raketasks/project_import_export.md) raketask.
+> - The exports are stored in a temporary [shared directory](../../../development/shared_files.md)
+>   and are deleted every 24 hours by a specific worker.
+> - Group members will get exported as project members, as long as the user has
+>   maintainer or admin access to the group where the exported project lives. An admin
+>   in the import side is required to map the users, based on email or username.
+>   Otherwise, a supplementary comment is left to mention the original author and
+>   the MRs, notes or issues will be owned by the importer.
+> - Project members with owner access will get imported as maintainers.
+> - Control project Import/Export with the [API](../../../api/project_import_export.md).
+> - If an imported project contains merge requests originated from forks,
+>   then new branches associated with such merge requests will be created
+>   within a project during the import/export. Thus, the number of branches
+>   in the exported project could be bigger than in the original project.
 
 Existing projects running on any GitLab instance or GitLab.com can be exported
 with all their related data and be moved into a new GitLab instance.
@@ -79,7 +79,7 @@ The following items will NOT be exported:
 - Awards
 
 NOTE: **Note:**
-For more details on the specific data persisted in a project export, see the 
+For more details on the specific data persisted in a project export, see the
 [`import_export.yml`](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/lib/gitlab/import_export/import_export.yml) file.
 
 ## Exporting a project and its data
@@ -90,29 +90,29 @@ For more details on the specific data persisted in a project export, see the
 
 1. Scroll down to find the **Export project** button:
 
-    ![Export button](img/import_export_export_button.png)
+   ![Export button](img/import_export_export_button.png)
 
 1. Once the export is generated, you should receive an e-mail with a link to
    download the file:
 
-    ![Email download link](img/import_export_mail_link.png)
+   ![Email download link](img/import_export_mail_link.png)
 
 1. Alternatively, you can come back to the project settings and download the
    file from there, or generate a new export. Once the file available, the page
    should show the **Download export** button:
 
-    ![Download export](img/import_export_download_export.png)
+   ![Download export](img/import_export_download_export.png)
 
 ## Importing the project
 
-1. The GitLab project import feature is the first import option when creating a 
+1. The GitLab project import feature is the first import option when creating a
    new project. Click on **GitLab export**:
 
-    ![New project](img/import_export_new_project.png)
+   ![New project](img/import_export_new_project.png)
 
 1. Enter your project name and URL. Then select the file you exported previously:
 
-    ![Select file](img/import_export_select_file.png)
+   ![Select file](img/import_export_select_file.png)
 
 1. Click on **Import project** to begin importing. Your newly imported project
    page will appear soon.
diff --git a/doc/user/project/settings/index.md b/doc/user/project/settings/index.md
index 06b431decad..1c8cd0c7be3 100644
--- a/doc/user/project/settings/index.md
+++ b/doc/user/project/settings/index.md
@@ -96,7 +96,7 @@ To rename a repository:
 1. Hit **Rename project**.
 
 Remember that this can have unintended side effects since everyone with the
-old URL will not be able to push or pull. Read more about what happens with the 
+old URL will not be able to push or pull. Read more about what happens with the
 [redirects when renaming repositories](../index.md#redirects-when-changing-repository-paths).
 
 #### Transferring an existing project into another namespace