Minor: Fix build

Author: OskarStark

cache.rst

@@ -305,7 +305,7 @@ You can also create more customized pools:
 Each pool manages a set of independent cache keys: keys from different pools
 *never* collide, even if they share the same backend. This is achieved by prefixing
 keys with a namespace that's generated by hashing the name of the pool, the name
-of the compiled container class and a :ref:`configurable seed<reference-cache-prefix-seed>`
+of the compiled container class and a :ref:`configurable seed <reference-cache-prefix-seed>`
 that defaults to the project directory.
 
 Each custom pool becomes a service whose service ID is the name of the pool

configuration/secrets.rst

@@ -102,7 +102,7 @@ Referencing Secrets in Configuration Files
 ------------------------------------------
 
 Secret values can be referenced in the same way as
-:ref:`environment variables<config-env-vars>`. Be careful that you don't
+:ref:`environment variables <config-env-vars>`. Be careful that you don't
 accidentally define a secret *and* an environment variable with the same name:
 **environment variables override secrets**.
 

contributing/code/stack_trace.rst

@@ -137,7 +137,7 @@ going on:
 
 
 If that is not the case, you can obtain a stack trace by increasing the
-:doc:`verbosity level</console/verbosity>` with ``--verbose``:
+:doc:`verbosity level </console/verbosity>` with ``--verbose``:
 
 .. code-block:: terminal
 

mailer.rst

@@ -4,7 +4,7 @@ Sending Emails with Mailer
 .. versionadded:: 4.3
 
     The Mailer component was introduced in Symfony 4.3. The previous solution,
-    called Swift Mailer, is still valid: :doc:`Swift Mailer</email>`.
+    called Swift Mailer, is still valid: :doc:`Swift Mailer </email>`.
 
 Installation
 ------------

profiler.rst

@@ -201,7 +201,7 @@ the AJAX request to force the refresh of the toolbar::
 
 Ideally this header should only be set during development and not for
 production. To do that, create an :doc:`event subscriber </event_dispatcher>`
-and listen to the :ref:`kernel.response<component-http-kernel-kernel-response>`
+and listen to the :ref:`kernel.response <component-http-kernel-kernel-response>`
 event::
 
     use Symfony\Component\HttpKernel\Event\ResponseEvent;

reference/constraints/map.rst.inc

@@ -20,7 +20,7 @@ String Constraints
 * :doc:`Url </reference/constraints/Url>`
 * :doc:`Regex </reference/constraints/Regex>`
 * :doc:`Ip </reference/constraints/Ip>`
-* :doc:`Json</reference/constraints/Json>`
+* :doc:`Json </reference/constraints/Json>`
 * :doc:`Uuid </reference/constraints/Uuid>`
 * :doc:`UserPassword </reference/constraints/UserPassword>`
 * :doc:`NotCompromisedPassword </reference/constraints/NotCompromisedPassword>`

security/ldap.rst

@@ -8,7 +8,7 @@ Symfony provides different means to work with an LDAP server.
 
 The Security component offers:
 
-* The ``ldap`` :doc:`user provider</security/user_provider>`, using the
+* The ``ldap`` :doc:`user provider </security/user_provider>`, using the
   :class:`Symfony\\Component\\Ldap\\Security\\LdapUserProvider`
   class. Like all other user providers, it can be used with any
   authentication provider.