Merge branch '5.4' into 6.3

* 5.4:
  Fix wrong reStructuredText references

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

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.