Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Commit 4adccc5

Browse files
jeff-matthewsjeff-matthews
authored
Merge pull request #5666 from magento/5248-ol-list-prefix-2
Fixed ordered list prefix (MD029) - Group 2
2 parents a61e1a0 + 8139e9e commit 4adccc5

File tree

11 files changed

+51
-48
lines changed

11 files changed

+51
-48
lines changed

‎guides/v2.2/release-notes/ReleaseNotes2.2.7CE.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -28,13 +28,13 @@ Follow these steps to download and apply this patch:
2828

2929
1. Access the Downloads page [here](https://magento.com/tech-resources/download#download2288).
3030

31-
2. Select the Git-based option from **Select your format**.
31+
1. Select the Git-based option from **Select your format**.
3232

33-
4. Download the patch and upload to a specific directory in your Magento installation such as `m2-hotfixes` (confirm that the directory is not accessible publicly).
33+
1. Download the patch and upload to a specific directory in your Magento installation such as `m2-hotfixes` (confirm that the directory is not accessible publicly).
3434

35-
5. From your project root, apply the patch.
 `git apply ./m2-hotfixes/<patch-file-name>`.
35+
1. From your project root, apply the patch.
 `git apply ./m2-hotfixes/<patch-file-name>`.
3636

37-
6. Refresh the cache from the Admin (**System** > **Cache Management**).
37+
1. Refresh the cache from the Admin (**System** > **Cache Management**).
3838

3939
## Highlights
4040

‎guides/v2.2/release-notes/ReleaseNotes2.2.7EE.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -29,15 +29,15 @@ Follow these steps to download and apply this patch:
2929

3030
1. Access [My Account](https://account.magento.com/customer/account/login).
3131

32-
2. Navigate to the **Downloads** tab. Select the Magento edition and version you need.
32+
1. Navigate to the **Downloads** tab. Select the Magento edition and version you need.
3333

34-
3. Select **Support Patches and Security Patches**, then **PRODSECBUG-2198**.
34+
1. Select **Support Patches and Security Patches**, then **PRODSECBUG-2198**.
3535

36-
4. Download the patch and upload to a specific directory in your Magento installation such as `m2-hotfixes` (confirm that the directory is not accessible publicly).
36+
1. Download the patch and upload to a specific directory in your Magento installation such as `m2-hotfixes` (confirm that the directory is not accessible publicly).
3737

38-
5. From your project root, apply the patch.
 `git apply ./m2-hotfixes/<patch-file-name>`.
38+
1. From your project root, apply the patch.
 `git apply ./m2-hotfixes/<patch-file-name>`.
3939

40-
6. Refresh the cache from the Admin (**System** > **Cache Management**).
40+
1. Refresh the cache from the Admin (**System** > **Cache Management**).
4141

4242
## Highlights
4343

‎guides/v2.2/release-notes/ReleaseNotes2.2.8CE.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -26,13 +26,13 @@ Follow these steps to download and apply this patch:
2626

2727
1. Access the Downloads page [here](https://magento.com/tech-resources/download#download2288).
2828

29-
2. Select the Git-based option from **Select your format**.
29+
1. Select the Git-based option from **Select your format**.
3030

31-
4. Download the patch and upload to a specific directory in your Magento installation such as `m2-hotfixes` (confirm that the directory is not accessible publicly).
31+
1. Download the patch and upload to a specific directory in your Magento installation such as `m2-hotfixes` (confirm that the directory is not accessible publicly).
3232

33-
5. From your project root, apply the patch.
 `git apply ./m2-hotfixes/<patch-file-name>`.
33+
1. From your project root, apply the patch.
 `git apply ./m2-hotfixes/<patch-file-name>`.
3434

35-
6. Refresh the cache from the Admin (**System** > **Cache Management**).
35+
1. Refresh the cache from the Admin (**System** > **Cache Management**).
3636

3737
## PayPal Payflow Pro active carding activity update
3838

@@ -1182,9 +1182,9 @@ If UPS Type is set to `United Parcel Service` in the UPS Shipping Method Config
11821182

11831183
1. Navigate to **Stores**  > **Settings**  > **Configuration**  >  **Sales**  > **Shipping Methods**. Then, expand the **UPS** section.
11841184

1185-
2. At the **UPS Type** field, clear the Use system value checkbox. Then, change **UPS Type** to `United Parcel Service XML`. The Gateway URL populates correctly when this value is selected.
1185+
1. At the **UPS Type** field, clear the Use system value checkbox. Then, change **UPS Type** to `United Parcel Service XML`. The Gateway URL populates correctly when this value is selected.
11861186

1187-
3. Tap **Save Config**.
1187+
1. Tap **Save Config**.
11881188

11891189
## Community contributions
11901190

‎guides/v2.2/release-notes/ReleaseNotes2.2.8EE.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -27,15 +27,15 @@ Follow these steps to download and apply this patch:
2727

2828
1. Access [My Account](https://account.magento.com/customer/account/login).
2929

30-
2. Navigate to the **Downloads** tab. Select the Magento edition and version you need.
30+
1. Navigate to the **Downloads** tab. Select the Magento edition and version you need.
3131

32-
3. Select **Support Patches and Security Patches**, then **PRODSECBUG-2198**.
32+
1. Select **Support Patches and Security Patches**, then **PRODSECBUG-2198**.
3333

34-
4. Download the patch and upload to a specific directory in your Magento installation such as `m2-hotfixes` (confirm that the directory is not accessible publicly).
34+
1. Download the patch and upload to a specific directory in your Magento installation such as `m2-hotfixes` (confirm that the directory is not accessible publicly).
3535

36-
5. From your project root, apply the patch.
 `git apply ./m2-hotfixes/<patch-file-name>`.
36+
1. From your project root, apply the patch.
 `git apply ./m2-hotfixes/<patch-file-name>`.
3737

38-
6. Refresh the cache from the Admin (**System** > **Cache Management**).
38+
1. Refresh the cache from the Admin (**System** > **Cache Management**).
3939

4040
## PayPal Payflow Pro active carding activity update
4141

@@ -1225,9 +1225,9 @@ If UPS Type is set to `United Parcel Service` in the UPS Shipping Method Config
12251225

12261226
1. Navigate to **Stores**  > **Settings**  > **Configuration**  >  **Sales**  > **Shipping Methods**. Then, expand the **UPS** section.
12271227

1228-
2. At the **UPS Type** field, clear the Use system value checkbox. Then, change **UPS Type** to `United Parcel Service XML`. The Gateway URL populates correctly when this value is selected.
1228+
1. At the **UPS Type** field, clear the Use system value checkbox. Then, change **UPS Type** to `United Parcel Service XML`. The Gateway URL populates correctly when this value is selected.
12291229

1230-
3. Tap **Save Config**.
1230+
1. Tap **Save Config**.
12311231

12321232
## Community contributions
12331233

‎guides/v2.2/release-notes/backward-incompatible-changes/reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ All changes are generated automatically using the codebase of the corresponding
1414
The changes are aggregated into two tables:
1515

1616
1. **Changes in classes** that contains backward incompatible changes made to the Magento classes
17-
2. **Changes in interfaces** that contains backward incompatible changes made to the Magento interfaces
17+
1. **Changes in interfaces** that contains backward incompatible changes made to the Magento interfaces
1818

1919
## 2.2.8 - 2.2.9 {#releases-2_2_8-2_2_9}
2020

‎guides/v2.3/performance-best-practices/advanced-js-bundling.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ It is designed to provide optimal bundles and be less error-prone than the built
1919
Bundling JavaScript modules for better performance is about reducing two things:
2020

2121
1. The number of server requests.
22-
2. The size of those server requests.
22+
1. The size of those server requests.
2323

2424
In a modular application, the number of server requests can reach into the hundreds. For example, the following screen shot shows only the start of the list of JavaScript modules loaded on the home page of a clean Magento installation.
2525

@@ -108,6 +108,7 @@ Full versions of the sample code used in this article are available here:
108108
#### 1\. Add a build.js file
109109

110110
Create a `build.js` file in the Magento root directory. This file will contain the entire build configuration for your bundles.
111+
111112
```javascript
112113
({
113114
optimize: 'none',
@@ -120,6 +121,7 @@ Later, we will change the `optimize:` setting from_ `none` to `uglify2` to minif
120121
#### 2\. Add RequireJS dependencies, shims, paths, and map
121122

122123
Add the following RequireJS build configuration nodes, `deps`, `shim`, `paths`, and `map`, to your build file:
124+
123125
```javascript
124126
({
125127
optimize: 'none',
@@ -143,6 +145,7 @@ Within this file, you will find multiple entries for each of the configuration n
143145
#### 4\. Add a modules node
144146

145147
At the end of the `build.js` file, add the modules[] array as a placeholder for the bundles you will define for your storefront later.
148+
146149
```javascript
147150
({
148151
optimize: 'none',
@@ -162,7 +165,7 @@ At the end of the `build.js` file, add the modules[] array as a placeholder for
162165
You can retrieve all the RequireJS module dependencies from your store's page types by using:
163166

164167
1. PhantomJS from the command line (assuming you have PhantomJS installed).
165-
2. RequireJS command in your browser's console.
168+
1. RequireJS command in your browser's console.
166169

167170
#### To use PhantomJS:
168171

‎guides/v2.3/release-notes/ReleaseNotes2.3.0Commerce.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -23,15 +23,15 @@ Follow these steps to download and apply this patch:
2323

2424
1. Access [My Account](https://account.magento.com/customer/account/login).
2525

26-
2. Navigate to the **Downloads** tab. Select the Magento edition and version you need.
26+
1. Navigate to the **Downloads** tab. Select the Magento edition and version you need.
2727

28-
3. Select **Support Patches and Security Patches**, then **PRODSECBUG-2198**.
28+
1. Select **Support Patches and Security Patches**, then **PRODSECBUG-2198**.
2929

30-
4. Download the patch and upload to a specific directory in your Magento installation such as `m2-hotfixes` (confirm that the directory is not accessible publicly).
30+
1. Download the patch and upload to a specific directory in your Magento installation such as `m2-hotfixes` (confirm that the directory is not accessible publicly).
3131

32-
5. From your project root, apply the patch.
 `git apply ./m2-hotfixes/<patch-file-name>`.
32+
1. From your project root, apply the patch.
 `git apply ./m2-hotfixes/<patch-file-name>`.
3333

34-
6. Refresh the cache from the Admin (**System** > Tools > **Cache Management**).
34+
1. Refresh the cache from the Admin (**System** > Tools > **Cache Management**).
3535

3636
## Highlights
3737

‎guides/v2.3/release-notes/ReleaseNotes2.3.0OpenSource.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,13 +22,13 @@ Follow these steps to download and apply this patch:
2222

2323
1. Access the Downloads page [here](https://magento.com/tech-resources/download#download2288).
2424

25-
2. Select the Git-based option from **Select your format**.
25+
1. Select the Git-based option from **Select your format**.
2626

27-
4. Download the patch and upload to a specific directory in your Magento installation such as `m2-hotfixes` (confirm that the directory is not accessible publicly).
27+
1. Download the patch and upload to a specific directory in your Magento installation such as `m2-hotfixes` (confirm that the directory is not accessible publicly).
2828

29-
5. From your project root, apply the patch.
 `git apply ./m2-hotfixes/<patch-file-name>`.
29+
1. From your project root, apply the patch.
 `git apply ./m2-hotfixes/<patch-file-name>`.
3030

31-
6. Refresh the cache from the Admin (**System** > **Cache Management**).
31+
1. Refresh the cache from the Admin (**System** > **Cache Management**).
3232

3333
## Highlights
3434

‎guides/v2.3/release-notes/ReleaseNotes2.3.1Commerce.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -29,15 +29,15 @@ Follow these steps to download and apply this patch:
2929

3030
1. Access [My Account](https://account.magento.com/customer/account/login).
3131

32-
2. Navigate to the **Downloads** tab. Select the Magento edition and version you need.
32+
1. Navigate to the **Downloads** tab. Select the Magento edition and version you need.
3333

34-
3. Select **Support Patches and Security Patches**, then **PRODSECBUG-2198**.
34+
1. Select **Support Patches and Security Patches**, then **PRODSECBUG-2198**.
3535

36-
4. Download the patch and upload to a specific directory in your Magento installation such as `m2-hotfixes` (confirm that the directory is not accessible publicly).
36+
1. Download the patch and upload to a specific directory in your Magento installation such as `m2-hotfixes` (confirm that the directory is not accessible publicly).
3737

38-
5. From your project root, apply the patch.
 `git apply ./m2-hotfixes/<patch-file-name>`.
38+
1. From your project root, apply the patch.
 `git apply ./m2-hotfixes/<patch-file-name>`.
3939

40-
6. Refresh the cache from the Admin (**System** > **Cache Management**).
40+
1. Refresh the cache from the Admin (**System** > **Cache Management**).
4141

4242
## PayPal Payflow Pro active carding activity update
4343

@@ -1873,9 +1873,9 @@ If UPS Type is set to `United Parcel Service` in the UPS Shipping Method Config
18731873

18741874
1. Navigate to **Stores**  > **Settings**  > **Configuration**  >  **Sales**  > **Shipping Methods**. Then, expand the **UPS** section.
18751875

1876-
2. At the **UPS Type** field, clear the Use system value checkbox. Then, change **UPS Type** to `United Parcel Service XML`. The Gateway URL populates correctly when this value is selected.
1876+
1. At the **UPS Type** field, clear the Use system value checkbox. Then, change **UPS Type** to `United Parcel Service XML`. The Gateway URL populates correctly when this value is selected.
18771877

1878-
3. Tap **Save Config**.
1878+
1. Tap **Save Config**.
18791879

18801880
* **Issue**: The Async/Bulk Web APIs support only the default store view. A hot fix for this issue will be available in the near future. This issue has been resolved with the Scope parameter for Async/Bulk API patch, which is now available. See [Patch for Magento Framework Message Queue and Store Scopes](https://community.magento.com/t5/Magento-DevBlog/Patch-for-Magento-Framework-Message-Queue-and-Store-Scopes/ba-p/135209) for a full discussion of this scope-related issue and patch contents.
18811881

‎guides/v2.3/release-notes/ReleaseNotes2.3.1OpenSource.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -27,13 +27,13 @@ Follow these steps to download and apply this patch:
2727

2828
1. Access the Downloads page [here](https://magento.com/tech-resources/download#download2288).
2929

30-
2. Select the Git-based option from **Select your format**.
30+
1. Select the Git-based option from **Select your format**.
3131

32-
4. Download the patch and upload to a specific directory in your Magento installation such as `m2-hotfixes` (confirm that the directory is not accessible publicly).
32+
1. Download the patch and upload to a specific directory in your Magento installation such as `m2-hotfixes` (confirm that the directory is not accessible publicly).
3333

34-
5. From your project root, apply the patch.
 `git apply ./m2-hotfixes/<patch-file-name>`.
34+
1. From your project root, apply the patch.
 `git apply ./m2-hotfixes/<patch-file-name>`.
3535

36-
6. Refresh the cache from the Admin (**System** > **Cache Management**).
36+
1. Refresh the cache from the Admin (**System** > **Cache Management**).
3737

3838
## PayPal Payflow Pro active carding activity update
3939

@@ -1736,9 +1736,9 @@ If UPS Type is set to `United Parcel Service` in the UPS Shipping Method Config
17361736

17371737
1. Navigate to **Stores**  > **Settings**  > **Configuration**  >  **Sales**  > **Shipping Methods**. Then, expand the **UPS** section.
17381738

1739-
2. At the **UPS Type** field, clear the Use system value checkbox. Then, change **UPS Type** to `United Parcel Service XML`. The Gateway URL populates correctly when this value is selected.
1739+
1. At the **UPS Type** field, clear the Use system value checkbox. Then, change **UPS Type** to `United Parcel Service XML`. The Gateway URL populates correctly when this value is selected.
17401740

1741-
3. Tap **Save Config**.
1741+
1. Tap **Save Config**.
17421742

17431743
* **Issue**: The Async/Bulk Web APIs support only the default store view. A hot fix for this issue will be available in the near future. This issue has been resolved with the Scope parameter for Async/Bulk API patch, which is now available. See [Patch for Magento Framework Message Queue and Store Scopes](https://community.magento.com/t5/Magento-DevBlog/Patch-for-Magento-Framework-Message-Queue-and-Store-Scopes/ba-p/135209) for a full discussion of this scope-related issue and patch contents.
17441744

‎guides/v2.3/release-notes/backward-incompatible-changes/reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ redirect_from:
99
The changes are aggregated into two tables:
1010

1111
1. **Changes in classes** that contains backward incompatible changes made to the PHP classes
12-
2. **Changes in interfaces** that contains backward incompatible changes made to the PHP interfaces
12+
1. **Changes in interfaces** that contains backward incompatible changes made to the PHP interfaces
1313

1414
## 2.3.1 - 2.3.2
1515

0 commit comments

Comments
 (0)