Merge branch '2.8' into 3.4

* 2.8:
  fixing second stopwatch example in phpunit-bridge docs
  fix console script path
  improve validation groups references
  Fix typo

Author: xabbuh

components/form.rst

@@ -728,7 +728,7 @@ method to access the list of errors. It returns a
     // ...
 
     // a FormErrorIterator instance, but only errors attached to this
-    // form level (e.g. "global errors)
+    // form level (e.g. global errors)
     $errors = $form->getErrors();
 
     // a FormErrorIterator instance, but only errors attached to the

components/phpunit_bridge.rst

@@ -296,11 +296,11 @@ test::
         {
             $stopwatch = new Stopwatch();
 
-            $stopwatch->start();
+            $stopwatch->start('event_name');
             sleep(10);
-            $duration = $stopwatch->stop();
+            $duration = $stopwatch->stop('event_name')->getDuration();
 
-            $this->assertEquals(10, $duration);
+            $this->assertEquals(10000, $duration);
         }
     }
 

configuration/multiple_kernels.rst

@@ -143,9 +143,9 @@ config files or better, import them and override the needed options:
 Executing Commands with a Different Kernel
 ------------------------------------------
 
-The ``bin/console`` script used to run Symfony commands always uses the default
+The ``app/console`` script used to run Symfony commands always uses the default
 ``AppKernel`` class to build the application and load the commands. If you need
-to execute console commands using the new kernel, duplicate the ``bin/console``
+to execute console commands using the new kernel, duplicate the ``app/console``
 script and rename it (e.g. ``bin/api``).
 
 Then, replace the ``AppKernel`` instantiation by your own kernel instantiation
@@ -155,7 +155,7 @@ new kernel.
 
 .. note::
 
-    The commands available for each console script (e.g. ``bin/console`` and
+    The commands available for each console script (e.g. ``app/console`` and
     ``bin/api``) can differ because they depend on the bundles enabled for each
     kernel, which could be different.
 

reference/events.rst

@@ -43,7 +43,7 @@ their priorities:
 
 .. code-block:: terminal
 
-    $ php bin/console debug:event-dispatcher kernel.request
+    $ php app/console debug:event-dispatcher kernel.request
 
 ``kernel.controller``
 ~~~~~~~~~~~~~~~~~~~~~
@@ -74,7 +74,7 @@ their priorities:
 
 .. code-block:: terminal
 
-    $ php bin/console debug:event-dispatcher kernel.controller
+    $ php app/console debug:event-dispatcher kernel.controller
 
 ``kernel.view``
 ~~~~~~~~~~~~~~~
@@ -108,7 +108,7 @@ their priorities:
 
 .. code-block:: terminal
 
-    $ php bin/console debug:event-dispatcher kernel.view
+    $ php app/console debug:event-dispatcher kernel.view
 
 ``kernel.response``
 ~~~~~~~~~~~~~~~~~~~
@@ -135,7 +135,7 @@ their priorities:
 
 .. code-block:: terminal
 
-    $ php bin/console debug:event-dispatcher kernel.response
+    $ php app/console debug:event-dispatcher kernel.response
 
 ``kernel.finish_request``
 ~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -162,7 +162,7 @@ their priorities:
 
 .. code-block:: terminal
 
-    $ php bin/console debug:event-dispatcher kernel.finish_request
+    $ php app/console debug:event-dispatcher kernel.finish_request
 
 ``kernel.terminate``
 ~~~~~~~~~~~~~~~~~~~~
@@ -183,7 +183,7 @@ their priorities:
 
 .. code-block:: terminal
 
-    $ php bin/console debug:event-dispatcher kernel.terminate
+    $ php app/console debug:event-dispatcher kernel.terminate
 
 .. _kernel-kernel.exception:
 
@@ -256,6 +256,6 @@ their priorities:
 
 .. code-block:: terminal
 
-    $ php bin/console debug:event-dispatcher kernel.exception
+    $ php app/console debug:event-dispatcher kernel.exception
 
 .. _`param converters`: https://symfony.com/doc/master/bundles/SensioFrameworkExtraBundle/annotations/converters.html

validation/groups.rst

@@ -137,7 +137,7 @@ With this configuration, there are three validation groups:
 ``User``
     Equivalent to all constraints of the ``User`` object in the ``Default``
     group. This is always the name of the class. The difference between this
-    and ``Default`` is explained below.
+    and ``Default`` is explained in :doc:`/validation/sequence_provider`.
 
 ``registration``
     Contains the constraints on the ``email`` and ``password`` fields only.

validation/sequence_provider.rst

@@ -128,7 +128,7 @@ that group are valid, the second group, ``Strict``, will be validated.
 
 .. caution::
 
-    As you have already seen in the previous section, the ``Default`` group
+    As you have already seen in :doc:`/validation/groups`, the ``Default`` group
     and the group containing the class name (e.g. ``User``) were identical.
     However, when using Group Sequences, they are no longer identical. The
     ``Default`` group will now reference the group sequence, instead of all