Merge pull request #5689 from magento/5248-ol-list-prefix-15

Fixed ordered list prefix (MD029) - Group 15

Author: jeff-matthews

_includes/comp-man/backup.md

@@ -22,7 +22,7 @@ To back up:
    {:.bs-callout .bs-callout-info}
    We strongly recommend you <em>do</em> back up in the event of issues.
 
-2. Wait while backups are created and continue with any of the following:
+1. Wait while backups are created and continue with any of the following:
 
 The following page displays to confirm a successful backup.
 

_includes/config/multi-site_verify.md

@@ -1,15 +1,20 @@
 Unless you have DNS set up for your stores' URLs, you must add a static route to the host in your `hosts` file:
 
 1. Locate your operating system's [`hosts` file](https://en.wikipedia.org/wiki/Hosts_(file)#Location_in_the_file_system).
-2. Add the static route in the format:
+1. Add the static route in the format:
 
-        <ip address> french.mysite.mg
-        <ip address> german.mysite.mg
-3. Go to one of the following URLs in your browser:
+   ```conf
+   <ip address> french.mysite.mg
+   <ip address> german.mysite.mg
+   ```
 
-        http://mysite.mg/admin
-        http://french.mysite.mg/frenchstoreview
-        http://german.mysite.mg/germanstoreview
+1. Go to one of the following URLs in your browser:
+
+   ```http
+   http://mysite.mg/admin
+   http://french.mysite.mg/frenchstoreview
+   http://german.mysite.mg/germanstoreview
+   ```
 
 You're done!
 

_includes/config/secure-ws-apache_step1.md

@@ -12,7 +12,7 @@ First, see if you have the Apache `htpasswd` utility is installed as follows:
 
    If a path displays, it is installed; if the command returns no output, `htpasswd` is not installed.
 
-2. If necessary, install `htpasswd`:
+1. If necessary, install `htpasswd`:
 
    *  Ubuntu: `apt-get -y install apache2-utils`
    *  CentOS: `yum -y install httpd-tools`

_includes/config/split-db.md

@@ -3,14 +3,14 @@
 Create checkout and OMS master databases as follows:
 
 1. Log in to your database server as any user.
-2. Enter the following command to get to a MySQL command prompt:
+1. Enter the following command to get to a MySQL command prompt:
 
    ```bash
    mysql -u root -p
    ```
 
-3. Enter the MySQL `root` user's password when prompted.
-4. Enter the following commands in the order shown to create database instances named `magento_quote` and `magento_sales` with the same usernames and passwords:
+1. Enter the MySQL `root` user's password when prompted.
+1. Enter the following commands in the order shown to create database instances named `magento_quote` and `magento_sales` with the same usernames and passwords:
 
    ```shell
    create database magento_quote;
@@ -28,9 +28,9 @@ Create checkout and OMS master databases as follows:
    GRANT ALL ON magento_sales.* TO magento_sales@localhost IDENTIFIED BY 'magento_sales';
    ```
 
-5. Enter `exit` to quit the command prompt.
+1. Enter `exit` to quit the command prompt.
 
-6. Verify the databases, one at a time:
+1. Verify the databases, one at a time:
 
    Checkout database:
 

_includes/config/split-deploy/example_build-sync.md

@@ -1,28 +1,28 @@
 To update your build system:
 
 1. Log in to your build system as, or switch to, the [Magento file system owner](https://glossary.magento.com/magento-file-system-owner).
-2. Change to the build system's Magento root directory.
-3. Pull the changes to `app/etc/config.php` from source control.
+1. Change to the build system's Magento root directory.
+1. Pull the changes to `app/etc/config.php` from source control.
 
    The Git command follows:
 
    ```bash
    git pull mconfig m2.2_deploy
    ```
 
-4. Compile code:
+1. Compile code:
 
    ```bash
    php bin/magento setup:di:compile
    ```
 
-5. After code has been compiled, generate static view files:
+1. After code has been compiled, generate static view files:
 
    ```bash
    php bin/magento setup:static-content:deploy -f
    ```
 
-6. Check the changes into source control.
+1. Check the changes into source control.
 
    The Git command follows:
 

_includes/design/icon-fonts.md

@@ -2,8 +2,8 @@ If you want to add your own icons, each icon will need to be in its own SVG file
 
 1. Go to [https://icomoon.io/app/](https://icomoon.io/app/) or download this app in Chrome web store.
 
-2. Upload your icons in SVG format into the app.
+1. Upload your icons in SVG format into the app.
 
-3. Specify desired font names and specify the Unicode characters to map the icons. Setting the icons to Private User Area will disable screen-readers or other accessibility tools to read your icon's characters (read "Unicode" section here).
+1. Specify desired font names and specify the Unicode characters to map the icons. Setting the icons to Private User Area will disable screen-readers or other accessibility tools to read your icon's characters (read "Unicode" section here).
 
-4. Then initialize a download in the app to generate the icon font and [CSS](https://glossary.magento.com/css) style sheet.
+1. Then initialize a download in the app to generate the icon font and [CSS](https://glossary.magento.com/css) style sheet.

_includes/install/allowoverrides22.md

@@ -10,40 +10,40 @@ Failure to enable these settings typically results in no styles displaying on yo
    *  Ubuntu: `vim /etc/apache2/sites-available/default`
    *  CentOS: `vim /etc/httpd/conf/httpd.conf`
 
-2. Locate the block that starts with:
+1. Locate the block that starts with:
 
    *  Ubuntu 12: `<Directory /var/www/>`
    *  Ubuntu 14 or CentOS: `<Directory /var/www/html>`
 
-3. Change the value of `AllowOverride` to `<value from Apache site>`.
+1. Change the value of `AllowOverride` to `<value from Apache site>`.
 
-    An example for Ubuntu 12 follows.
+   An example for Ubuntu 12 follows.
 
-    ```conf
-    <Directory /var/www/>
-    Options Indexes FollowSymLinks MultiViews
-    AllowOverride <value from Apache site>
-    Order allow,deny
-    Allow from all
-    <Directory>
-    ```
+   ```conf
+   <Directory /var/www/>
+   Options Indexes FollowSymLinks MultiViews
+   AllowOverride <value from Apache site>
+   Order allow,deny
+   Allow from all
+   <Directory>
+   ```
 
    {:.bs-callout .bs-callout-info}
    The preceding values for `Order` might not work in all cases. For more information, see the Apache documentation ([2.2](https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#order)), [2.4](https://httpd.apache.org/docs/2.4/mod/mod_authz_host.html#order)).
 
-4. Save the file and exit the text editor.
-5. *Ubuntu only*. Configure Apache to use the `mod_rewrite` module.
+1. Save the file and exit the text editor.
+1. *Ubuntu only*. Configure Apache to use the `mod_rewrite` module.
 
-    ```bash
-    cd /etc/apache2/mods-enabled
-    ```
+   ```bash
+   cd /etc/apache2/mods-enabled
+   ```
 
-    ```bash
-    ln -s ../mods-available/rewrite.load
-    ```
+   ```bash
+   ln -s ../mods-available/rewrite.load
+   ```
 
-6. If you changed Apache settings, restart Apache.
+1. If you changed Apache settings, restart Apache.
 
-    ```bash
-    service apache2 restart
-    ```
+   ```bash
+   service apache2 restart
+   ```

_includes/install/auth-json.md

@@ -21,7 +21,7 @@ When choosing token permissions, select all checkboxes in the `repo` scope. Comp
 ### Create `auth.json` file
 
 1. Log in to your Magento server as the [Magento file system owner]({{ page.baseurl }}/install-gde/prereq/file-sys-perms-over.html).
-2. Create the `auth.json` file in the user's home directory. For example, if `magento_user` is your Unix username, then create `/home/magento_user/.composer/auth.json`.
+1. Create the `auth.json` file in the user's home directory. For example, if `magento_user` is your Unix username, then create `/home/magento_user/.composer/auth.json`.
 
 ### Edit `auth.json` file
 

_includes/install/auth-tokens-get.md

@@ -3,15 +3,15 @@ The `repo.magento.com` repository is where Magento 2 and third-party Composer pa
 To create authentication keys:
 
 1. Log in to the [Magento Marketplace](https://marketplace.magento.com){:target="_blank"}. If you don't have an account, click **Register**.
-2. Click your account name in the top-right of the page and select **My Profile**.
+1. Click your account name in the top-right of the page and select **My Profile**.
 
-3. Click **Access Keys** in the Marketplace tab.
+1. Click **Access Keys** in the Marketplace tab.
 
    ![Get your secure access keys on Magento Marketplace]({{ site.baseurl }}/common/images/cloud_access-key.png){:width="500px"}
 
-4. Click **Create a New Access Key**. Enter a specific name for the keys (e.g., the name of the developer receiving the keys) and click **OK**.
+1. Click **Create a New Access Key**. Enter a specific name for the keys (e.g., the name of the developer receiving the keys) and click **OK**.
 
-5. New public and private keys are now associated with your account that you can click to copy. Save this information or keep the page open when working with your Magento project. Use the **Public key** as your username and the **Private key** as your password.
+1. New public and private keys are now associated with your account that you can click to copy. Save this information or keep the page open when working with your Magento project. Use the **Public key** as your username and the **Private key** as your password.
 
 ### Manage your authentication keys
 
@@ -24,9 +24,9 @@ You can also disable or delete authentication keys. For example, you can disable
 You cannot delete or disable keys you created by signing in to your [magento.com account](https://www.magentocommerce.com/products/customer/account/login){:target="_blank"}. To manage those keys:
 
 1. Log in to your [magento.com account](https://www.magentocommerce.com/products/customer/account/login){:target="_blank"}.
-2. Click **My Account** at the top of the page.
-3. Click **Account Settings** > **Downloads Access Token**.
+1. Click **My Account** at the top of the page.
+1. Click **Account Settings** > **Downloads Access Token**.
 
    ![Access your keys]({{ site.baseurl }}/common/images/connect_keys1.png){:width="200px"}
 
-4. Click **Generate new token** to replace and disable an existing token.
+1. Click **Generate new token** to replace and disable an existing token.

_includes/install/composer-clone.md

@@ -13,14 +13,14 @@ To install Composer:
 
 1. Change to or create an empty directory on your Magento server.
 
-2. Enter the following commands:
+1. Enter the following commands:
 
-    ```bash
-    curl -sS https://getcomposer.org/installer | php
-    ```
+   ```bash
+   curl -sS https://getcomposer.org/installer | php
+   ```
 
-    ```bash
-    mv composer.phar /usr/local/bin/composer
-    ```
+   ```bash
+   mv composer.phar /usr/local/bin/composer
+   ```
 
 For additional installation options, see the [Composer installation documentation](https://getcomposer.org/download/).

_includes/install/file-system-umask.md

@@ -7,33 +7,33 @@ We recommend changing the umask on a one-user or shared hosting system only. If
 
 The default umask (with no `magento_umask` specified) is `002`, which means:
 
-* 775 for directories, which means full control by the user, full control by the group, and enables everyone to traverse the directory. These permissions are typically required by shared hosting providers.
+*  775 for directories, which means full control by the user, full control by the group, and enables everyone to traverse the directory. These permissions are typically required by shared hosting providers.
 
-* 664 for files, which means writable by the user, writable by the group, and read-only for everyone else
+*  664 for files, which means writable by the user, writable by the group, and read-only for everyone else
 
 A common suggestion is to use a value of `022` in the `magento_umask` file, which means:
 
-* 755 for directories: full control for the user, and everyone else can traverse directories.
-* 644 for files: read-write permissions for the user, and read-only for everyone else.
+*  755 for directories: full control for the user, and everyone else can traverse directories.
+*  644 for files: read-write permissions for the user, and read-only for everyone else.
 
 To set `magento_umask`:
 
 1. In a command line terminal, log in to your Magento server as a [Magento file system owner][].
-2. Navigate to the Magento install directory:
+1. Navigate to the Magento install directory:
 
    ```bash
    cd <Magento install directory>
    ```
 
-3. Use the following command to create a file named `magento_umask` and write the `umask` value to it.
+1. Use the following command to create a file named `magento_umask` and write the `umask` value to it.
 
    ```bash
    echo <desired umask number> > magento_umask
    ```
 
    You should now have a file named `magento_umask` in the `<Magento install dir>` with the only content being the `umask` number.
 
-4. Log out and log back in as the [Magento file system owner][] to apply the changes.
+1. Log out and log back in as the [Magento file system owner][] to apply the changes.
 
 <!-- Link Definitions -->
 

_includes/install/flow-diagram.md

@@ -9,7 +9,7 @@ The diagram shows the following:
    *  [2.2.x system requirements]({{ site.gdeurl22 }}install-gde/system-requirements-tech.html)
    *  [2.3.x system requirements]({{ site.gdeurl23 }}install-gde/system-requirements-tech.html)
 
-2. Get the Magento software.
+1. Get the Magento software.
 
    *  For simplicity, get a compressed {{site.data.var.ce}} or {{site.data.var.ee}} [archive]({{ page.baseurl }}/install-gde/prereq/zip_install.html), extract it on your Magento server, and start your installation.
 
@@ -20,12 +20,12 @@ The diagram shows the following:
    {:.bs-callout .bs-callout-info}
    To be able to use the Web Setup Wizard to install or upgrade the Magento software, or to manage extensions you get from Magento Marketplace, you must either get a compressed archive or a Composer metapackage. If you clone the GitHub repository, you *cannot* use the Web Setup Wizard to upgrade the Magento software and extensions. You must upgrade using [Composer and Git commands]({{ page.baseurl }}/install-gde/install/cli/dev_options.html).
 
-3. Install the Magento software using either the Web Setup Wizard or command line.
+1. Install the Magento software using either the Web Setup Wizard or command line.
 
    For simplicity, only the Web Setup Wizard is shown in the diagram.
 
    At each step, the Web Setup Wizard validates the information you entered. As shown in the preceding diagram, if validation fails, you must manually fix the issues before you proceed.
 
    If the step fails because prerequisite software isn't set up correctly, review our [Prerequisites]({{ page.baseurl }}/install-gde/prereq/prereq-overview.html).
 
-4. Verify the installation by viewing your storefront and the Magento Admin.
+1. Verify the installation by viewing your storefront and the Magento Admin.

_includes/install/releasenotes/ce_install_20.md

@@ -35,7 +35,7 @@ composer create-project --repository=https://repo.magento.com/ magento/project-c
 After you get the Open Source software:
 
 1. [Set file system ownership and permissions]({{ page.baseurl }}/install-gde/prereq/file-system-perms.html).
-2. Install the Magento software:
+1. Install the Magento software:
 
    *  [Web Setup Wizard]({{ page.baseurl }}/install-gde/install/web/install-web.html)
    *  [Command line]({{ page.baseurl }}/install-gde/install/cli/install-cli.html)

_includes/install/releasenotes/ee_install_20.md

@@ -35,7 +35,7 @@ composer create-project --repository=https://repo.magento.com/ magento/project-e
 After you get the Commerce software:
 
 1. [Set file system ownership and permissions]({{ page.baseurl }}/install-gde/prereq/file-system-perms.html).
-2. Install the Magento software:
+1. Install the Magento software:
 
    *  [Web Setup Wizard]({{ page.baseurl }}/install-gde/install/web/install-web.html)
    *  [Command line]({{ page.baseurl }}/install-gde/install/cli/install-cli.html)

_includes/install/releasenotes/get-ce-software_zip.md

@@ -11,7 +11,7 @@ Archives are available in the following formats: `.zip`, `.tar.bz2`, `.tar.gz`
 To get the Magento Open Source software archive:
 
 1. Go to [http://magento.com/download](http://magento.com/download){:target="_blank"}.
-2. Choose either the software or the software and sample data:
+1. Choose either the software or the software and sample data:
 
    *  `Magento-CE-<version>.*` (without sample data)
    *  `Magento-CE-<version>+Samples.*` (with sample data)