Standardize markdown in dev and workflow

Delete trailing whitespace, fix blockquotes, fix note
boxes, with indentation, clean up tables, etc.

8 files changed, 277 insertions, 277 deletions

diff --git a/doc/development/fe_guide/axios.md b/doc/development/fe_guide/axios.md
index 09b4a3c3d96..6e7cf523f36 100644
--- a/doc/development/fe_guide/axios.md
+++ b/doc/development/fe_guide/axios.md
@@ -38,7 +38,7 @@ Advantages over [`spyOn()`]:
 
 - no need to create response objects
 - does not allow call through (which we want to avoid)
-- simple API to test error cases 
+- simple API to test error cases
 - provides `replyOnce()` to allow for different responses
 
 We have also decided against using [axios interceptors] because they are not suitable for mocking.
diff --git a/doc/development/fe_guide/style_guide_js.md b/doc/development/fe_guide/style_guide_js.md
index d3fa350b847..125b11afcd0 100644
--- a/doc/development/fe_guide/style_guide_js.md
+++ b/doc/development/fe_guide/style_guide_js.md
@@ -21,31 +21,31 @@ See [our current .eslintrc](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/
 1. **Never Ever EVER** disable eslint globally for a file
 
    ```javascript
-     // bad
-     /* eslint-disable */
+   // bad
+   /* eslint-disable */
 
-     // better
-     /* eslint-disable some-rule, some-other-rule */
+   // better
+   /* eslint-disable some-rule, some-other-rule */
 
-     // best
-     // nothing :)
+   // best
+   // nothing :)
    ```
 
 1. If you do need to disable a rule for a single violation, try to do it as locally as possible
 
    ```javascript
-     // bad
-     /* eslint-disable no-new */
+   // bad
+   /* eslint-disable no-new */
 
-     import Foo from 'foo';
+   import Foo from 'foo';
 
-     new Foo();
+   new Foo();
 
-     // better
-     import Foo from 'foo';
+   // better
+   import Foo from 'foo';
 
-     // eslint-disable-next-line no-new
-     new Foo();
+   // eslint-disable-next-line no-new
+   new Foo();
    ```
 
 1. There are few rules that we need to disable due to technical debt. Which are:
@@ -56,16 +56,16 @@ See [our current .eslintrc](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/
    followed by any global declarations, then a blank newline prior to any imports or code.
 
    ```javascript
-     // bad
-     /* global Foo */
-     /* eslint-disable no-new */
-     import Bar from './bar';
+   // bad
+   /* global Foo */
+   /* eslint-disable no-new */
+   import Bar from './bar';
 
-     // good
-     /* eslint-disable no-new */
-     /* global Foo */
+   // good
+   /* eslint-disable no-new */
+   /* global Foo */
 
-     import Bar from './bar';
+   import Bar from './bar';
    ```
 
 1. **Never** disable the `no-undef` rule. Declare globals with `/* global Foo */` instead.
@@ -73,23 +73,23 @@ See [our current .eslintrc](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/
 1. When declaring multiple globals, always use one `/* global [name] */` line per variable.
 
    ```javascript
-     // bad
-     /* globals Flash, Cookies, jQuery */
+   // bad
+   /* globals Flash, Cookies, jQuery */
 
-     // good
-     /* global Flash */
-     /* global Cookies */
-     /* global jQuery */
+   // good
+   /* global Flash */
+   /* global Cookies */
+   /* global jQuery */
    ```
 
 1. Use up to 3 parameters for a function or class. If you need more accept an Object instead.
 
    ```javascript
-     // bad
-     fn(p1, p2, p3, p4) {}
+   // bad
+   fn(p1, p2, p3, p4) {}
 
-     // good
-     fn(options) {}
+   // good
+   fn(options) {}
    ```
 
 #### Modules, Imports, and Exports
@@ -97,32 +97,32 @@ See [our current .eslintrc](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/
 1. Use ES module syntax to import modules
 
    ```javascript
-     // bad
-     const SomeClass = require('some_class');
+   // bad
+   const SomeClass = require('some_class');
 
-     // good
-     import SomeClass from 'some_class';
+   // good
+   import SomeClass from 'some_class';
 
-     // bad
-     module.exports = SomeClass;
+   // bad
+   module.exports = SomeClass;
 
-     // good
-     export default SomeClass;
+   // good
+   export default SomeClass;
    ```
 
    Import statements are following usual naming guidelines, for example object literals use camel case:
 
    ```javascript
-     // some_object file
-     export default {
-       key: 'value',
-     };
+   // some_object file
+   export default {
+     key: 'value',
+   };
 
-     // bad
-     import ObjectLiteral from 'some_object';
+   // bad
+   import ObjectLiteral from 'some_object';
 
-     // good
-     import objectLiteral from 'some_object';
+   // good
+   import objectLiteral from 'some_object';
    ```
 
 1. Relative paths: when importing a module in the same directory, a child
@@ -171,22 +171,22 @@ See [our current .eslintrc](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/
 1. Avoid adding to the global namespace.
 
    ```javascript
-     // bad
-     window.MyClass = class { /* ... */ };
+   // bad
+   window.MyClass = class { /* ... */ };
 
-     // good
-     export default class MyClass { /* ... */ }
+   // good
+   export default class MyClass { /* ... */ }
    ```
 
 1. Side effects are forbidden in any script which contains export
 
    ```javascript
-     // bad
-     export default class MyClass { /* ... */ }
+   // bad
+   export default class MyClass { /* ... */ }
 
-     document.addEventListener("DOMContentLoaded", function(event) {
-       new MyClass();
-     }
+   document.addEventListener("DOMContentLoaded", function(event) {
+     new MyClass();
+   }
    ```
 
 #### Data Mutation and Pure functions
@@ -257,17 +257,17 @@ See [our current .eslintrc](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/
    `.reduce` or `.filter`
 
    ```javascript
-     const users = [ { name: 'Foo' }, { name: 'Bar' } ];
+   const users = [ { name: 'Foo' }, { name: 'Bar' } ];
 
-     // bad
-     users.forEach((user, index) => {
-       user.id = index;
-     });
+   // bad
+   users.forEach((user, index) => {
+     user.id = index;
+   });
 
-     // good
-     const usersWithId = users.map((user, index) => {
-       return Object.assign({}, user, { id: index });
-     });
+   // good
+   const usersWithId = users.map((user, index) => {
+     return Object.assign({}, user, { id: index });
+   });
    ```
 
 #### Parse Strings into Numbers
@@ -275,14 +275,14 @@ See [our current .eslintrc](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/
 1. `parseInt()` is preferable over `Number()` or `+`
 
    ```javascript
-     // bad
-     +'10' // 10
+   // bad
+   +'10' // 10
 
-     // good
-     Number('10') // 10
+   // good
+   Number('10') // 10
 
-     // better
-     parseInt('10', 10);
+   // better
+   parseInt('10', 10);
    ```
 
 #### CSS classes used for JavaScript
@@ -290,15 +290,15 @@ See [our current .eslintrc](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/
 1. If the class is being used in Javascript it needs to be prepend with `js-`
 
    ```html
-     // bad
-     <button class="add-user">
-       Add User
-     </button>
+   // bad
+   <button class="add-user">
+     Add User
+   </button>
 
-     // good
-     <button class="js-add-user">
-       Add User
-     </button>
+   // good
+   <button class="js-add-user">
+     Add User
+   </button>
    ```
 
 ### Vue.js
@@ -315,41 +315,41 @@ Please check this [rules][eslint-plugin-vue-rules] for more documentation.
 1. Use a function in the bundle file to instantiate the Vue component:
 
    ```javascript
-     // bad
-     class {
-       init() {
-         new Component({})
-       }
+   // bad
+   class {
+     init() {
+       new Component({})
      }
+   }
 
-     // good
-     document.addEventListener('DOMContentLoaded', () => new Vue({
-       el: '#element',
-       components: {
-         componentName
-       },
-       render: createElement => createElement('component-name'),
-     }));
+   // good
+   document.addEventListener('DOMContentLoaded', () => new Vue({
+     el: '#element',
+     components: {
+       componentName
+     },
+     render: createElement => createElement('component-name'),
+   }));
    ```
 
 1. Do not use a singleton for the service or the store
 
    ```javascript
-     // bad
-     class Store {
-       constructor() {
-         if (!this.prototype.singleton) {
-           // do something
-         }
+   // bad
+   class Store {
+     constructor() {
+       if (!this.prototype.singleton) {
+         // do something
        }
      }
+   }
 
-     // good
-     class Store {
-       constructor() {
-         // do something
-       }
+   // good
+   class Store {
+     constructor() {
+       // do something
      }
+   }
    ```
 
 1. Use `.vue` for Vue templates. Do not use `%template` in HAML.
@@ -360,36 +360,36 @@ Please check this [rules][eslint-plugin-vue-rules] for more documentation.
 1. **Reference Naming**: Use PascalCase for their instances:
 
    ```javascript
-     // bad
-     import cardBoard from 'cardBoard.vue'
+   // bad
+   import cardBoard from 'cardBoard.vue'
 
-     components: {
-       cardBoard,
-     };
+   components: {
+     cardBoard,
+   };
 
-     // good
-     import CardBoard from 'cardBoard.vue'
+   // good
+   import CardBoard from 'cardBoard.vue'
 
-     components: {
-       CardBoard,
-     };
+   components: {
+     CardBoard,
+   };
    ```
 
 1. **Props Naming:**  Avoid using DOM component prop names.
 1. **Props Naming:** Use kebab-case instead of camelCase to provide props in templates.
 
    ```javascript
-     // bad
-     <component class="btn">
+   // bad
+   <component class="btn">
 
-     // good
-     <component css-class="btn">
+   // good
+   <component css-class="btn">
 
-     // bad
-     <component myProp="prop" />
+   // bad
+   <component myProp="prop" />
 
-     // good
-     <component my-prop="prop" />
+   // good
+   <component my-prop="prop" />
    ```
 
 [#34371]: https://gitlab.com/gitlab-org/gitlab-ce/issues/34371
@@ -401,37 +401,37 @@ Please check this [rules][eslint-plugin-vue-rules] for more documentation.
    1. With more than one attribute, all attributes should be on a new line:
 
       ```javascript
-        // bad
-        <component v-if="bar"
-            param="baz" />
+      // bad
+      <component v-if="bar"
+          param="baz" />
 
-        <button class="btn">Click me</button>
+      <button class="btn">Click me</button>
 
-        // good
-        <component
-          v-if="bar"
-          param="baz"
-        />
+      // good
+      <component
+        v-if="bar"
+        param="baz"
+      />
 
-        <button class="btn">
-          Click me
-        </button>
+      <button class="btn">
+        Click me
+      </button>
       ```
 
    1. The tag can be inline if there is only one attribute:
 
       ```javascript
-        // good
-          <component bar="bar" />
+      // good
+        <component bar="bar" />
 
-        // good
-          <component
-            bar="bar"
-            />
+      // good
+        <component
+          bar="bar"
+          />
 
-        // bad
-         <component
-            bar="bar" />
+      // bad
+       <component
+          bar="bar" />
       ```
 
 #### Quotes
@@ -439,15 +439,15 @@ Please check this [rules][eslint-plugin-vue-rules] for more documentation.
 1. Always use double quotes `"` inside templates and single quotes `'` for all other JS.
 
    ```javascript
-     // bad
-     template: `
-       <button :class='style'>Button</button>
-     `
+   // bad
+   template: `
+     <button :class='style'>Button</button>
+   `
 
-     // good
-     template: `
-       <button :class="style">Button</button>
-     `
+   // good
+   template: `
+     <button :class="style">Button</button>
+   `
    ```
 
 #### Props
@@ -455,37 +455,37 @@ Please check this [rules][eslint-plugin-vue-rules] for more documentation.
 1. Props should be declared as an object
 
    ```javascript
-     // bad
-     props: ['foo']
-
-     // good
-     props: {
-       foo: {
-         type: String,
-         required: false,
-         default: 'bar'
-       }
+   // bad
+   props: ['foo']
+
+   // good
+   props: {
+     foo: {
+       type: String,
+       required: false,
+       default: 'bar'
      }
+   }
    ```
 
 1. Required key should always be provided when declaring a prop
 
    ```javascript
-     // bad
-     props: {
-       foo: {
-         type: String,
-       }
+   // bad
+   props: {
+     foo: {
+       type: String,
      }
+   }
 
-     // good
-     props: {
-       foo: {
-         type: String,
-         required: false,
-         default: 'bar'
-       }
+   // good
+   props: {
+     foo: {
+       type: String,
+       required: false,
+       default: 'bar'
      }
+   }
    ```
 
 1. Default key should be provided if the prop is not required.
@@ -493,30 +493,30 @@ Please check this [rules][eslint-plugin-vue-rules] for more documentation.
    On those a default key should not be provided.
 
    ```javascript
-     // good
-     props: {
-       foo: {
-         type: String,
-         required: false,
-       }
+   // good
+   props: {
+     foo: {
+       type: String,
+       required: false,
      }
+   }
 
-     // good
-     props: {
-       foo: {
-         type: String,
-         required: false,
-         default: 'bar'
-       }
+   // good
+   props: {
+     foo: {
+       type: String,
+       required: false,
+       default: 'bar'
      }
+   }
 
-     // good
-     props: {
-       foo: {
-         type: String,
-         required: true
-       }
+   // good
+   props: {
+     foo: {
+       type: String,
+       required: true
      }
+   }
    ```
 
 #### Data
@@ -524,17 +524,17 @@ Please check this [rules][eslint-plugin-vue-rules] for more documentation.
 1. `data` method should always be a function
 
    ```javascript
-     // bad
-     data: {
-       foo: 'foo'
-     }
+   // bad
+   data: {
+     foo: 'foo'
+   }
 
-     // good
-     data() {
-       return {
-         foo: 'foo'
-       };
-     }
+   // good
+   data() {
+     return {
+       foo: 'foo'
+     };
+   }
    ```
 
 #### Directives
@@ -542,31 +542,31 @@ Please check this [rules][eslint-plugin-vue-rules] for more documentation.
 1. Shorthand `@` is preferable over `v-on`
 
    ```javascript
-     // bad
-     <component v-on:click="eventHandler"/>
+   // bad
+   <component v-on:click="eventHandler"/>
 
-     // good
-     <component @click="eventHandler"/>
+   // good
+   <component @click="eventHandler"/>
    ```
 
 1. Shorthand `:` is preferable over `v-bind`
 
    ```javascript
-     // bad
-     <component v-bind:class="btn"/>
+   // bad
+   <component v-bind:class="btn"/>
 
-     // good
-     <component :class="btn"/>
+   // good
+   <component :class="btn"/>
    ```
 
 1. Shorthand `#` is preferable over `v-slot`
 
    ```javascript
-     // bad
-     <template v-slot:header></template>
+   // bad
+   <template v-slot:header></template>
 
-     // good
-     <template #header></template>
+   // good
+   <template #header></template>
    ```
 
 #### Closing tags
@@ -574,11 +574,11 @@ Please check this [rules][eslint-plugin-vue-rules] for more documentation.
 1. Prefer self closing component tags
 
    ```javascript
-     // bad
-     <component></component>
+   // bad
+   <component></component>
 
-     // good
-     <component />
+   // good
+   <component />
    ```
 
 #### Ordering
@@ -610,48 +610,48 @@ When using `v-for` you need to provide a *unique* `:key` attribute for each item
 1. If the elements of the array being iterated have an unique `id` it is advised to use it:
 
    ```html
-     <div
-       v-for="item in items"
-       :key="item.id"
-     >
-       <!-- content -->
-     </div>
+   <div
+     v-for="item in items"
+     :key="item.id"
+   >
+     <!-- content -->
+   </div>
    ```
 
 1. When the elements being iterated don't have a unique id, you can use the array index as the `:key` attribute
 
    ```html
-     <div
-       v-for="(item, index) in items"
-       :key="index"
-     >
-       <!-- content -->
-     </div>
+   <div
+     v-for="(item, index) in items"
+     :key="index"
+   >
+     <!-- content -->
+   </div>
    ```
 
 1. When using `v-for` with `template` and there is more than one child element, the `:key` values must be unique. It's advised to use `kebab-case` namespaces.
 
    ```html
-     <template v-for="(item, index) in items">
-       <span :key="`span-${index}`"></span>
-       <button :key="`button-${index}`"></button>
-     </template>
+   <template v-for="(item, index) in items">
+     <span :key="`span-${index}`"></span>
+     <button :key="`button-${index}`"></button>
+   </template>
    ```
 
 1. When dealing with nested `v-for` use the same guidelines as above.
 
    ```html
-     <div
-       v-for="item in items"
-       :key="item.id"
+   <div
+     v-for="item in items"
+     :key="item.id"
+   >
+     <span
+       v-for="element in array"
+       :key="element.id"
      >
-       <span
-         v-for="element in array"
-         :key="element.id"
-       >
-         <!-- content -->
-       </span>
-     </div>
+       <!-- content -->
+     </span>
+   </div>
    ```
 
 Useful links:
@@ -664,19 +664,19 @@ Useful links:
 1. Tooltips: Do not rely on `has-tooltip` class name for Vue components
 
    ```javascript
-     // bad
-     <span
-       class="has-tooltip"
-       title="Some tooltip text">
-       Text
-     </span>
+   // bad
+   <span
+     class="has-tooltip"
+     title="Some tooltip text">
+     Text
+   </span>
 
-     // good
-     <span
-       v-tooltip
-       title="Some tooltip text">
-       Text
-     </span>
+   // good
+   <span
+     v-tooltip
+     title="Some tooltip text">
+     Text
+   </span>
    ```
 
 1. Tooltips: When using a tooltip, include the tooltip directive, `./app/assets/javascripts/vue_shared/directives/tooltip.js`
@@ -684,13 +684,13 @@ Useful links:
 1. Don't change `data-original-title`.
 
    ```javascript
-     // bad
-     <span data-original-title="tooltip text">Foo</span>
+   // bad
+   <span data-original-title="tooltip text">Foo</span>
 
-     // good
-     <span title="tooltip text">Foo</span>
+   // good
+   <span title="tooltip text">Foo</span>
 
-     $('span').tooltip('_fixTitle');
+   $('span').tooltip('_fixTitle');
    ```
 
 ### The Javascript/Vue Accord
diff --git a/doc/development/fe_guide/vuex.md b/doc/development/fe_guide/vuex.md
index 9eeaee4482f..557d3132d71 100644
--- a/doc/development/fe_guide/vuex.md
+++ b/doc/development/fe_guide/vuex.md
@@ -313,7 +313,7 @@ export default {
 
 1. Do not call a mutation directly. Always use an action to commit a mutation. Doing so will keep consistency throughout the application. From Vuex docs:
 
-   >  why don't we just call store.commit('action') directly? Well, remember that mutations must be synchronous? Actions aren't. We can perform asynchronous operations inside an action.
+   > Why don't we just call store.commit('action') directly? Well, remember that mutations must be synchronous? Actions aren't. We can perform asynchronous operations inside an action.
 
    ```javascript
      // component.vue
diff --git a/doc/development/interacting_components.md b/doc/development/interacting_components.md
index 74d52d808e2..5e6dc8d460a 100644
--- a/doc/development/interacting_components.md
+++ b/doc/development/interacting_components.md
@@ -9,8 +9,8 @@ when making _backend_ changes that might involve multiple features or [component
 
 ## Uploads
 
-GitLab supports uploads to [object storage]. That means every feature and 
-change that affects uploads should also be tested against [object storage], 
+GitLab supports uploads to [object storage]. That means every feature and
+change that affects uploads should also be tested against [object storage],
 which is _not_ enabled by default in [GDK](https://gitlab.com/gitlab-org/gitlab-development-kit).
 
 When working on a related feature, make sure to enable and test it
diff --git a/doc/development/new_fe_guide/modules/dirty_submit.md b/doc/development/new_fe_guide/modules/dirty_submit.md
index 6c03958b463..217743ea395 100644
--- a/doc/development/new_fe_guide/modules/dirty_submit.md
+++ b/doc/development/new_fe_guide/modules/dirty_submit.md
@@ -1,7 +1,6 @@
 # Dirty Submit
 
-> [Introduced][ce-21115] in GitLab 11.3.  
-> [dirty_submit][dirty-submit]
+> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/21115) in GitLab 11.3.
 
 ## Summary
 
@@ -9,6 +8,9 @@ Prevent submitting forms with no changes.
 
 Currently handles `input`, `textarea` and `select` elements.
 
+Also, see [the code](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/app/assets/javascripts/dirty_submit/)
+within the GitLab project.
+
 ## Usage
 
 ```js
@@ -18,6 +20,3 @@ new DirtySubmitForm(document.querySelector('form'));
 // or
 new DirtySubmitForm(document.querySelectorAll('form'));
 ```
-
-[ce-21115]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/21115
-[dirty-submit]: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/app/assets/javascripts/dirty_submit/
\ No newline at end of file
diff --git a/doc/development/new_fe_guide/style/javascript.md b/doc/development/new_fe_guide/style/javascript.md
index 802ebd12d92..b742d567f41 100644
--- a/doc/development/new_fe_guide/style/javascript.md
+++ b/doc/development/new_fe_guide/style/javascript.md
@@ -192,4 +192,4 @@ rules only if you are invoking/instantiating existing code modules.
 - [class-method-use-this](http://eslint.org/docs/rules/class-methods-use-this)
 
 > Note: Disable these rules on a per line basis. This makes it easier to refactor
-  in the future. E.g. use `eslint-disable-next-line` or `eslint-disable-line`.
+> in the future. E.g. use `eslint-disable-next-line` or `eslint-disable-line`.
diff --git a/doc/development/shell_scripting_guide/index.md b/doc/development/shell_scripting_guide/index.md
index ae7f2154682..0809f8b1a0a 100644
--- a/doc/development/shell_scripting_guide/index.md
+++ b/doc/development/shell_scripting_guide/index.md
@@ -24,7 +24,8 @@ Having said all of the above, we recommend staying away from shell scripts
 as much as possible. A language like Ruby or Python (if required for
 consistency with codebases that we leverage) is almost always a better choice.
 The high-level interpreted languages have more readable syntax, offer much more
-mature capabilities for unit-testing, linting, and error reporting.  
+mature capabilities for unit-testing, linting, and error reporting.
+
 Use shell scripts only if there's a strong restriction on project's
 dependencies size or any other requirements that are more important
 in a particular case.
@@ -48,12 +49,12 @@ that is:
 
 This section describes the tools that should be made a mandatory part of
 a project's CI pipeline if it contains shell scripts. These tools
-automate shell code formatting, checking for errors or vulnerabilities, etc.   
+automate shell code formatting, checking for errors or vulnerabilities, etc.
 
 ### Linting
 
 We're using the [ShellCheck](https://www.shellcheck.net/) utility in its default configuration to lint our
-shell scripts. 
+shell scripts.
 
 All projects with shell scripts should use this GitLab CI/CD job:
 
@@ -98,7 +99,7 @@ NOTE: **Note:**
 This is a work in progress.
 
 It is an [ongoing effort](https://gitlab.com/gitlab-org/gitlab-ce/issues/64016) to evaluate different tools for the
-automated testing of shell scripts (like [BATS](https://github.com/sstephenson/bats)).  
+automated testing of shell scripts (like [BATS](https://github.com/sstephenson/bats)).
 
 ## Code Review
 
diff --git a/doc/development/testing_guide/review_apps.md b/doc/development/testing_guide/review_apps.md
index 7843fc4c874..11449712a04 100644
--- a/doc/development/testing_guide/review_apps.md
+++ b/doc/development/testing_guide/review_apps.md
@@ -255,8 +255,8 @@ that a machine will hit the "too many mount points" problem in the future.
 thousands of unused Docker images.**
 
   > We have to start somewhere and improve later. Also, we're using the
-  CNG-mirror project to store these Docker images so that we can just wipe out
-  the registry at some point, and use a new fresh, empty one.
+  > CNG-mirror project to store these Docker images so that we can just wipe out
+  > the registry at some point, and use a new fresh, empty one.
 
 **How do we secure this from abuse? Apps are open to the world so we need to
 find a way to limit it to only us.**