Skip to content

Commit 65a4bdd

Browse files
committed
notification_channels.md: Fix ordered lists
1 parent f25faeb commit 65a4bdd

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

docs/api/notification_channels.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ The following example shows how you can deliver notifications about Commerce-rel
9696
```
9797

9898
3. Subscribe to notification types related to Commerce, such as order, payment, and shipment status changes.
99-
For example, define the following configuration in a new `config/packages/notifications.yaml` file:
99+
For example, define the following configuration in a new `config/packages/notifications.yaml` file:
100100

101101
``` yaml hl_lines="12-20"
102102
[[= include_code('code_samples/api/notifications/config/packages/notifications.yaml', 1, 20, indent_level=1) =]]
@@ -159,8 +159,8 @@ The following example is a command that sends a notification to users on several
159159
This example could be a scheduled task or cron job that warns users about its result.
160160
161161
1. First, create a `CommandExecuted` notification type.
162-
It supports two channels (`ibexa`, `email`), but could be extended to support more.
163-
As constructor arguments, an instance takes the command itself, the exit code of the run, and any caught exceptions.
162+
It supports two channels (`ibexa`, `email`), but could be extended to support more.
163+
As constructor arguments, an instance takes the command itself, the exit code of the run, and any caught exceptions.
164164
165165
``` php
166166
[[= include_code('code_samples/api/notifications/src/Notifications/CommandExecuted.php', indent_level=1) =]]

0 commit comments

Comments
 (0)