symfony
diff --git a/‎components/event_dispatcher/container_aware_dispatcher.rst
Copy file name to clipboardExpand all lines: components/event_dispatcher/container_aware_dispatcher.rst
+8-7Lines changed: 8 additions & 7 deletions b/‎components/event_dispatcher/container_aware_dispatcher.rst
Copy file name to clipboardExpand all lines: components/event_dispatcher/container_aware_dispatcher.rst
+8-7Lines changed: 8 additions & 7 deletions
diff --git a/‎components/event_dispatcher/generic_event.rst
Copy file name to clipboardExpand all lines: components/event_dispatcher/generic_event.rst
+14-13Lines changed: 14 additions & 13 deletions b/‎components/event_dispatcher/generic_event.rst
Copy file name to clipboardExpand all lines: components/event_dispatcher/generic_event.rst
+14-13Lines changed: 14 additions & 13 deletions
diff --git a/‎components/event_dispatcher/immutable_dispatcher.rst
Copy file name to clipboardExpand all lines: components/event_dispatcher/immutable_dispatcher.rst
+5-5Lines changed: 5 additions & 5 deletions b/‎components/event_dispatcher/immutable_dispatcher.rst
Copy file name to clipboardExpand all lines: components/event_dispatcher/immutable_dispatcher.rst
+5-5Lines changed: 5 additions & 5 deletions
@@ -7,14 +7,15 @@ The Container Aware Event Dispatcher
 Introduction
 ------------
 
-The :class:`Symfony\\Component\\EventDispatcher\\ContainerAwareEventDispatcher` is
-a special ``EventDispatcher`` implementation which is coupled to the service container
-that is part of :doc:`the DependencyInjection component </components/dependency_injection/introduction>`.
+The :class:`Symfony\\Component\\EventDispatcher\\ContainerAwareEventDispatcher`
+is a special ``EventDispatcher`` implementation which is coupled to the
+service container that is part of
+:doc:`the DependencyInjection component </components/dependency_injection/introduction>`.
 It allows services to be specified as event listeners making the ``EventDispatcher``
 extremely powerful.
 
-Services are lazy loaded meaning the services attached as listeners will only be
-created if an event is dispatched that requires those listeners.
+Services are lazy loaded meaning the services attached as listeners will
+only be created if an event is dispatched that requires those listeners.
 
 Setup
 -----
@@ -34,8 +35,8 @@ Adding Listeners
 The ``ContainerAwareEventDispatcher`` can either load specified services
 directly or services that implement :class:`Symfony\\Component\\EventDispatcher\\EventSubscriberInterface`.
 
-The following examples assume the service container has been loaded with any
-services that are mentioned.
+The following examples assume the service container has been loaded with
+any services that are mentioned.
 
 .. note::
 
 
@@ -4,20 +4,21 @@
 The Generic Event Object
 ========================
 
-The base :class:`Symfony\\Component\\EventDispatcher\\Event` class provided by the
-EventDispatcher component is deliberately sparse to allow the creation of
-API specific event objects by inheritance using OOP. This allows for elegant and
-readable code in complex applications.
+The base :class:`Symfony\\Component\\EventDispatcher\\Event` class provided
+by the EventDispatcher component is deliberately sparse to allow the creation
+of API specific event objects by inheritance using OOP. This allows for
+elegant and readable code in complex applications.
 
 The :class:`Symfony\\Component\\EventDispatcher\\GenericEvent` is available
-for convenience for those who wish to use just one event object throughout their
-application. It is suitable for most purposes straight out of the box, because
-it follows the standard observer pattern where the event object
+for convenience for those who wish to use just one event object throughout
+their application. It is suitable for most purposes straight out of the
+box, because it follows the standard observer pattern where the event object
 encapsulates an event 'subject', but has the addition of optional extra
 arguments.
 
-:class:`Symfony\\Component\\EventDispatcher\\GenericEvent` has a simple API in
-addition to the base class :class:`Symfony\\Component\\EventDispatcher\\Event`
+:class:`Symfony\\Component\\EventDispatcher\\GenericEvent` has a simple
+API in addition to the base class
+:class:`Symfony\\Component\\EventDispatcher\\Event`
 
 * :method:`Symfony\\Component\\EventDispatcher\\GenericEvent::__construct`:
   Constructor takes the event subject and any arguments;
@@ -41,8 +42,8 @@ addition to the base class :class:`Symfony\\Component\\EventDispatcher\\Event`
   Returns true if the argument key exists;
 
 The ``GenericEvent`` also implements :phpclass:`ArrayAccess` on the event
-arguments which makes it very convenient to pass extra arguments regarding the
-event subject.
+arguments which makes it very convenient to pass extra arguments regarding
+the event subject.
 
 The following examples show use-cases to give a general idea of the flexibility.
 The examples assume event listeners have been added to the dispatcher.
@@ -64,8 +65,8 @@ Simply passing a subject::
         }
     }
 
-Passing and processing arguments using the :phpclass:`ArrayAccess` API to access
-the event arguments::
+Passing and processing arguments using the :phpclass:`ArrayAccess` API to
+access the event arguments::
 
     use Symfony\Component\EventDispatcher\GenericEvent;
 
 
@@ -7,13 +7,13 @@ The Immutable Event Dispatcher
 .. versionadded:: 2.1
     This feature was introduced in Symfony 2.1.
 
-The :class:`Symfony\\Component\\EventDispatcher\\ImmutableEventDispatcher` is
-a locked or frozen event dispatcher. The dispatcher cannot register new
+The :class:`Symfony\\Component\\EventDispatcher\\ImmutableEventDispatcher`
+is a locked or frozen event dispatcher. The dispatcher cannot register new
 listeners or subscribers.
 
-The ``ImmutableEventDispatcher`` takes another event dispatcher with all the
-listeners and subscribers. The immutable dispatcher is just a proxy of this
-original dispatcher.
+The ``ImmutableEventDispatcher`` takes another event dispatcher with all
+the listeners and subscribers. The immutable dispatcher is just a proxy
+of this original dispatcher.
 
 To use it, first create a normal dispatcher (``EventDispatcher`` or
 ``ContainerAwareEventDispatcher``) and register some listeners or