Fixed ordered list prefix (MD029) - Group 12

guides/v2.2/config-guide/cli/config-cli-subcommands-config-mgmt-set.md

@@ -50,55 +50,69 @@ To set a configuration value, you must know at least one of the following:
 
 See the following references:
 
-*   [Sensitive and system-specific configuration paths reference]({{ page.baseurl }}/config-guide/prod/config-reference-sens.html)
-*   [Payment configuration paths reference]({{ page.baseurl }}/config-guide/prod/config-reference-payment.html)
-*   [Other configuration paths reference]({{ page.baseurl }}/config-guide/prod/config-reference-most.html)
-*   [Magento Enterprise B2B Extension configuration paths reference]({{ page.baseurl }}/config-guide/prod/config-reference-b2b.html)
+*  [Sensitive and system-specific configuration paths reference]({{ page.baseurl }}/config-guide/prod/config-reference-sens.html)
+*  [Payment configuration paths reference]({{ page.baseurl }}/config-guide/prod/config-reference-payment.html)
+*  [Other configuration paths reference]({{ page.baseurl }}/config-guide/prod/config-reference-most.html)
+*  [Magento Enterprise B2B Extension configuration paths reference]({{ page.baseurl }}/config-guide/prod/config-reference-b2b.html)
 
 ### Find the scope code
 
 You can find the scope code either in the Magento database or in the Magento [Admin](https://glossary.magento.com/admin). See one of the following sections for more information.
 
 #### Find the scope code in the Admin
 
-1.  Log into Admin as a user who can view websites and store views.
-2.  Click **Stores** > **Settings** > **All Stores**.
-3.  In the right pane, click the name of the website or store view to see its code.
+1. Log into Admin as a user who can view websites and store views.
+1. Click **Stores** > **Settings** > **All Stores**.
+1. In the right pane, click the name of the website or store view to see its code.
 
-    The following figure shows a sample website code.
+   The following figure shows a sample website code.
 
-    ![Get a website or store view code from the Admin]({{ site.baseurl }}/common/images/config_configset_website-code.png){:width="450px"}
-4.  Continue with [Set configuration values](#config-cli-config-set).
+   ![Get a website or store view code from the Admin]({{ site.baseurl }}/common/images/config_configset_website-code.png){:width="450px"}
+
+1. Continue with [Set configuration values](#config-cli-config-set).
 
 #### Find the scope code in the database
 
 Scope codes for websites and store views are stored in the Magento database in the `store_website` and `store` tables, respectively.
 
 To find the values in the database:
 
-1.  Connect to the Magento database:
+1. Connect to the Magento database:
+
+   ```bash
+   mysql -u <magento database username> -p
+   ```
 
-        mysql -u <magento database username> -p
-2.  Enter the following commands:
+1. Enter the following commands:
 
-        use <magento database name>;
-        SELECT * FROM store;
-        SELECT * FROM store_website;
+   ```shell
+   use <magento database name>;
+   ```
 
-    A sample result follows:
+   ```shell
+   SELECT * FROM store;
+   ```
 
-        [mysql]> SELECT * FROM store_website;
-        +------------+-------+--------------+------------+------------------+------------+
-        | website_id | code  | name         | sort_order | default_group_id | is_default |
-        +------------+-------+--------------+------------+------------------+------------+
-        |          0 | admin | Admin        |          0 |                0 |          0 |
-        |          1 | base  | Main Website |          0 |                1 |          1 |
-        |          2 | test1 | Test Website |          0 |                3 |          0 |
-        +------------+-------+--------------+------------+------------------+------------+
+   ```shell
+   SELECT * FROM store_website;
+   ```
 
-    Use the value in the `code` column.
+   A sample result follows:
 
-3.  Continue with the next section.
+   ```terminal
+   [mysql]> SELECT * FROM store_website;
+   +------------+-------+--------------+------------+------------------+------------+
+   | website_id | code  | name         | sort_order | default_group_id | is_default |
+   +------------+-------+--------------+------------+------------------+------------+
+   |          0 | admin | Admin        |          0 |                0 |          0 |
+   |          1 | base  | Main Website |          0 |                1 |          1 |
+   |          2 | test1 | Test Website |          0 |                3 |          0 |
+   +------------+-------+--------------+------------+------------------+------------+
+   ```
+
+   Use the value in the `code` column.
+
+1. Continue with the next section.
 
 ## Set configuration values {#config-cli-config-set}
 
@@ -107,6 +121,7 @@ To set system-specific configuration values on Magento 2.2.0 - 2.2.3, use:
 ```bash
 bin/magento config:set [--scope="..."] [--scope-code="..."] [-l | --lock] path value
 ```
+
 To set system-specific configuration values on Magento 2.2.4 and higher (on the 2.2 branch), use:
 
 ```bash
@@ -136,12 +151,14 @@ If you use the `--lock`, `--lock-env`, or `--lock-config` option to set or chang
 
 If you enter an incorrect configuration path, this command returns an error:
 
-    The "wrong/config/path" does not exist
+```terminal
+The "wrong/config/path" does not exist
+```
 
 See one of the following sections for more information:
 
-*   [Set configuration values that can be edited in the Magento Admin](#config-cli-config-set-edit)
-*   [Set configuration values that cannot be edited in the Magento Admin](#config-cli-config-file)
+*  [Set configuration values that can be edited in the Magento Admin](#config-cli-config-set-edit)
+*  [Set configuration values that cannot be edited in the Magento Admin](#config-cli-config-file)
 
 ### Set configuration values that can be edited in the Magento Admin {#config-cli-config-set-edit}
 
@@ -201,9 +218,9 @@ bin/magento config:show [--scope[="..."]] [--scope-code[="..."]] path
 
 In this case:
 
-* `--scope` is the scope of configuration (`default`, `website`, `store`). The default value is `default`.
-* `--scope-code` is the scope code of configuration (website code or store view code).
-* `path` is the configuration path in format `first_part/second_part/third_part/etc` *(required)*.
+*  `--scope` is the scope of configuration (`default`, `website`, `store`). The default value is `default`.
+*  `--scope-code` is the scope code of configuration (website code or store view code).
+*  `path` is the configuration path in format `first_part/second_part/third_part/etc` *(required)*.
 
 {:.bs-callout .bs-callout-info}
 The `bin/magento config:show` command displays the values of any [encrypted values]({{ page.baseurl }}/config-guide/prod/config-reference-sens.html) as a series of asterisks: `******`.

guides/v2.2/config-guide/cli/config-cli-subcommands-cron.md

@@ -8,6 +8,7 @@ functional_areas:
 ---
 
 ## Overview of cron {#config-cli-cron-overview}
+
 {% include config/cron-overview.md %}
 
 To run cron in a web browser, see [Secure cron.php to run in a browser]({{ page.baseurl }}/config-guide/secy/secy-cron.html)
@@ -26,10 +27,13 @@ You should remove the Magento crontab only before uninstalling the Magento appli
 
 To remove the Magento crontab:
 
-1.  Log in as or switch to the [Magento file system owner]({{ page.baseurl }}/install-gde/prereq/file-sys-perms-over.html).
-2.  Change to the Magento installation directory.
-3.  Enter the following command:
-      `bin/magento cron:remove`
+1. Log in as or switch to the [Magento file system owner]({{ page.baseurl }}/install-gde/prereq/file-sys-perms-over.html).
+1. Change to the Magento installation directory.
+1. Enter the following command:
+
+   ```bash
+   bin/magento cron:remove
+   ```
 
 {:.bs-callout .bs-callout-info}
 This command has no effect on cron jobs outside the `#~ MAGENTO START` and `#~ MAGENTO END` comments in your crontab.
@@ -39,18 +43,22 @@ This command has no effect on cron jobs outside the `#~ MAGENTO START` and `#~ M
 Command options:
 
 ```bash
-  bin/magento cron:run [--group="<cron group name>"]
+bin/magento cron:run [--group="<cron group name>"]
 ```
 
 where `--group` specifies the cron group to run (omit this option to run cron for all groups)
 
 To run the indexing cron job, enter:
 
-`bin/magento cron:run --group index`
+```bash
+bin/magento cron:run --group index`
+```
 
 To run the default cron job, enter:
 
-`bin/magento cron:run --group default`
+```bash
+bin/magento cron:run --group default
+```
 
 To set up custom cron jobs and groups, see [Configure custom cron jobs and cron groups]({{ page.baseurl }}/config-guide/cron/custom-cron.html).
 
@@ -65,23 +73,23 @@ All exceptions from cron jobs are logged by `\Magento\Cron\Observer\ProcessCronQ
 
 In addition to being logged in `cron.log`:
 
-- Failed jobs with `ERROR` and `MISSED` statuses are logged to the `<install_directory>/var/log/support_report.log`.
+-  Failed jobs with `ERROR` and `MISSED` statuses are logged to the `<install_directory>/var/log/support_report.log`.
 
-- Jobs with an `ERROR` status are always logged as `CRITICAL` in `<install_directory>/var/log/exception.log`.
+-  Jobs with an `ERROR` status are always logged as `CRITICAL` in `<install_directory>/var/log/exception.log`.
 
-- Jobs with a `MISSED` status are logged as `INFO` in the `<install_directory>/var/log/debug.log` directory (developer mode only).
+-  Jobs with a `MISSED` status are logged as `INFO` in the `<install_directory>/var/log/debug.log` directory (developer mode only).
 
 {%
 include note.html
 type='info'
 content='All cron data is also written to the `cron_schedule` table in the Magento database. The table provides a history of cron jobs, including:
 
-- Job ID and code
-- Status
-- Created date
-- Scheduled date
-- Executed date
-- Finished date
+-  Job ID and code
+-  Status
+-  Created date
+-  Scheduled date
+-  Executed date
+-  Finished date
 
 To see records in the table, log in to the Magento database on the command line and enter `SELECT * from cron_schedule;`.'
 %}