From be2f7ef7cc9299ae3bfca8eb876c4fd43ee4287a Mon Sep 17 00:00:00 2001 From: Javier Eguiluz Date: Wed, 8 Nov 2017 13:27:23 +0100 Subject: [PATCH] Reworded the introduction of event listeners article --- event_dispatcher.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/event_dispatcher.rst b/event_dispatcher.rst index 8bc88be3cbb..1498605ee4d 100644 --- a/event_dispatcher.rst +++ b/event_dispatcher.rst @@ -9,10 +9,10 @@ During the execution of a Symfony application, lots of event notifications are triggered. Your application can listen to these notifications and respond to them by executing any piece of code. -Internal events provided by Symfony itself are defined in the -:class:`Symfony\\Component\\HttpKernel\\KernelEvents` class. Third-party bundles -and libraries also trigger lots of events and your own application can trigger -:doc:`custom events `. +Symfony triggers several :doc:`events related to the kernel ` +while processing an HTTP Request, third-party bundles and libraries also trigger +lots of events and your own application can trigger :doc:`custom events +`. All the examples shown in this article use the same ``KernelEvents::EXCEPTION`` event for consistency purposes. In your own application, you can use any event