minor #11504 fix indention (OskarStark)

This PR was merged into the 3.4 branch.

Discussion
----------

fix indention

<!--

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
-------

5218163 fix indention

Author: javiereguiluz

best_practices/forms.rst

@@ -143,7 +143,7 @@ view layer:
         {{ form_widget(form) }}
 
         <input type="submit" value="Create"
-               class="btn btn-default pull-right"/>
+            class="btn btn-default pull-right"/>
     {{ form_end(form) }}
 
 Validation

bundles/configuration.rst

@@ -81,11 +81,11 @@ allow users to configure it with some configuration that looks like this:
             xsi:schemaLocation="http://symfony.com/schema/dic/services
                 https://symfony.com/schema/dic/services/services-1.0.xsd">
 
-           <acme-social:config>
-               <acme-social:twitter client-id="123" client-secret="your_secret"/>
-           </acme-social:config>
+            <acme-social:config>
+                <acme-social:twitter client-id="123" client-secret="your_secret"/>
+            </acme-social:config>
 
-           <!-- ... -->
+            <!-- ... -->
         </container>
 
     .. code-block:: php

components/cache/adapters/pdo_doctrine_dbal_adapter.rst

@@ -9,7 +9,7 @@ PDO & Doctrine DBAL Cache Adapter
 
 .. versionadded:: 3.2
 
-   The PDO & Doctrine DBAL adapter was introduced in Symfony 3.2.
+    The PDO & Doctrine DBAL adapter was introduced in Symfony 3.2.
 
 This adapter stores the cache items in an SQL database. It requires a `PDO`_,
 `Doctrine DBAL Connection`_, or `Data Source Name (DSN)`_ as its first parameter, and

components/cache/adapters/proxy_adapter.rst

@@ -15,8 +15,9 @@ and optionally a namespace and default cache lifetime as its second and third pa
     use Psr\Cache\CacheItemPoolInterface;
     use Symfony\Component\Cache\Adapter\ProxyAdapter;
 
-    $psr6CachePool = \\ create your own cache pool instance that implements the PSR-6
-                     \\ interface `CacheItemPoolInterface`
+    \\ create your own cache pool instance that implements the PSR-6
+    \\ interface `CacheItemPoolInterface`
+    $psr6CachePool = ...
 
     $cache = new ProxyAdapter(
 

components/console/console_arguments.rst

@@ -39,7 +39,7 @@ Have a look at the following command that has three options::
 
         protected function execute(InputInterface $input, OutputInterface $output)
         {
-           // ...
+            // ...
         }
     }
 

components/console/single_command_tool.rst

@@ -8,44 +8,44 @@ When building a command line tool, you may not need to provide several commands.
 In such case, having to pass the command name each time is tedious. Fortunately,
 it is possible to remove this need by declaring a single command application::
 
-  #!/usr/bin/env php
-  <?php
-  require __DIR__.'/vendor/autoload.php';
-
-  use Symfony\Component\Console\Application;
-  use Symfony\Component\Console\Input\InputArgument;
-  use Symfony\Component\Console\Input\InputInterface;
-  use Symfony\Component\Console\Input\InputOption;
-  use Symfony\Component\Console\Output\OutputInterface;
-
-  (new Application('echo', '1.0.0'))
-    ->register('echo')
-        ->addArgument('foo', InputArgument::OPTIONAL, 'The directory')
-        ->addOption('bar', null, InputOption::VALUE_REQUIRED)
-        ->setCode(function(InputInterface $input, OutputInterface $output) {
-            // output arguments and options
-        })
-    ->getApplication()
-    ->setDefaultCommand('echo', true) // Single command application
-    ->run();
+    #!/usr/bin/env php
+    <?php
+    require __DIR__.'/vendor/autoload.php';
+
+    use Symfony\Component\Console\Application;
+    use Symfony\Component\Console\Input\InputArgument;
+    use Symfony\Component\Console\Input\InputInterface;
+    use Symfony\Component\Console\Input\InputOption;
+    use Symfony\Component\Console\Output\OutputInterface;
+
+    (new Application('echo', '1.0.0'))
+      ->register('echo')
+          ->addArgument('foo', InputArgument::OPTIONAL, 'The directory')
+          ->addOption('bar', null, InputOption::VALUE_REQUIRED)
+          ->setCode(function(InputInterface $input, OutputInterface $output) {
+              // output arguments and options
+          })
+      ->getApplication()
+      ->setDefaultCommand('echo', true) // Single command application
+      ->run();
 
 The method :method:`Symfony\\Component\\Console\\Application::setDefaultCommand`
 accepts a boolean as second parameter. If true, the command ``echo`` will then
 always be used, without having to pass its name.
 
 Of course, you can still register a command as usual::
 
-  #!/usr/bin/env php
-  <?php
-  require __DIR__.'/vendor/autoload.php';
+    #!/usr/bin/env php
+    <?php
+    require __DIR__.'/vendor/autoload.php';
 
-  use Acme\Command\DefaultCommand;
-  use Symfony\Component\Console\Application;
+    use Acme\Command\DefaultCommand;
+    use Symfony\Component\Console\Application;
 
-  $application = new Application('echo', '1.0.0');
-  $command = new DefaultCommand();
+    $application = new Application('echo', '1.0.0');
+    $command = new DefaultCommand();
 
-  $application->add($command);
+    $application->add($command);
 
-  $application->setDefaultCommand($command->getName(), true);
-  $application->run();
+    $application->setDefaultCommand($command->getName(), true);
+    $application->run();

components/dependency_injection/compilation.rst

@@ -325,7 +325,7 @@ compilation::
     {
         public function process(ContainerBuilder $container)
         {
-           // ... do something during the compilation
+            // ... do something during the compilation
         }
 
         // ...
@@ -379,7 +379,7 @@ class implementing the ``CompilerPassInterface``::
     {
         public function process(ContainerBuilder $container)
         {
-           // ... do something during the compilation
+            // ... do something during the compilation
         }
     }
 

components/dom_crawler.rst

@@ -234,7 +234,7 @@ context of the crawler::
         // DO THIS: specify the parent tag too
         $subCrawler = $parentCrawler->filterXPath('parent/sub-tag/sub-child-tag');
         $subCrawler = $parentCrawler->filterXPath('node()/sub-tag/sub-child-tag');
-  });
+    });
 
 Adding the Content
 ~~~~~~~~~~~~~~~~~~
@@ -338,30 +338,30 @@ This behavior is best illustrated with examples::
 
     $crawler->filterXPath('//span[contains(@id, "article-")]')->evaluate('substring-after(@id, "-")');
     /* array:3 [
-         0 => "100"
-         1 => "101"
-         2 => "102"
-       ]
+        0 => "100",
+        1 => "101",
+        2 => "102",
+    ]
      */
 
     $crawler->evaluate('substring-after(//span[contains(@id, "article-")]/@id, "-")');
     /* array:1 [
-         0 => "100"
-       ]
+        0 => "100",
+    ]
      */
 
     $crawler->filterXPath('//span[@class="article"]')->evaluate('count(@id)');
     /* array:3 [
-         0 => 1.0
-         1 => 1.0
-         2 => 1.0
-       ]
+        0 => 1.0,
+        1 => 1.0,
+        2 => 1.0,
+    ]
      */
 
     $crawler->evaluate('count(//span[@class="article"])');
     /* array:1 [
-         0 => 3.0
-       ]
+        0 => 3.0,
+    ]
      */
 
     $crawler->evaluate('//span[1]');

components/filesystem/lock_handler.rst

@@ -82,7 +82,7 @@ PHP code will wait indefinitely until the lock is released by another process.
 
         use Symfony\Component\Filesystem\LockHandler;
 
-         if (!(new LockHandler('hello.lock'))->lock()) {
+        if (!(new LockHandler('hello.lock'))->lock()) {
             // the resource "hello" is already locked by another process
 
             return 0;

components/serializer.rst

@@ -856,11 +856,11 @@ because it is deeper than the configured maximum depth of 2::
     $result = [
         'foo' => 'level1',
         'child' => [
-                'foo' => 'level2',
-                'child' => [
-                        'child' => null,
-                    ],
+            'foo' => 'level2',
+            'child' => [
+                'child' => null,
             ],
+        ],
     ];
     */
 
@@ -1031,7 +1031,7 @@ parameter of the ``ObjectNormalizer``::
 
     $obj = $serializer->denormalize(
         ['inner' => ['foo' => 'foo', 'bar' => 'bar'], 'date' => '1988/01/21'],
-         'Acme\ObjectOuter'
+        'Acme\ObjectOuter'
     );
 
     dump($obj->getInner()->foo); // 'foo'