@@ -29,12 +29,13 @@ leveraging a Messenger bus for synchronous needs.
2929The :method: `Symfony\\ Component\\ Messenger\\ HandleTrait::handle ` method ensures
3030there is exactly one handler registered and returns its result.
3131
32- Working with command & query buses
32+ Working with Command & Query Buses
3333----------------------------------
3434
3535The Messenger component can be used in CQRS architectures where command & query
36- buses are central pieces of the application.
37- See Martin Fowler's `article about CQRS `_ to learn more and :doc: `how to configure multiple buses </messenger/multiple_buses >`.
36+ buses are central pieces of the application. Read Martin Fowler's
37+ `article about CQRS `_ to learn more and
38+ :doc: `how to configure multiple buses </messenger/multiple_buses >`.
3839
3940As queries are usually synchronous and expected to be handled once,
4041getting the result from the handler is a common need.
@@ -47,7 +48,6 @@ a ``$messageBus`` property:
4748 .. code-block :: php
4849
4950 // src/Action/ListItems.php
50-
5151 namespace App\Action;
5252
5353 use App\Message\ListItemsQuery;
@@ -88,7 +88,6 @@ wherever you need a query bus behavior instead of the ``MessageBusInterface``:
8888 .. code-block :: php
8989
9090 // src/MessageBus/QueryBus.php
91-
9291 namespace App\MessageBus;
9392
9493 use Symfony\Component\Messenger\Envelope;
@@ -115,4 +114,4 @@ wherever you need a query bus behavior instead of the ``MessageBusInterface``:
115114 }
116115 }
117116
118- .. _ article about CQRS : https://martinfowler.com/bliki/CQRS.html
117+ .. _ `article about CQRS` : https://martinfowler.com/bliki/CQRS.html
0 commit comments