Merge branch '4.4' into 5.0

* 4.4:
  Updated a link to Debug component
  Remove ErrorRenderer reference everywhere

Author: javiereguiluz

components/error_handler.rst

@@ -67,11 +67,6 @@ to enable this error handler::
 
     ErrorHandler::register();
 
-.. tip::
-
-    If you want to get even better exception pages, install the
-    :doc:`ErrorRenderer component </components/error_renderer>` too.
-
 Catching PHP Function Errors and Turning Them into Exceptions
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -145,11 +140,6 @@ to enable this exception handler::
 
     ExceptionHandler::register();
 
-.. tip::
-
-    If you want to get even better exception pages, install the
-    :doc:`ErrorRenderer component </components/error_renderer>` too.
-
 .. _component-debug-class-loader:
 
 Class Loading Debugger

components/error_renderer.rst

@@ -554,7 +554,7 @@ below for more details).
     The listener has several goals:
 
     1) The thrown exception is converted into a
-       :class:`Symfony\\Component\\ErrorRenderer\\Exception\\FlattenException`
+       :class:`Symfony\\Component\\ErrorHandler\\Exception\\FlattenException`
        object, which contains all the information about the request, but which
        can be printed and serialized.
 

components/http_kernel.rst

@@ -311,8 +311,9 @@ Deprecation Notices at Autoloading Time
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 By default, the PHPUnit Bridge uses ``DebugClassLoader`` from the
-`Debug component`_ to throw deprecation notices at class autoloading time.
-This can be disabled with the ``debug-class-loader`` option.
+:doc:`ErrorHandler component </components/error_handler>`_ to throw deprecation
+notices at class autoloading time. This can be disabled with the
+``debug-class-loader`` option.
 
 .. code-block:: xml
 
@@ -962,4 +963,3 @@ not find the SUT:
 .. _`test listener`: https://phpunit.de/manual/current/en/appendixes.configuration.html#appendixes.configuration.test-listeners
 .. _`@covers`: https://phpunit.de/manual/current/en/appendixes.annotations.html#appendixes.annotations.covers
 .. _`PHP namespace resolutions rules`: https://php.net/manual/en/language.namespaces.rules.php
-.. _Debug component: https://github.com/symfony/debug

components/phpunit_bridge.rst

@@ -247,7 +247,7 @@ the request that will be dispatched to your controller. In addition, your contro
 will be passed two parameters:
 
 ``exception``
-    A :class:`\\Symfony\\Component\\ErrorRenderer\\Exception\\FlattenException`
+    A :class:`\\Symfony\\Component\\ErrorHandler\\Exception\\FlattenException`
     instance created from the exception being handled.
 
 ``logger``

controller/error_pages.rst

@@ -69,7 +69,7 @@ Our code is now much more concise and surprisingly more robust and more
 powerful than ever. For instance, use the built-in ``ExceptionListener`` to
 make your error management configurable::
 
-    $errorHandler = function (Symfony\Component\ErrorRenderer\Exception\FlattenException $exception) {
+    $errorHandler = function (Symfony\Component\ErrorHandler\Exception\FlattenException $exception) {
         $msg = 'Something went wrong! ('.$exception->getMessage().')';
 
         return new Response($msg, $exception->getStatusCode());
@@ -91,7 +91,7 @@ The error controller reads as follows::
     // example.com/src/Calendar/Controller/ErrorController.php
     namespace Calendar\Controller;
 
-    use Symfony\Component\ErrorRenderer\Exception\FlattenException;
+    use Symfony\Component\ErrorHandler\Exception\FlattenException;
     use Symfony\Component\HttpFoundation\Response;
 
     class ErrorController