minor #8953 Clean up (carusogabriel)

This PR was squashed before being merged into the 4.0 branch (closes #8953).

Discussion
----------

Clean up

Following #8948, suggested by @xabbuh

Commits
-------

ce10e67 Clean up

Author: xabbuh

components/http_kernel.rst

@@ -234,7 +234,6 @@ This implementation is explained more in the sidebar below::
         public function getController(Request $request);
     }
 
-
 Internally, the ``HttpKernel::handle()`` method first calls
 :method:`Symfony\\Component\\HttpKernel\\Controller\\ControllerResolverInterface::getController`
 on the controller resolver. This method is passed the ``Request`` and is responsible

components/var_dumper.rst

@@ -80,7 +80,7 @@ DebugBundle and Twig Integration
 --------------------------------
 
 The DebugBundle allows greater integration of this component into Symfony
-applications. 
+applications.
 
 Since generating (even debug) output in the controller or in the model
 of your application may just break it by e.g. sending HTTP headers or

create_framework/http_kernel_controller_resolver.rst

@@ -56,7 +56,6 @@ based on a Request object. All controller resolvers implement the following inte
         public function getController(Request $request);
     }
 
-
 The ``getController()`` method relies on the same convention as the one we
 have defined earlier: the ``_controller`` request attribute must contain the
 controller associated with the Request. Besides the built-in PHP callbacks,
@@ -100,7 +99,6 @@ following interface::
         public function getArguments(Request $request, $controller);
     }
 
-
 The ``indexAction()`` method needs the Request object as an argument.
 ``getArguments()`` knows when to inject it properly if it is type-hinted
 correctly::

logging/monolog_console.rst

@@ -39,7 +39,7 @@ The example above could then be rewritten as::
     use Symfony\Component\Console\Input\InputInterface;
     use Symfony\Component\Console\Output\OutputInterface;
     // ...
-    
+
     class YourCommand extends Command
     {
         private $logger;

quick_tour/flex_recipes.rst

@@ -79,7 +79,7 @@ Thanks to Flex, after one command, you can start using Twig immediately:
     // ...
 
     + use Symfony\Bundle\FrameworkBundle\Controller\AbstractController;
- 
+
     -class DefaultController
     +class DefaultController extends AbstractController
      {
@@ -216,16 +216,16 @@ me? List your routes by running:
 
 .. code-block:: text
 
-    ------------------------------ -------- ------------------------------------- 
-     Name                           Method   Path                                 
-    ------------------------------ -------- ------------------------------------- 
-     api_products_get_collection    GET      /api/products.{_format}              
-     api_products_post_collection   POST     /api/products.{_format}              
-     api_products_get_item          GET      /api/products/{id}.{_format}         
-     api_products_put_item          PUT      /api/products/{id}.{_format}         
-     api_products_delete_item       DELETE   /api/products/{id}.{_format}         
+    ------------------------------ -------- -------------------------------------
+     Name                           Method   Path
+    ------------------------------ -------- -------------------------------------
+     api_products_get_collection    GET      /api/products.{_format}
+     api_products_post_collection   POST     /api/products.{_format}
+     api_products_get_item          GET      /api/products/{id}.{_format}
+     api_products_put_item          PUT      /api/products/{id}.{_format}
+     api_products_delete_item       DELETE   /api/products/{id}.{_format}
      ...
-    ------------------------------ -------- ------------------------------------- 
+    ------------------------------ -------- -------------------------------------
 
 Easily Remove Recipes
 ---------------------

quick_tour/the_architecture.rst

@@ -113,7 +113,7 @@ difference is that it's done in the constructor:
     class GreetingGenerator
     {
     +     private $logger;
-    + 
+    +
     +     public function __construct(LoggerInterface $logger)
     +     {
     +         $this->logger = $logger;

quick_tour/the_big_picture.rst

@@ -149,21 +149,21 @@ Instead, add the route *right above* the controller method:
 
     // src/Controller/DefaultController.php
     // ...
-    
+
     + use Symfony\Component\Routing\Annotation\Route;
-    
+
     + /**
     +  * @Route("/hello/{name}")
     +  */
     public function index($name)
-    
+
 This works just like before! But by using annotations, the route and controller
 live right next to each other. Need another page? Just add another route and method
 in ``DefaultController``::
 
     // src/Controller/DefaultController.php
     // ...
-    
+
     /**
      * @Route("/simplicity")
      */

routing.rst

@@ -343,7 +343,7 @@ As your app grows, you'll eventually have a *lot* of routes! To see them all, ru
 .. code-block:: text
 
     ------------------------------ -------- -------------------------------------
-     Name                           Method   Path                                 
+     Name                           Method   Path
     ------------------------------ -------- -------------------------------------
      app_lucky_number              ANY    /lucky/number/{max}
      ...

security/entity_provider.rst

@@ -41,7 +41,7 @@ Before you begin, first make sure you install the Security component:
 .. code-block:: terminal
 
     $ composer require security
-    
+
 For this entry, suppose that you already have a ``User`` entity
 with the following fields: ``id``, ``username``, ``password``,
 ``email`` and ``isActive``::

setup/unstable_versions.rst

@@ -16,7 +16,7 @@ execute the following command:
 
     # Download the latest beta version
     $ composer create-project symfony/skeleton my_project "4.0.*" -s beta
-    
+
     # Download the absolute latest commit
     $ composer create-project symfony/skeleton my_project "4.0.*" -s dev