@@ -55,7 +55,7 @@ On top of HttpFoundation is the :namespace:`Symfony\\Component\\HttpKernel`
55
55
component. HttpKernel handles the dynamic part of HTTP; it is a thin wrapper
56
56
on top of the Request and Response classes to standardize the way requests are
57
57
handled. It also provides extension points and tools that makes it the ideal
58
- starting point to create a Web framework without too much overhead.
58
+ starting point to create a web framework without too much overhead.
59
59
60
60
It also optionally adds configurability and extensibility, thanks to the
61
61
DependencyInjection component and a powerful plugin system (bundles).
@@ -177,12 +177,12 @@ Event):
177
177
#. Listeners of the ``kernel.terminate `` event can perform tasks after the
178
178
Response has been served.
179
179
180
- If an Exception is thrown during processing, the ``kernel.exception `` is
181
- notified and listeners are given a chance to convert the Exception to a
180
+ If an exception is thrown during processing, the ``kernel.exception `` is
181
+ notified and listeners are given a chance to convert the exception into a
182
182
Response. If that works, the ``kernel.response `` event is notified; if not, the
183
183
Exception is re-thrown.
184
184
185
- If you don't want Exceptions to be caught (for embedded requests for
185
+ If you don't want exceptions to be caught (for embedded requests for
186
186
instance), disable the ``kernel.exception `` event by passing ``false `` as the
187
187
third argument to the ``handle() `` method.
188
188
@@ -241,8 +241,8 @@ add the following code at the beginning of your listener method::
241
241
242
242
.. tip ::
243
243
244
- If you are not yet familiar with the Symfony EventDispatcher, read the
245
- :doc: `EventDispatcher component documentation </components/event_dispatcher/introduction >`
244
+ If you are not yet familiar with the Symfony EventDispatcher component,
245
+ read :doc: `its documentation </components/event_dispatcher/introduction >`
246
246
section first.
247
247
248
248
.. index ::
@@ -354,7 +354,7 @@ The FrameworkBundle registers several listeners:
354
354
Collects data for the current request.
355
355
356
356
:class: `Symfony\\ Bundle\\ WebProfilerBundle\\ EventListener\\ WebDebugToolbarListener `
357
- Injects the Web Debug Toolbar .
357
+ Injects the web debug toolbar .
358
358
359
359
:class: `Symfony\\ Component\\ HttpKernel\\ EventListener\\ ResponseListener `
360
360
Fixes the Response ``Content-Type `` based on the request format.
@@ -412,7 +412,7 @@ forwards the ``Request`` to a given Controller (the value of the
412
412
``class::method `` notation).
413
413
414
414
A listener on this event can create and set a ``Response `` object, create
415
- and set a new ``Exception `` object, or do nothing::
415
+ and set a new ``Exception `` object or do nothing::
416
416
417
417
use Symfony\Component\HttpKernel\Event\GetResponseForExceptionEvent;
418
418
use Symfony\Component\HttpFoundation\Response;
@@ -452,8 +452,10 @@ and set a new ``Exception`` object, or do nothing::
452
452
.. index ::
453
453
single: EventDispatcher
454
454
455
- The EventDispatcher
456
- -------------------
455
+ .. _the-eventdispatcher :
456
+
457
+ The EventDispatcher Component
458
+ -----------------------------
457
459
458
460
The EventDispatcher is a standalone component that is responsible for much
459
461
of the underlying logic and flow behind a Symfony request. For more information,
@@ -474,7 +476,7 @@ enhance performance; use it in the production environment to explore problems
474
476
after the fact.
475
477
476
478
You rarely have to deal with the profiler directly as Symfony provides
477
- visualizer tools like the Web Debug Toolbar and the Web Profiler . If you use
479
+ visualizer tools like the web debug toolbar and the web profiler . If you use
478
480
the Symfony Standard Edition, the profiler, the web debug toolbar, and the
479
481
web profiler are all already configured with sensible settings.
480
482
@@ -500,7 +502,7 @@ bottom of all pages. It displays a good summary of the profiling data that
500
502
gives you instant access to a lot of useful information when something does
501
503
not work as expected.
502
504
503
- If the summary provided by the Web Debug Toolbar is not enough, click on the
505
+ If the summary provided by the web debug toolbar is not enough, click on the
504
506
token link (a string made of 13 random characters) to access the Web Profiler.
505
507
506
508
.. note ::
0 commit comments