updated the section on customizing the error pages

fabpot · fabpot · commit 099218d2e778 · 2011-07-21T20:41:59.000+02:00
diff --git a/cookbook/controller/error_pages.rst b/cookbook/controller/error_pages.rst
@@ -3,9 +3,9 @@ How to customize Error Pages
 
 When any exception is thrown in Symfony2, the exception is caught inside the
 ``Kernel`` class and eventually forwarded to a special controller,
-``FrameworkBundle:Exception:show`` for handling. This controller, which lives
-inside the core ``FrameworkBundle``, determines which error template to
-display and the status code that should be set for the given exception.
+``TwigBundle:Exception:show`` for handling. This controller, which lives
+inside the core ``TwigBundle``, determines which error template to display and
+the status code that should be set for the given exception.
 
 .. tip::
 
@@ -14,14 +14,14 @@ display and the status code that should be set for the given exception.
     which allows complete control over exception handling. For more
     information, see :ref:`kernel-kernel.exception`.
 
-All of the error templates live inside ``FrameworkBundle``. To override the
+All of the error templates live inside ``TwigBundle``. To override the
 templates, we simply rely on the standard method for overriding templates that
 live inside a bundle. For more information, see
 :ref:`overriding-bundle-templates`.
 
 For example, to override the default error template that's shown to the
 end-user, create a new template located at
-``app/Resources/FrameworkBundle/views/Exception/error.html.twig``:
+``app/Resources/TwigBundle/views/Exception/error.html.twig``:
 
 .. code-block:: html+jinja
 
@@ -47,8 +47,8 @@ page for many of the most common response formats, including JSON
 (``error.json.twig``), XML, (``error.xml.twig``), and even Javascript
 (``error.js.twig``), to name a few. To override any of these templates, just
 create a new file with the same name in the
-``app/Resources/FrameworkBundle/views/Exception`` directory. This is the
-standard way of overriding any template that lives inside a bundle.
+``app/Resources/TwigBundle/views/Exception`` directory. This is the standard
+way of overriding any template that lives inside a bundle.
 
 .. _cookbook-error-pages-by-status-code:
 
@@ -57,8 +57,8 @@ Customizing the 404 Page and other Error Pages
 
 You can also customize specific error templates according to the HTTP status
 code. For instance, create a
-``app/Resources/FrameworkBundle/views/Exception/error404.html.twig`` template
-to display a special page for 404 (page not found) errors.
+``app/Resources/TwigBundle/views/Exception/error404.html.twig`` template to
+display a special page for 404 (page not found) errors.
 
 Symfony uses the following algorithm to determine which template to use:
 
@@ -74,11 +74,11 @@ Symfony uses the following algorithm to determine which template to use:
 .. tip::
 
     To see the full list of default error templates, see the
-    ``Resources/views/Exception`` directory of the ``FrameworkBundle``. In a
-    standard Symfony2 installation, the ``FrameworkBundle`` can be found at
-    ``vendor/symfony/src/Symfony/Bundle/FrameworkBundle``. Often, the easiest
-    way to customize an error page is to copy it from the ``FrameworkBundle``
-    into ``app/Resources/FrameworkBundle/views/Exception`` and then modify it.
+    ``Resources/views/Exception`` directory of the ``TwigBundle``. In a
+    standard Symfony2 installation, the ``TwigBundle`` can be found at
+    ``vendor/symfony/src/Symfony/Bundle/TwigBundle``. Often, the easiest way
+    to customize an error page is to copy it from the ``TwigBundle`` into
+    ``app/Resources/TwigBundle/views/Exception`` and then modify it.
 
 .. note::
 
