diff --git a/components/serializer.rst b/components/serializer.rst index 0ab12259baa..3e2cb972ae9 100644 --- a/components/serializer.rst +++ b/components/serializer.rst @@ -233,7 +233,7 @@ data. Context ------- -Many Serializer features can be configured :doc:`using a context `. +Many Serializer features can be configured :ref:`using a context `. .. _component-serializer-attributes-groups: diff --git a/configuration/multiple_kernels.rst b/configuration/multiple_kernels.rst index 60d9b83f3e7..249cf08c084 100644 --- a/configuration/multiple_kernels.rst +++ b/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 `: +directory structure like the one described in :doc:`Symfony Best Practice `: .. 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 `, the shared Kernel +follow the :doc:`Symfony 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 diff --git a/mercure.rst b/mercure.rst index fd91c16ad3c..c2a52685f2a 100644 --- a/mercure.rst +++ b/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 `, +Thanks to :doc:`the Docker integration of Symfony `, :ref:`Flex ` proposes to install a Mercure hub. Run ``docker-compose up`` to start the hub if you have chosen this option.