Markdown linting: Enable rule MD029 (#5698)

* Fixed errors in rest, test, and ui comps

* Fix errors in release notes

* Fixed errors in pattern-library and payment integrations

* Fixed errors in marketplace, migration, mrg, and mtf

* Fixed errors in install, js-dev, and inventory

* Applied peer review edits

* Applied peer review edits

* Removed forced numbering class

* Fixed errors in howdoi

* Fixed errors in get-started, graphql

* Fixed errors in frontend-dev-guide

* Fixed errors in ext-dev

* Fixed some errors in config

* Fixed some errors in config

* Applied edits from peer review

* Removed redundant TOC

* Fixed errors in config

* Fixed errors in coding standards, comp-mgr, contributor

* Disable rule

* Fixed errors in _vidoes, reporting, arch

* Fixed errors in includes (not cloud)

* Enable rule

* Fixed errors in cloud includes

* Fixed errors in cloud

Author: jeff-matthews

.github/ISSUE_TEMPLATE/BUG.md

@@ -14,8 +14,8 @@ about: Create an issue about a bug on the devdocs website
 <!-- (OPTIONAL) What needs to be done to replicate this issue? (provide Gist if needed) -->
 
 1. First Step
-2. Second Step
-3. Etc.
+1. Second Step
+1. Etc.
 
 ## Expected result
 

_checks/styles/style-rules-prod

@@ -22,7 +22,7 @@ rule 'MD025'
 exclude_rule 'MD026'
 exclude_rule 'MD027'
 exclude_rule 'MD028'
-exclude_rule 'MD029'
+rule 'MD029'
 exclude_rule 'MD030'
 exclude_rule 'MD031'
 exclude_rule 'MD032'

_includes/cloud/backup-db.md

@@ -3,33 +3,33 @@ We recommend creating a backup of your project before an upgrade. Use the follow
 {:.procedure}
 To back up your Integration environment database and code:
 
-1.  Create a local backup of the remote database.
+1. Create a local backup of the remote database.
 
-    ```bash
-    magento-cloud db:dump
-    ```
+   ```bash
+   magento-cloud db:dump
+   ```
 
-    {: .bs-callout-info }
-    The `magento-cloud db:dump` command runs the [mysqldump](https://dev.mysql.com/doc/refman/8.0/en/mysqldump.html) command with the `--single-transaction` flag, which allows you to back up your database without locking the tables.
+   {: .bs-callout-info }
+   The `magento-cloud db:dump` command runs the [mysqldump](https://dev.mysql.com/doc/refman/8.0/en/mysqldump.html) command with the `--single-transaction` flag, which allows you to back up your database without locking the tables.
 
-1.  Back up code and media.
+1. Back up code and media.
 
-    ```bash
-    php bin/magento setup:backup --code [--media]
-    ```
+   ```bash
+   php bin/magento setup:backup --code [--media]
+   ```
 
-    Optionally, you can omit `[--media]` if you have a large number of static files that are already in source control.
+   Optionally, you can omit `[--media]` if you have a large number of static files that are already in source control.
 
 {:.procedure}
 To back up your Staging or Production environment database before deploying:
 
-1.  Use SSH to log in to the remote server.
+1. Use SSH to log in to the remote server.
 
-2.  Create a database dump.
+1. Create a database dump.
 
-    ```bash
-    vendor/bin/ece-tools db-dump
-    ```
+   ```bash
+   vendor/bin/ece-tools db-dump
+   ```
 
--   We recommend setting the application in maintenance mode before doing a database dump in Production environments.
--   This creates an `dump-<timestamp>.sql.gz` archive file in your local project directory. See [Snapshot and backup management]({{ site.baseurl }}/guides/v2.2/cloud/project/project-webint-snap.html#db-dump).
+-  We recommend setting the application in maintenance mode before doing a database dump in Production environments.
+-  This creates an `dump-<timestamp>.sql.gz` archive file in your local project directory. See [Snapshot and backup management]({{ site.baseurl }}/guides/v2.2/cloud/project/project-webint-snap.html#db-dump).

_includes/cloud/enable-ssh.md

@@ -2,8 +2,8 @@ You must create an SSH key pair on every machine and workspace you and your team
 
 The SSH keys require the following:
 
-* Set up SSH keys as the [Magento file system owner]({{ page.baseurl }}/cloud/before/before-workspace-file-sys-owner.html).
-* Create the keys using the email address used for the GitHub account.
+*  Set up SSH keys as the [Magento file system owner]({{ page.baseurl }}/cloud/before/before-workspace-file-sys-owner.html).
+*  Create the keys using the email address used for the GitHub account.
 
 For more information on SSH keys, see the following:
 
@@ -33,8 +33,8 @@ If you do not have SSH keys, you need to generate the keys for adding to your Ma
 
 If you already have SSH keys, continue to:
 
-* [Add a public SSH key to your Magento account](#ssh-add-to-account) section
-* [Add your SSH key to your GitHub account](https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/)
+*  [Add a public SSH key to your Magento account](#ssh-add-to-account) section
+*  [Add your SSH key to your GitHub account](https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/)
 
 ## Create a new SSH key pair {#ssh-create-new-key-pair}
 
@@ -43,70 +43,70 @@ Use the `ssh-keygen` command to create an SSH key pair. `ssh-keygen` is typicall
 {:.procedure}
 To create an SSH key pair:
 
-1.  The command syntax follows, entering the email used for your GitHub account:
+1. The command syntax follows, entering the email used for your GitHub account:
 
-    ```bash
-    ssh-keygen -t rsa
-    ```
+   ```bash
+   ssh-keygen -t rsa
+   ```
 
-    GitHub also uses the key length `-b 4096` in the command. Follow the prompts to complete the key.
+   GitHub also uses the key length `-b 4096` in the command. Follow the prompts to complete the key.
 
-1.  When prompted to "Enter a file in which to save the key," press **Enter** to save the file to the default location. The prompt displays the location.
+1. When prompted to "Enter a file in which to save the key," press **Enter** to save the file to the default location. The prompt displays the location.
 
-1.  When prompted to enter a secure passphrase, enter a phrase to use like a password. Make note of this passphrase. You may be requested to enter it depending on tasks you complete using a terminal during development.
+1. When prompted to enter a secure passphrase, enter a phrase to use like a password. Make note of this passphrase. You may be requested to enter it depending on tasks you complete using a terminal during development.
 
-1.  After creating the SSH key pair, start the ssh-agent:
+1. After creating the SSH key pair, start the ssh-agent:
 
-    For Mac or Linux:
+   For Mac or Linux:
 
-    ```bash
-    eval "$(ssh-agent -s)"
-    ```
+   ```bash
+   eval "$(ssh-agent -s)"
+   ```
 
-    For Mac, you can edit the  `~/.ssh/config` file to automatically load keys into the ssh-agent and store passphrases in your keychain.
+   For Mac, you can edit the  `~/.ssh/config` file to automatically load keys into the ssh-agent and store passphrases in your keychain.
 
-    ```conf
-    Host *
-        AddKeysToAgent yes
-        UseKeychain yes
-        IdentityFile ~/.ssh/id_rsa
-    ```
+   ```conf
+   Host *
+       AddKeysToAgent yes
+       UseKeychain yes
+       IdentityFile ~/.ssh/id_rsa
+   ```
 
     For Windows:
 
     ```shell
     eval $(ssh-agent -s)
     ```
 
-1.  Add the SSH key to the ssh-agent. If you used a different name for the key file name, replace `id_rsa` with that file name.
+1. Add the SSH key to the ssh-agent. If you used a different name for the key file name, replace `id_rsa` with that file name.
 
-    For Mac:
+   For Mac:
 
-    ```bash
-    ssh-add -K ~/.ssh/id_rsa
-    ```
+   ```bash
+   ssh-add -K ~/.ssh/id_rsa
+   ```
 
-    For Windows or Linux:
+   For Windows or Linux:
 
-    ```shell
-    ssh-add ~/.ssh/id_rsa
-    ```
+   ```shell
+   ssh-add ~/.ssh/id_rsa
+   ```
 
-1.  [Add your SSH key to your GitHub account.](https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/) The instructions include Mac, Windows, and Linux.
+1. [Add your SSH key to your GitHub account.](https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/) The instructions include Mac, Windows, and Linux.
 
 ### Test the SSH keys {#test}
 
 After adding the SSH keys, test the SSH connection to GitHub:
 
 1. In the terminal, enter the following command:
 
-    ```bash
-    ssh -T [email protected]
-    ```
+   ```bash
+   ssh -T [email protected]
+   ```
 
-2. You may see a warning that the authenticity of the host can't be established followed by an RSA fingerprint. Enter `yes` to continue.
+1. You may see a warning that the authenticity of the host can't be established followed by an RSA fingerprint. Enter `yes` to continue.
 
-3. If successful, you should receive a success message. If you receive a permission denied error, see [Error: Permission denied (publickey)](https://help.github.com/articles/error-permission-denied-publickey) troubleshooting on GitHub.
+1. If successful, you should receive a success message. If you receive a permission denied error, see [Error: Permission denied (publickey)](https://help.github.com/articles/error-permission-denied-publickey) troubleshooting on GitHub.
 
 ## Add a public SSH key to your Magento account {#ssh-add-to-account}
 
@@ -120,43 +120,43 @@ You can add SSH keys to your account in any of the following ways:
 To add an SSH key using the CLI:
 
 1. Open a terminal application on your local.
-2. If you haven't done so already, log in (or switch to) the [Magento file system owner]({{ page.baseurl }}/cloud/before/before-workspace-file-sys-owner.html) to the server on which your SSH keys are located.
+1. If you haven't done so already, log in (or switch to) the [Magento file system owner]({{ page.baseurl }}/cloud/before/before-workspace-file-sys-owner.html) to the server on which your SSH keys are located.
 
-3. Log in to your project:
+1. Log in to your project:
 
-    ```bash
-    magento-cloud login
-    ```
+   ```bash
+   magento-cloud login
+   ```
 
-3. Add the key:
+1. Add the key:
 
-    ```bash
-    magento-cloud ssh-key:add ~/.ssh/id_rsa.pub
-    ```
+   ```bash
+   magento-cloud ssh-key:add ~/.ssh/id_rsa.pub
+   ```
 
 #### Add a key using the Project Web Interface {#add-key-web}
 
 You will select and add your SSH public key to each environment in your account.
 
-* Starter: Add to Master (Production) and any environments you create by branching from Master
-* Pro: Add to Master Integration environment. After your Staging and Production environments are provisioned, you can add the SSH keys to those environments.
+*  Starter: Add to Master (Production) and any environments you create by branching from Master
+*  Pro: Add to Master Integration environment. After your Staging and Production environments are provisioned, you can add the SSH keys to those environments.
 
 To add an SSH key using the Project Web Interface:
 
 1. Copy your SSH public key to the clipboard.
 
    If you do not already have SSH keys on that machine, see [GitHub documentation](https://help.github.com/articles/generating-an-ssh-key) to create them.
 
-2. Login and access your project through the [Project Web Interface](https://accounts.magento.cloud).
-3. In your selected branch, an icon displays if you do not have an SSH key added.
+1. Login and access your project through the [Project Web Interface](https://accounts.magento.cloud).
+1. In your selected branch, an icon displays if you do not have an SSH key added.
 
    ![No SSH key]({{ site.baseurl }}/common/images/cloud_ssh-key-install.png)
 
-4. Copy and paste the content of your public SSH key in the screen.
+1. Copy and paste the content of your public SSH key in the screen.
 
    ![Add SSH key]({{ site.baseurl }}/common/images/cloud_ssh-key-add.png)
 
-5. Follow the prompts on your screen to complete the task.
+1. Follow the prompts on your screen to complete the task.
 
 ## Set global Git variables
 

_includes/cloud/log-in-db.md

@@ -1,41 +1,41 @@
 The following steps provide an example of accessing a database:
 
-1.  SSH to the integration environment.
-
-    ```bash
-    magento-cloud ssh
-    ```
-
-1.  Find the database login information:
-
-    ```bash
-    php -r 'print_r(json_decode(base64_decode($_ENV["MAGENTO_CLOUD_RELATIONSHIPS"]))->database);'
-    ```
-
-    Sample output follows:
-
-    ```php
-    Array
-     (
-          [0] => stdClass Object
-            (
-               [username] => user
-               [password] =>
-               [ip] => 192.0.2.60
-               [host] => database.internal
-               [query] => stdClass Object
-                  (
-                    [is_master] => 1
-                  )
-               [path] => main
-               [scheme] => mysql
-               [port] => 3306
-            )
-        )
-    ```
-
-3.  Use the following command to connect to the database:
-
-    ```bash
-    mysql --host=<host> --user='<database username>' --password='<user password>' --port='<port>' --database='<path>'
-    ```
+1. SSH to the integration environment.
+
+   ```bash
+   magento-cloud ssh
+   ```
+
+1. Find the database login information:
+
+   ```bash
+   php -r 'print_r(json_decode(base64_decode($_ENV["MAGENTO_CLOUD_RELATIONSHIPS"]))->database);'
+   ```
+
+   Sample output follows:
+
+   ```php
+   Array
+    (
+         [0] => stdClass Object
+           (
+              [username] => user
+              [password] =>
+              [ip] => 192.0.2.60
+              [host] => database.internal
+              [query] => stdClass Object
+                 (
+                   [is_master] => 1
+                 )
+              [path] => main
+              [scheme] => mysql
+              [port] => 3306
+           )
+       )
+   ```
+
+1. Use the following command to connect to the database:
+
+   ```bash
+   mysql --host=<host> --user='<database username>' --password='<user password>' --port='<port>' --database='<path>'
+   ```

_includes/cloud/new-project-from-template.md

@@ -1,24 +1,24 @@
 1. Access your account. You can open the email you received from Magento Cloud ([email protected]) and click the _Access your project now_ link. Or you can log in to [your {{site.data.var.ee}} account](https://accounts.magento.cloud).
-2. Click the _This project has no code yet_ link next to the Project name.
+1. Click the _This project has no code yet_ link next to the Project name.
 
    ![Project without code]({{ site.baseurl }}/common/images/cloud_project_empty.png)
 
-3. Enter a name for the project.
+1. Enter a name for the project.
 
    ![Project name]({{ site.baseurl }}/common/images/cloud_project_name.png)
 
-4. Click **Create a blank site from a template** and click **Continue**. We recommend starting with the Magento template as your initial project option. If you have an existing Magento deployment, you can later import code, extensions, themes, and data after fully deploying this base Magento code.
+1. Click **Create a blank site from a template** and click **Continue**. We recommend starting with the Magento template as your initial project option. If you have an existing Magento deployment, you can later import code, extensions, themes, and data after fully deploying this base Magento code.
 
    ![Create a site using the sample Magento project]({{ site.baseurl }}/common/images/cloud_project_template.png){:width="650px"}
 
-5. When prompted, enter your {{site.data.var.ee}} [Magento authentication keys]({{ page.baseurl }}/install-gde/prereq/connect-auth.html) in the provided fields. You created these keys earlier in the Magento Marketplace. Enter the private and public keys and click **Finish**.
+1. When prompted, enter your {{site.data.var.ee}} [Magento authentication keys]({{ page.baseurl }}/install-gde/prereq/connect-auth.html) in the provided fields. You created these keys earlier in the Magento Marketplace. Enter the private and public keys and click **Finish**.
 
    ![Enter your authentication keys]({{ site.baseurl }}/common/images/cloud-project-magento-auth-creds.png){:width="650px"}
 
    The keys are added to the `auth.json` file in the repository `master` branch, required for all created branches and deployments.
 
-6. Wait a few minutes while the project deploys. A status of _Pending_ displays until completed, similar to the following:
+1. Wait a few minutes while the project deploys. A status of _Pending_ displays until completed, similar to the following:
 
    ![Your sample Magento project]({{ site.baseurl }}/common/images/cloud_project_template2.png){:width="650px"}
 
-7. After the project deploys, **Success** displays next to the name of your project.
+1. After the project deploys, **Success** displays next to the name of your project.