Merge branch '6.4' into 7.0

* 6.4:
  clarify how to disable client-side validation using the Regex constraint
  Fix ScheduledStamp FQN
  example function param 1 requires string
  Minor tweak in the setup page
  Update configuration.rst
  style: Typo in content title
  fix dump destination value in PHP config

bundles/configuration.rst

@@ -93,7 +93,7 @@ class, you can add all the logic related to processing the configuration in that
             // the "$config" variable is already merged and processed so you can
             // use it directly to configure the service container (when defining an
             // extension class, you also have to do this merging and processing)
-            $containerConfigurator->services()
+            $container->services()
                 ->get('acme_social.twitter_client')
                 ->arg(0, $config['twitter']['client_id'])
                 ->arg(1, $config['twitter']['client_secret'])

components/messenger.rst

@@ -162,7 +162,7 @@ Here are some important envelope stamps that are shipped with the Symfony Messen
   to configure the validation groups used when the validation middleware is enabled.
 * :class:`Symfony\\Component\\Messenger\\Stamp\\ErrorDetailsStamp`,
   an internal stamp when a message fails due to an exception in the handler.
-* :class:`Symfony\\Component\\Messenger\\Stamp\\ScheduledStamp`,
+* :class:`Symfony\\Component\\Scheduler\\Messenger\\ScheduledStamp`,
   a stamp that marks the message as produced by a scheduler. This helps
   differentiate it from messages created "manually". You can learn more about it
   in the :doc:`Scheduler documentation </scheduler>`.

components/var_dumper.rst

@@ -623,7 +623,7 @@ For example, to get a dump as a string in a variable, you can do::
 
     $dumper->dump(
         $cloner->cloneVar($variable),
-        function (int $line, int $depth) use (&$output): void {
+        function (string $line, int $depth) use (&$output): void {
             // A negative depth means "end of dump"
             if ($depth >= 0) {
                 // Adds a two spaces indentation to the line

reference/configuration/debug.rst

@@ -95,7 +95,7 @@ Typically, you would set this to ``php://stderr``:
 
         return static function (ContainerConfigurator $container): void {
             $container->extension('debug', [
-                'dump_destination' => 'tcp://%env(VAR_DUMPER_SERVER)%',
+                'dump_destination' => 'php://stderr',
             ]);
         };
 

reference/constraints/Regex.rst

@@ -163,7 +163,7 @@ Options
 ``htmlPattern``
 ~~~~~~~~~~~~~~~
 
-**type**: ``string|boolean`` **default**: ``null``
+**type**: ``string|null`` **default**: ``null``
 
 This option specifies the pattern to use in the HTML5 ``pattern`` attribute.
 You usually don't need to specify this option because by default, the constraint
@@ -243,7 +243,7 @@ need to specify the HTML5 compatible pattern in the ``htmlPattern`` option:
             }
         }
 
-Setting ``htmlPattern`` to false will disable client side validation.
+Setting ``htmlPattern`` to the empty string will disable client side validation.
 
 ``match``
 ~~~~~~~~~

setup.rst

@@ -34,7 +34,7 @@ requirements. Open your console terminal and run this command:
 
 .. note::
 
-    The Symfony CLI is written in Go and you can contribute to it in the
+    The Symfony CLI is open source, and you can contribute to it in the
     `symfony-cli/symfony-cli GitHub repository`_.
 
 .. _creating-symfony-applications:

testing/database.rst

@@ -83,7 +83,7 @@ the employee which gets returned by the ``Repository``, which itself gets
 returned by the ``EntityManager``. This way, no real class is involved in
 testing.
 
-Functional Testing of A Doctrine Repository
+Functional Testing of a Doctrine Repository
 -------------------------------------------
 
 In :ref:`functional tests <functional-tests>` you'll make queries to the