minor #11288 remove blank line after filepath in php code examples (OskarStark)

This PR was merged into the 3.4 branch.

Discussion
----------

remove blank line after filepath in php code examples

<!--

If your pull request fixes a BUG, use the oldest maintained branch that contains
the bug (see https://symfony.com/roadmap for the list of maintained branches).

If your pull request documents a NEW FEATURE, use the same Symfony branch where
the feature was introduced (and `master` for features of unreleased versions).

-->

Commits
-------

48badfd remove blank line after filepath in php code examples

Author: javiereguiluz

bundles/configuration.rst

@@ -223,7 +223,6 @@ force validation (e.g. if an additional option was passed, an exception will be
 thrown)::
 
     // src/Acme/SocialBundle/DependencyInjection/AcmeSocialExtension.php
-
     public function load(array $configs, ContainerBuilder $container)
     {
         $configuration = new Configuration();

components/console/changing_default_command.rst

@@ -31,7 +31,6 @@ name to the ``setDefaultCommand()`` method::
 Executing the application and changing the default command::
 
     // application.php
-
     use Acme\Console\Command\HelloWorldCommand;
     use Symfony\Component\Console\Application;
 

components/yaml.rst

@@ -415,7 +415,6 @@ First, install the Console component:
 Create a console application with ``lint:yaml`` as its only command::
 
     // lint.php
-
     use Symfony\Component\Console\Application;
     use Symfony\Component\Yaml\Command\LintCommand;
 

configuration/micro_kernel_trait.rst

@@ -133,7 +133,6 @@ putting *everything* in ``index.php``, create a new ``app/AppKernel.php`` to
 hold the kernel. Now it looks like this::
 
     // app/AppKernel.php
-
     use Symfony\Bundle\FrameworkBundle\Kernel\MicroKernelTrait;
     use Symfony\Component\Config\Loader\LoaderInterface;
     use Symfony\Component\DependencyInjection\ContainerBuilder;
@@ -298,7 +297,6 @@ Finally, you need a front controller to boot and run the application. Create a
 ``web/index.php``::
 
     // web/index.php
-
     use Symfony\Component\HttpFoundation\Request;
 
     require __DIR__.'/../app/AppKernel.php';

doctrine/pdo_session_storage.rst

@@ -146,7 +146,6 @@ a second array argument to ``PdoSessionHandler``:
     .. code-block:: php
 
         // app/config/config.php
-
         use Symfony\Component\HttpFoundation\Session\Storage\Handler\PdoSessionHandler;
         // ...
 

doctrine/resolve_target_entity.rst

@@ -40,7 +40,6 @@ brevity) to explain how to set up and use the ``ResolveTargetEntityListener``.
 A Customer entity::
 
     // src/AppBundle/Entity/Customer.php
-
     namespace AppBundle\Entity;
 
     use Doctrine\ORM\Mapping as ORM;
@@ -60,7 +59,6 @@ A Customer entity::
 An Invoice entity::
 
     // src/Acme/InvoiceBundle/Entity/Invoice.php
-
     namespace Acme\InvoiceBundle\Entity;
 
     use Doctrine\ORM\Mapping as ORM;
@@ -84,7 +82,6 @@ An Invoice entity::
 An InvoiceSubjectInterface::
 
     // src/Acme/InvoiceBundle/Model/InvoiceSubjectInterface.php
-
     namespace Acme\InvoiceBundle\Model;
 
     /**

form/dynamic_form_modification.rst

@@ -251,7 +251,6 @@ Now that you have all the basics in place you can use the features of the
 security helper to fill in the listener logic::
 
     // src/AppBundle/Form/Type/FriendMessageFormType.php
-
     use AppBundle\Entity\User;
     use Doctrine\ORM\EntityRepository;
     use Symfony\Bridge\Doctrine\Form\Type\EntityType;

form/form_collections.rst

@@ -649,7 +649,6 @@ the relationship between the removed ``Tag`` and ``Task`` object.
     is handling the "update" of your Task::
 
         // src/AppBundle/Controller/TaskController.php
-
         use AppBundle\Entity\Task;
         use Doctrine\Common\Collections\ArrayCollection;
 

form/form_dependencies.rst

@@ -77,7 +77,6 @@ Suppose you need to access the :ref:`EntityManager <doctrine-entity-manager>` ob
 so that you can make a query. First, add this as an argument to your form class::
 
     // src/AppBundle/Form/TaskType.php
-
     use Doctrine\ORM\EntityManagerInterface;
     // ...
 

http_cache/cache_invalidation.rst

@@ -51,7 +51,6 @@ Here is how you can configure the Symfony reverse proxy to support the
 ``PURGE`` HTTP method::
 
     // app/AppCache.php
-
     use Symfony\Bundle\FrameworkBundle\HttpCache\HttpCache;
     use Symfony\Component\HttpFoundation\Request;
     use Symfony\Component\HttpFoundation\Response;

security/entity_provider.rst

@@ -345,7 +345,6 @@ This extends :class:`Symfony\\Component\\Security\\Core\\User\\UserInterface`,
 so you only need the new interface::
 
     // src/AppBundle/Entity/User.php
-
     use Symfony\Component\Security\Core\User\AdvancedUserInterface;
     // ...
 

service_container/factories.rst

@@ -72,7 +72,6 @@ configure the service container to use the
     .. code-block:: php
 
         // app/config/services.php
-
         use AppBundle\Email\NewsletterManager;
         use AppBundle\Email\NewsletterManagerStaticFactory;
         // ...
@@ -136,7 +135,6 @@ Configuration of the service container then looks like this:
     .. code-block:: php
 
         // app/config/services.php
-
         use AppBundle\Email\NewsletterManager;
         use AppBundle\Email\NewsletterManagerFactory;
         use Symfony\Component\DependencyInjection\Reference;
@@ -216,7 +214,6 @@ example takes the ``templating`` service as an argument:
     .. code-block:: php
 
         // app/config/services.php
-
         use AppBundle\Email\NewsletterManager;
         use AppBundle\Email\NewsletterManagerFactory;
         use Symfony\Component\DependencyInjection\Reference;

templating/PHP.rst

@@ -279,7 +279,6 @@ Here, the ``AppBundle:Hello:fancy`` string refers to the ``fancy`` action of the
 ``Hello`` controller::
 
     // src/AppBundle/Controller/HelloController.php
-
     class HelloController extends Controller
     {
         public function fancyAction($name, $color)

workflow/state-machines.rst

@@ -142,7 +142,6 @@ Below is the configuration for the pull request state machine.
     .. code-block:: php
 
         // app/config/config.php
-
         $container->loadFromExtension('framework', [
             // ...
             'workflows' => [

workflow/usage.rst

@@ -104,7 +104,6 @@ like this:
     .. code-block:: php
 
         // app/config/config.php
-
         $container->loadFromExtension('framework', [
             // ...
             'workflows' => [