Merge remote-tracking branch 'upstream/7.0' into 7.0

* upstream/7.0:
  -
  Fix comma fopen http_client
  [Constraints] Update `callback` argument type
  Update asset_mapper.rst
  Fix wrong reStructuredText references
  -
  Remove semicolon marking previous end of statement
  [Lock] 15952 Remove mention off DBAL Connection support for locking

Author: javiereguiluz

components/lock.rst

@@ -512,13 +512,12 @@ MongoDB Connection String:
 PdoStore
 ~~~~~~~~
 
-The PdoStore saves locks in an SQL database. It is identical to DoctrineDbalStore
-but requires a `PDO`_ connection or a `Data Source Name (DSN)`_. This store does
-not support blocking, and expects a TTL to avoid stalled locks::
+The PdoStore saves locks in an SQL database. It requires a `PDO`_ connection or a `Data Source Name (DSN)`_.
+This store does not support blocking, and expects a TTL to avoid stalled locks::
 
     use Symfony\Component\Lock\Store\PdoStore;
 
-    // a PDO or DSN for lazy connecting through PDO
+    // a PDO instance or DSN for lazy connecting through PDO
     $databaseConnectionOrDSN = 'mysql:host=127.0.0.1;dbname=app';
     $store = new PdoStore($databaseConnectionOrDSN, ['db_username' => 'myuser', 'db_password' => 'mypassword']);
 
@@ -573,9 +572,8 @@ the :method:`Symfony\\Component\\Lock\\Store\\DoctrineDbalStore::save` method.
 PostgreSqlStore
 ~~~~~~~~~~~~~~~
 
-The PostgreSqlStore and DoctrineDbalPostgreSqlStore uses `Advisory Locks`_ provided by PostgreSQL.
-It is identical to DoctrineDbalPostgreSqlStore but requires `PDO`_ connection or
-a `Data Source Name (DSN)`_. It supports native blocking, as well as sharing
+The PostgreSqlStore uses `Advisory Locks`_ provided by PostgreSQL. It requires a
+`PDO`_ connection or a `Data Source Name (DSN)`_. It supports native blocking, as well as sharing
 locks::
 
     use Symfony\Component\Lock\Store\PostgreSqlStore;

components/serializer.rst

@@ -233,7 +233,7 @@ data.
 Context
 -------
 
-Many Serializer features can be configured :doc:`using a context </serializer#serializer_serializer-context>`.
+Many Serializer features can be configured :ref:`using a context <serializer_serializer-context>`.
 
 .. _component-serializer-attributes-groups:
 

configuration.rst

@@ -259,7 +259,7 @@ reusable configuration value. By convention, parameters are defined under the
 
                 // PHP constants as parameter values
                 ->set('app.some_constant', GLOBAL_CONSTANT)
-                ->set('app.another_constant', BlogPost::MAX_ITEMS);
+                ->set('app.another_constant', BlogPost::MAX_ITEMS)
 
                 // Enum case as parameter values
                 ->set('app.some_enum', PostState::Published);

configuration/multiple_kernels.rst

@@ -53,7 +53,7 @@ requirements, so it's up to you to decide which best suits your project.
 
 First, create a new ``apps`` directory at the root of your project, which will
 hold all the necessary applications. Each application will follow a simplified
-directory structure like the one described in :ref:`Symfony Best Practice </best_practices>`:
+directory structure like the one described in :doc:`Symfony Best Practice </best_practices>`:
 
 .. code-block:: text
 
@@ -321,7 +321,7 @@ Rendering Templates
 -------------------
 
 Let's consider that you need to create another app called ``admin``. If you
-follow the :ref:`Symfony Best Practices </best_practices>`, the shared Kernel
+follow the :doc:`Symfony Best Practices </best_practices>`, the shared Kernel
 templates will be located in the ``templates/`` directory at the project's root.
 For admin-specific templates, you can create a new directory
 ``apps/admin/templates/`` which you will need to manually configure under the

console.rst

@@ -611,10 +611,6 @@ profile is accessible through the web page of the profiler.
     terminal supports links). If you run it in debug verbosity (``-vvv``) you'll
     also see the time and memory consumed by the command.
 
-.. versionadded:: 6.4
-
-    The ``--profile`` option was introduced in Symfony 6.4.
-
 Learn More
 ----------
 

frontend/asset_mapper.rst

@@ -1007,7 +1007,7 @@ both ``app`` and ``checkout``:
     {% block importmap %}
         {# do NOT call parent() #}
 
-        {{ importmap('app', 'checkout') }}
+        {{ importmap(['app', 'checkout']) }}
     {% endblock %}
 
 By passing both ``app`` and ``checkout``, the ``importmap()`` function will

http_client.rst

@@ -619,7 +619,7 @@ A generator or any ``Traversable`` can also be used instead of a closure.
 
 To submit a form with file uploads, pass the file handle to the ``body`` option::
 
-    $fileHandle = fopen('/path/to/the/file' 'r');
+    $fileHandle = fopen('/path/to/the/file', 'r');
     $client->request('POST', 'https://...', ['body' => ['the_file' => $fileHandle]]);
 
 By default, this code will populate the filename and content-type with the data

mercure.rst

@@ -53,7 +53,7 @@ that handles persistent SSE connections with the clients.
 The Symfony app publishes the updates to the hub, that will broadcast them to
 clients.
 
-Thanks to :ref:`the Docker integration of Symfony </setup/docker>`,
+Thanks to :doc:`the Docker integration of Symfony </setup/docker>`,
 :ref:`Flex <symfony-flex>` proposes to install a Mercure hub.
 Run ``docker-compose up`` to start the hub if you have chosen this option.
 

reference/constraints/Choice.rst

@@ -262,7 +262,7 @@ Available Options
 ``callback``
 ~~~~~~~~~~~~
 
-**type**: ``string|array|Closure``
+**type**: ``callable|string|null`` **default**: ``null``
 
 This is a callback method that can be used instead of the `choices`_ option
 to return the choices array. See