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

Commit 149953f

Browse files
authored
Merge pull request #6778 from JosephMaxwell/patch-6
Small grammar updates
2 parents 3155d33 + ae52762 commit 149953f

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

src/guides/v2.3/howdoi/checkout/checkout_payment.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -159,7 +159,7 @@ This configuration is stored in the `window.checkoutConfig` variable that is def
159159

160160
In order to get access to the system configuration, your payment method or a group of payment methods has to implement the [`\Magento\Checkout\Model\ConfigProviderInterface`]({{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Checkout/Model/ConfigProviderInterface.php) interface, and the class implementing it must be injected to the composite config provider via DI [frontend](https://glossary.magento.com/frontend) configuration. The following code samples illustrate this.
161161

162-
A sample `.php` class implementing `\Magento\Checkout\Model\ConfigProviderInterface`:
162+
This is a sample `.php` file implementing `\Magento\Checkout\Model\ConfigProviderInterface`:
163163

164164
```php?start_inline=1
165165
class MyCustomPaymentConfigProvider implements \Magento\Checkout\Model\ConfigProviderInterface
@@ -175,7 +175,7 @@ class MyCustomPaymentConfigProvider implements \Magento\Checkout\Model\ConfigPro
175175
}
176176
```
177177

178-
A sample DI configuration file of a custom module `<your_module_dir>/etc/frontend/di.xml`:
178+
Here is the associated sample DI configuration file of a custom module `<your_module_dir>/etc/frontend/di.xml`:
179179

180180
```xml
181181
...

src/guides/v2.3/javascript-dev-guide/javascript/requirejs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ You can also use the `map` configuration to override a JS module with a custom J
5252

5353
### paths {#requirejs-config-paths}
5454

55-
The `paths` configuration, similar to `map`, is used for aliasing not just any real AMD module that calls `define()`, but also any JS file (event from a URL), HTML templates, etc. Magento uses this to alias URLs and third party libraries.
55+
The `paths` configuration, similar to `map`, is used for aliasing not just any real AMD module that calls `define()`, but also any JS file (even from a URL), HTML templates, etc. Magento uses this to alias URLs and third party libraries.
5656

5757
```javascript
5858
paths: {
@@ -95,7 +95,7 @@ shim: {
9595

9696
### mixins {#requirejs-config-mixin}
9797

98-
The `mixins` configuration is used to overwrite component methods of an AMD module which returns either a UI component,a jQuery widget, or a JS object. Unlike the above configuration properties, the `mixins` property is under the `config` property, apart from the parent object called **config**.
98+
The `mixins` configuration is used to overwrite component methods of an AMD module which returns either a UI component, a jQuery widget, or a JS object. Unlike the above configuration properties, the `mixins` property is under the `config` property, apart from the parent object called **config**.
9999

100100
In this snippet, `Vendor_Module/js/module-mixin` will overwrite the existing component methods in `Vendor_Module/js/module` with the specified component methods. It is a convention to name the mixin by appending a `-mixin` to the original `path/to/js`, although not required.
101101

0 commit comments

Comments
 (0)