@@ -50,8 +50,8 @@ serialized::
50
50
51
51
.. _messenger-handler :
52
52
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
55
55
type-hinted with the message class (or a message interface)::
56
56
57
57
// src/MessageHandler/SmsNotificationHandler.php
@@ -928,7 +928,7 @@ In Memory Transport
928
928
929
929
The ``in-memory `` transport was introduced in Symfony 4.3.
930
930
931
- The ``in-memory `` transport does not actually delivery messages. Instead, it
931
+ The ``in-memory `` transport does not actually deliver messages. Instead, it
932
932
holds them in memory during the request, which can be useful for testing.
933
933
For example, if you have an ``async_priority_normal `` transport, you could
934
934
override it in the ``test `` environment to use this transport:
@@ -1273,7 +1273,7 @@ Middleware
1273
1273
~~~~~~~~~~
1274
1274
1275
1275
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
1277
1277
for each bus looks like this:
1278
1278
1279
1279
#. ``add_bus_name_stamp_middleware `` - adds a stamp to record which bus this
0 commit comments