@@ -134,7 +134,7 @@ Connecting Listeners
134
134
135
135
To take advantage of an existing event, you need to connect a listener to the
136
136
dispatcher so that it can be notified when the event is dispatched. A call to
137
- the dispatcher ``addListener() `` method associates any valid PHP callable to
137
+ the dispatcher's ``addListener() `` method associates any valid PHP callable to
138
138
an event::
139
139
140
140
$listener = new AcmeListener();
@@ -158,7 +158,7 @@ The ``addListener()`` method takes up to three arguments:
158
158
A `PHP callable `_ is a PHP variable that can be used by the
159
159
``call_user_func() `` function and returns ``true `` when passed to the
160
160
``is_callable() `` function. It can be a ``\Closure `` instance, an object
161
- implementing an __invoke method (which is what closures are in fact),
161
+ implementing an `` __invoke `` method (which is what closures are in fact),
162
162
a string representing a function, or an array representing an object
163
163
method or a class method.
164
164
@@ -583,7 +583,7 @@ Dispatcher Shortcuts
583
583
584
584
The :method: `EventDispatcher::dispatch <Symfony\\ Component\\ EventDispatcher\\ EventDispatcher::dispatch> `
585
585
method always returns an :class: `Symfony\\ Component\\ EventDispatcher\\ Event `
586
- object. This allows for various shortcuts. For example if one does not need
586
+ object. This allows for various shortcuts. For example, if one does not need
587
587
a custom event object, one can simply rely on a plain
588
588
:class: `Symfony\\ Component\\ EventDispatcher\\ Event ` object. You do not even need
589
589
to pass this to the dispatcher as it will create one by default unless you
0 commit comments