Skip to content

Commit f98fe8f

Browse files
noniagriconomieOskarStark
authored andcommitted
Update messenger.rst
1 parent 9f6f101 commit f98fe8f

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

messenger.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -50,8 +50,8 @@ serialized::
5050

5151
.. _messenger-handler:
5252

53-
A message handler is a PHP callable, the easiest way to create it is to create a class that implements
54-
``MessageHandlerInterface`` and has an ``__invoke()`` method that's
53+
A message handler is a PHP callable, the recommended way to create it is to create a class that
54+
implements ``MessageHandlerInterface`` and has an ``__invoke()`` method that's
5555
type-hinted with the message class (or a message interface)::
5656

5757
// src/MessageHandler/SmsNotificationHandler.php
@@ -928,7 +928,7 @@ In Memory Transport
928928

929929
The ``in-memory`` transport was introduced in Symfony 4.3.
930930

931-
The ``in-memory`` transport does not actually delivery messages. Instead, it
931+
The ``in-memory`` transport does not actually deliver messages. Instead, it
932932
holds them in memory during the request, which can be useful for testing.
933933
For example, if you have an ``async_priority_normal`` transport, you could
934934
override it in the ``test`` environment to use this transport:
@@ -1273,7 +1273,7 @@ Middleware
12731273
~~~~~~~~~~
12741274

12751275
What happens when you dispatch a message to a message bus depends on its
1276-
collection of middleware (and their order). By default, the middleware configured
1276+
collection of middleware and their order. By default, the middleware configured
12771277
for each bus looks like this:
12781278

12791279
#. ``add_bus_name_stamp_middleware`` - adds a stamp to record which bus this

0 commit comments

Comments
 (0)