diff --git a/.doctor-rst.yaml b/.doctor-rst.yaml index 1c760251f18..6711c75c8f2 100644 --- a/.doctor-rst.yaml +++ b/.doctor-rst.yaml @@ -29,6 +29,7 @@ rules: replace_code_block_types: ~ replacement: ~ short_array_syntax: ~ + space_between_label_and_link_in_doc: ~ space_between_label_and_link_in_ref: ~ typo: ~ unused_links: ~ diff --git a/best_practices/security.rst b/best_practices/security.rst index 19ba9f7e330..63d95e27458 100644 --- a/best_practices/security.rst +++ b/best_practices/security.rst @@ -6,7 +6,7 @@ Authentication and Firewalls (i.e. Getting the User's Credentials) You can configure Symfony to authenticate your users using any method you want and to load user information from any source. This is a complex topic, but -the :doc:`Security guide` has a lot of information about +the :doc:`Security guide ` has a lot of information about this. Regardless of your needs, authentication is configured in ``security.yml``, diff --git a/contributing/code_of_conduct/code_of_conduct.rst b/contributing/code_of_conduct/code_of_conduct.rst index 7ecd91e8dbd..857d5437538 100644 --- a/contributing/code_of_conduct/code_of_conduct.rst +++ b/contributing/code_of_conduct/code_of_conduct.rst @@ -37,7 +37,7 @@ Examples of unacceptable behavior by participants include: Our Responsibilities -------------------- -:doc:`CoC Active Response Ensurers, or CARE`, +:doc:`CoC Active Response Ensurers, or CARE `, are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. diff --git a/contributing/map.rst.inc b/contributing/map.rst.inc index b9c9311a6cb..b495a0d76d0 100644 --- a/contributing/map.rst.inc +++ b/contributing/map.rst.inc @@ -15,9 +15,9 @@ * :doc:`Security ` * :doc:`Tests ` * :doc:`Backward Compatibility ` - * :doc:`Coding Standards` - * :doc:`Code Conventions` - * :doc:`Git` + * :doc:`Coding Standards ` + * :doc:`Code Conventions ` + * :doc:`Git ` * :doc:`License ` * **Documentation** diff --git a/deployment/proxies.rst b/deployment/proxies.rst index 6791605225c..7a130f4783c 100644 --- a/deployment/proxies.rst +++ b/deployment/proxies.rst @@ -3,7 +3,7 @@ How to Configure Symfony to Work behind a Load Balancer or a Reverse Proxy When you deploy your application, you may be behind a load balancer (e.g. an AWS Elastic Load Balancing) or a reverse proxy (e.g. Varnish for -:doc:`caching`). +:doc:`caching `). For the most part, this doesn't cause any problems with Symfony. But, when a request passes through a proxy, certain request information is sent using diff --git a/frontend/encore/simple-example.rst b/frontend/encore/simple-example.rst index aaf543a11fb..7a9800dd3b3 100644 --- a/frontend/encore/simple-example.rst +++ b/frontend/encore/simple-example.rst @@ -121,8 +121,8 @@ be executed. All the CSS files that were required will also be displayed. The ``encore_entry_link_tags()`` and ``encore_entry_script_tags()`` functions read from an ``entrypoints.json`` file that's generated by Encore to know the exact filename(s) to render. This file is *especially* useful because you can -:doc:`enable versioning` or -:doc:`point assets to a CDN` without making *any* changes to your +:doc:`enable versioning ` or +:doc:`point assets to a CDN ` without making *any* changes to your template: the paths in ``entrypoints.json`` will always be the final, correct paths. If you're *not* using Symfony, you can ignore the ``entrypoints.json`` file and diff --git a/reference/constraints/map.rst.inc b/reference/constraints/map.rst.inc index e0eae320682..6afc32008ea 100644 --- a/reference/constraints/map.rst.inc +++ b/reference/constraints/map.rst.inc @@ -20,7 +20,7 @@ String Constraints * :doc:`Url ` * :doc:`Regex ` * :doc:`Ip ` -* :doc:`Uuid` +* :doc:`Uuid ` * :doc:`UserPassword ` Comparison Constraints diff --git a/reference/forms/types/options/validation_groups.rst.inc b/reference/forms/types/options/validation_groups.rst.inc index dd9efcd8967..90f79bede75 100644 --- a/reference/forms/types/options/validation_groups.rst.inc +++ b/reference/forms/types/options/validation_groups.rst.inc @@ -49,7 +49,7 @@ the option. Symfony will then pass the form when calling it:: .. note:: When your form contains multiple submit buttons, you can change the - validation group depending on :doc:`which button is used` + validation group depending on :doc:`which button is used ` to submit the form. If you need advanced logic to determine the validation groups have diff --git a/reference/forms/types/submit.rst b/reference/forms/types/submit.rst index cd4cbe55cc7..adefa204fed 100644 --- a/reference/forms/types/submit.rst +++ b/reference/forms/types/submit.rst @@ -16,7 +16,7 @@ A submit button. | | - `translation_domain`_ | | | - `validation_groups`_ | +----------------------+----------------------------------------------------------------------+ -| Parent type | :doc:`ButtonType` | +| Parent type | :doc:`ButtonType ` | +----------------------+----------------------------------------------------------------------+ | Class | :class:`Symfony\\Component\\Form\\Extension\\Core\\Type\\SubmitType` | +----------------------+----------------------------------------------------------------------+