Merge pull request #5669 from magento/5248-ol-list-prefix-4

Fixed ordered list prefix (MD029) - Group 4

Author: jeff-matthews

guides/v2.2/marketplace/eqp/auth.md

@@ -6,7 +6,7 @@ title: Authentication
 All API requests must be authenticated using [HTTP Basic Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication). The REST APIs use a two-step process to authenticate a client application and authorize access to resources:
 
 1. Obtain a session token using an application ID and secret.
-2. Provide the session token as an HTTP Authorization Bearer header to access a resource.
+1. Provide the session token as an HTTP Authorization Bearer header to access a resource.
 
 First, you must create an application on the [Developer Portal](https://developer.magento.com) to obtain an application ID and secret for sandbox and production endpoints.
 
@@ -17,8 +17,8 @@ Information about how to create applications will be announced when the EQP REST
 
 You must use an application ID and secret to obtain a session token. See the following list for examples of an application ID and secret:
 
-* **id**—AQ17NZ49WC
-* **secret**—8820c99614d65f923df7660276f20e029d73e2ca
+*  **id**—AQ17NZ49WC
+*  **secret**—8820c99614d65f923df7660276f20e029d73e2ca
 
 The following endpoint grants an application session token:
 
@@ -61,10 +61,10 @@ A successful HTTP 200 OK response will be sent for a valid application ID and se
 }
 ```
 
-* The `mage_id` value will identify the user account associated with the client application.
-* The `ust` value (user session token) must be used as the `Authorization Bearer` header for all subsequent API calls.
-* The session token is valid only for the time specified in `expires_in` (seconds).
-* When session token expires, a new token must be obtained as described above.
+*  The `mage_id` value will identify the user account associated with the client application.
+*  The `ust` value (user session token) must be used as the `Authorization Bearer` header for all subsequent API calls.
+*  The session token is valid only for the time specified in `expires_in` (seconds).
+*  When session token expires, a new token must be obtained as described above.
 
 ## Authorization Bearer
 

guides/v2.2/marketplace/eqp/packages.md

@@ -382,8 +382,8 @@ You can submit a package in either of the following ways:
 *  A single POST request with all required fields set. You must explicitly indicate that you are for technical and marketing review using the `action` parameter.
 *  A series of requests, typically in the following order:
    1. A single POST request with the minimum required fields set and `action` set to `draft` in either `technical`, `marketing`, or both. This request accepts the new package and saves it on the Developer Portal for further updates. It returns a unique `submission_id` for subsequent PUT operations.
-   2. One or more PUT requests in which you configure the package parameters. In these requests, set `action` to `draft` in `technical`, `marketing`, or both.
-   3. A final PUT request indicating submission for `technical`, `marketing`, or both.
+   1. One or more PUT requests in which you configure the package parameters. In these requests, set `action` to `draft` in `technical`, `marketing`, or both.
+   1. A final PUT request indicating submission for `technical`, `marketing`, or both.
 
 You can update one or more parameters in `draft` mode, but the API does not check for validation errors.
 

guides/v2.2/migration/migration-manually.md

@@ -31,13 +31,13 @@ This section applies to you *only* if you store media files in the Magento datab
 
 1. Log in to the Magento 1 Admin Panel as an administrator.
 
-2. Click **System** > **Configuration** > ADVANCED > **System**.
+1. Click **System** > **Configuration** > ADVANCED > **System**.
 
-3. In the right pane, scroll to **Storage Configuration for Media**.
+1. In the right pane, scroll to **Storage Configuration for Media**.
 
-4. From the **Select Media Database** list, click the name of your [media storage](https://glossary.magento.com/media-storage) database.
+1. From the **Select Media Database** list, click the name of your [media storage](https://glossary.magento.com/media-storage) database.
 
-5. Click **Synchronize**.
+1. Click **Synchronize**.
 
 Then, repeat the same steps in your Magento 2 Admin panel.
 
@@ -49,9 +49,9 @@ However, do *not* copy the `.htaccess` files located in the Magento 1 `media` fo
 
 ## Storefront design
 
-* Design in files (CSS, JS, templates, [XML](https://glossary.magento.com/xml) layouts) changed its location and format
+*  Design in files (CSS, JS, templates, [XML](https://glossary.magento.com/xml) layouts) changed its location and format
 
-* [Layout](https://glossary.magento.com/layout) Updates stored in database. Placed through Magento 1 Admin in [CMS](https://glossary.magento.com/cms) Pages, CMS Widgets, [Category](https://glossary.magento.com/category) Pages and Product Pages
+*  [Layout](https://glossary.magento.com/layout) Updates stored in database. Placed through Magento 1 Admin in [CMS](https://glossary.magento.com/cms) Pages, CMS Widgets, [Category](https://glossary.magento.com/category) Pages and Product Pages
 
 ## Access Control Lists (ACLs)
 
@@ -67,4 +67,4 @@ You may adjust the time zone for a database entity using the `\Migration\Handler
 {:.ref-header}
 Related topics
 
-* <a href="{{ page.baseurl }}/migration/migration-migrate-after.html">After migration</a>
+*  <a href="{{ page.baseurl }}/migration/migration-migrate-after.html">After migration</a>

guides/v2.2/migration/migration-migrate-data.md

@@ -10,7 +10,7 @@ menu_order: 2
 ## Before you start: routine preparation
 
 1. Log in to Magento server as [the file system owner]({{ page.baseurl }}/install-gde/prereq/file-sys-perms-over.html).
-2. Change to the Magento installation directory or make sure it is added to your system PATH.
+1. Change to the Magento installation directory or make sure it is added to your system PATH.
 
 See the [First steps]({{ page.baseurl }}/migration/migration-migrate.html#migration-command-run-first) section for more details.
 

guides/v2.2/migration/migration-migrate-settings.md

@@ -18,7 +18,7 @@ According to our data migration [order]({{ page.baseurl }}/migration/migration-m
 
 1. Log in to Magento server as [the file system owner]({{ page.baseurl }}/install-gde/prereq/file-sys-perms-over.html).
 
-2. Change to the Magento `/bin` directory or make sure it is added to your system PATH.
+1. Change to the Magento `/bin` directory or make sure it is added to your system PATH.
 
 {: .bs-callout-info }
 Ensure Magento is deployed in default mode. Developer mode can cause validation errors in the migration tool.
@@ -35,9 +35,9 @@ bin/magento migrate:settings [-r|--reset] {<path to config.xml>}
 
 where:
 
-* `[-r|--reset]` is an optional argument that starts migration from the beginning. You can use this argument for testing migration
+*  `[-r|--reset]` is an optional argument that starts migration from the beginning. You can use this argument for testing migration
 
-* `{<path to config.xml>}` is the absolute file system path to the migration tool's [`config.xml`]({{page.baseurl}}/migration/migration-tool-configure.html#migration-configure) file; this argument is required.
+*  `{<path to config.xml>}` is the absolute file system path to the migration tool's [`config.xml`]({{page.baseurl}}/migration/migration-tool-configure.html#migration-configure) file; this argument is required.
 
 {: .bs-callout-info }
 This command does not migrate all configuration settings. Verify all settings in the Magento 2 [Admin](https://glossary.magento.com/admin) before proceeding.
@@ -74,4 +74,4 @@ For more details, see the [Settings migration mode]({{ page.baseurl }}/migration
 
 ## Next migration step
 
-* [Migrate data]({{ page.baseurl }}/migration/migration-migrate-data.html)
+*  [Migrate data]({{ page.baseurl }}/migration/migration-migrate-data.html)

guides/v2.2/migration/migration-migrate.md

@@ -17,9 +17,9 @@ During the migration process, **do not:**
 
 1. Make any changes in the Magento 1 [Admin](https://glossary.magento.com/admin) except for order management (shipping, creating invoice, credit memos, etc.)
 
-2. Alter any code
+1. Alter any code
 
-3. Make changes in the Magento 2 Admin and [storefront](https://glossary.magento.com/storefront)
+1. Make changes in the Magento 2 Admin and [storefront](https://glossary.magento.com/storefront)
 
 {: .bs-callout .bs-callout-tip }
 All operations in Magento 1 storefront are allowed at this time.
@@ -46,9 +46,9 @@ where:
 
 1. `<mode>` may be: [`settings`]({{ page.baseurl }}/migration/migration-migrate-settings.html), [`data`]({{ page.baseurl }}/migration/migration-migrate-data.html), or [`delta`]({{ page.baseurl }}/migration/migration-migrate-delta.html)
 
-2. `[-r|--reset]` is an optional argument that starts migration from the beginning. You can use this argument for testing migration.
+1. `[-r|--reset]` is an optional argument that starts migration from the beginning. You can use this argument for testing migration.
 
-3. `{<path to config.xml>}` is the absolute file system path to `config.xml`; this argument is required.
+1. `{<path to config.xml>}` is the absolute file system path to `config.xml`; this argument is required.
 
 {: .bs-callout-info }
 Logs are written to the `<magento_root>/var/` directory.
@@ -58,7 +58,7 @@ Logs are written to the `<magento_root>/var/` directory.
 When we created the Data Migration Tool, we assumed the following data transfer sequence:
 
 1. [Settings]({{ page.baseurl }}/migration/migration-migrate-settings.html)
-2. [Data]({{ page.baseurl }}/migration/migration-migrate-data.html)
-3. [Changes]({{ page.baseurl }}/migration/migration-migrate-delta.html)
+1. [Data]({{ page.baseurl }}/migration/migration-migrate-data.html)
+1. [Changes]({{ page.baseurl }}/migration/migration-migrate-delta.html)
 
 That's why we strongly recommend to keep this order to migrate quickly and with no issues.

guides/v2.2/migration/migration-overview-how.md

@@ -7,18 +7,18 @@ This topic provides a high-level overview of how data is migrated from Magento 1
 
 ## Terminology
 
-* **Modes** - an ordered set of operations for migrating data from Magento 1.x to Magento 2.x.
-* **Steps** - the tasks in a mode that define the kinds of data to migrate.
-* **Stages** - the tasks in step that validate, transfer, and verify the data.
-* **Map files** - XML files that define the rules and connections between Magento 1.x and Magento 2.x data structures for completing the stages.
+*  **Modes** - an ordered set of operations for migrating data from Magento 1.x to Magento 2.x.
+*  **Steps** - the tasks in a mode that define the kinds of data to migrate.
+*  **Stages** - the tasks in step that validate, transfer, and verify the data.
+*  **Map files** - XML files that define the rules and connections between Magento 1.x and Magento 2.x data structures for completing the stages.
 
 ## Modes
 
 The Data Migration Tool splits the migration process into three phases or *modes* in order to transfer and adapt data from Magento 1.x to Magento 2.x. The three modes are listed here and must be run in this order:
 
 1. **Settings Mode**: migrates the system configuration and website-related settings.
-2. **Data Mode**: migrates database assets in bulk.
-3. **Delta Mode**: migrates incremental changes (changes since the last run), such as new customers and orders.
+1. **Data Mode**: migrates database assets in bulk.
+1. **Delta Mode**: migrates incremental changes (changes since the last run), such as new customers and orders.
 
 ![Migration Modes]
 
@@ -32,9 +32,9 @@ The Data Migration Tool uses a list of *steps* within each mode to migrate a par
 
 Within each step are three *stages* that are always executed in this order to ensure the data gets properly migrated:
 
-1. **Integrity Check**: Compares the table field names, types, 
and other info to verify compatibility between Magento 1 and 2 data structures.
-2. **Data Transfer**: Transfers the data table by table from Magento 1 and 2.
-3. **Volume Check**: Compares the number of records 
between tables to verify that the transfer was successful.
+1. **Integrity Check**: Compares the table field names, types, and other info to verify compatibility between Magento 1 and 2 data structures.
+1. **Data Transfer**: Transfers the data table by table from Magento 1 and 2.
+1. **Volume Check**: Compares the number of records between tables to verify that the transfer was successful.
 
 ![Migration Steps]
 
@@ -64,4 +64,4 @@ Mapping files are discussed in more detail in [Data Migration Tool Technical Spe
 [Migration Steps]: {{site.baseurl}}/common/images/MigrationSteps2.png
 {: height="247px" width="930px"}
 
-[Migration Flow]: {{site.baseurl}}/common/images/migration_flow.png
+[Migration Flow]: {{site.baseurl}}/common/images/migration_flow.png