From 3c5bd9641391648b9992725cbad7b699fec87f69 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C5=BDilvinas=20Kuusas?= Date: Tue, 21 Jun 2016 17:56:32 +0300 Subject: [PATCH] Fix typo 'even' >> 'event' in event_listener.rst --- cookbook/event_dispatcher/event_listener.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cookbook/event_dispatcher/event_listener.rst b/cookbook/event_dispatcher/event_listener.rst index e864c3c22b6..46b81ccef3f 100644 --- a/cookbook/event_dispatcher/event_listener.rst +++ b/cookbook/event_dispatcher/event_listener.rst @@ -65,7 +65,7 @@ The most common way to listen to an event is to register an **event listener**:: Each event receives a slightly different type of ``$event`` object. For the ``kernel.exception`` event, it is :class:`Symfony\\Component\\HttpKernel\\Event\\GetResponseForExceptionEvent`. To see what type of object each event listener receives, see :class:`Symfony\\Component\\HttpKernel\\KernelEvents` - or the documentation about the specific even you're listening to. + or the documentation about the specific event you're listening to. Now that the class is created, you just need to register it as a service and notify Symfony that it is a "listener" on the ``kernel.exception`` event by