Skip to content

Commit daebffb

Browse files
committed
MAGEDOC-3440: Edit events topic
Minor language cleaning
1 parent 97a2b72 commit daebffb

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

docs/reference/events.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Page Builder events
22

3-
The pattern for consuming Page Builder events in JavaScript, such as within your content type's `preview.js` component, is to import `Magento_PageBuilder/js/events` and use the `events.on()` method to bind to the event you want to handle, as shown here:
3+
The pattern for consuming Page Builder events in JavaScript, such as within the `preview.js` component, is to import `Magento_PageBuilder/js/events` and use the `events.on()` method to bind to the event you want to handle, as shown here:
44

55
```js
66
define([
@@ -17,7 +17,7 @@ define([
1717

1818
## Events
1919

20-
The events you can consume are listed here with links to the details.
20+
The following table lists the Page Builder events you can consume.
2121

2222
<!-- {% raw %} -->
2323

@@ -45,9 +45,10 @@ The events you can consume are listed here with links to the details.
4545
| [image:uploadAfter](#imageuploadafter) | [{{config.name}}:{{preview.parent.id}}:updateAfter](#confignameidupdateafter) |
4646
| | |
4747

48+
## Usage
4849

4950
## `contentType:*` events
50-
Events starting with `contentType:` are triggered for every content type on the stage. These events can also be called for specific content types by prefixing the content type's name before the event (``name:event`). For example:
51+
Events starting with `contentType:` are triggered for every content type on the stage. These events can also be called for specific content types by prefixing the content type's name before the event (`name:event`). For example:
5152
* `text:createAfter`
5253
* `row:mountAfter`
5354
* `tab-item:mountAfter`

0 commit comments

Comments
 (0)