Fixed all references

javiereguiluz · javiereguiluz · commit a9830236eb75 · 2019-06-07T09:29:28.000+02:00
diff --git a/best_practices/configuration.rst b/best_practices/configuration.rst
@@ -83,7 +83,7 @@ layer of configuration that's not needed because you don't need or want these
 configuration values to change on each server.
 
 The configuration options defined in the ``services.yaml`` may vary from one
-:doc:`environment </configuration/environments>` to another. That's why Symfony
+:ref:`environment <configuration-environments>` to another. That's why Symfony
 supports defining ``config/services_dev.yaml`` and ``config/services_prod.yaml``
 files so that you can override specific values for each environment.
 
diff --git a/bundles.rst b/bundles.rst
@@ -18,7 +18,7 @@ SecurityBundle, DebugBundle, etc.) They are also used to add new features in
 your application via `third-party bundles`_.
 
 Bundles used in your applications must be enabled per
-:doc:`environment </configuration/environments>` in the ``config/bundles.php``
+:ref:`environment <configuration-environments>` in the ``config/bundles.php``
 file::
 
     // config/bundles.php
diff --git a/configuration.rst b/configuration.rst
@@ -19,9 +19,9 @@ directory, which has this default structure:
 
 The ``routes.yaml`` file defines the :doc:`routing configuration </routing>`;
 the ``services.yaml`` file configures the services of the
-:ref:`service container </service_container>`; the ``bundles.php`` file enables/
+:doc:`service container </service_container>`; the ``bundles.php`` file enables/
 disables packages in your application and it's managed automatically by
-:ref:`Symfony Flex </setup/flex>`.
+:doc:`Symfony Flex </setup/flex>`.
 
 The most important element inside ``config/`` is the ``packages/`` directory,
 which stores the configuration of every package installed in your application.
@@ -45,7 +45,7 @@ to change these files after package installation
 .. tip::
 
     To learn about all the available configuration options, check out the
-    :ref:`Symfony Configuration Reference </reference/index>` or run the
+    :doc:`Symfony Configuration Reference </reference/index>` or run the
     ``config:dump-reference`` command.
 
 Configuration Formats
@@ -511,7 +511,7 @@ Configuring Environment Variables in Production
 In production, the ``.env`` files are also parsed and loaded on each request so
 you can override the env vars already defined in the server. In order to improve
 performance, you can run the ``dump-env`` command (available when using
-:ref:`Symfony Flex </setup/flex>` 1.2 or later).
+:doc:`Symfony Flex </setup/flex>` 1.2 or later).
 
 This command parses all the ``.env`` files once and compiles their contents into
 a new PHP-optimized file called  ``.env.local.php``. From that moment, Symfony
diff --git a/configuration/front_controllers_and_kernel.rst b/configuration/front_controllers_and_kernel.rst
@@ -5,11 +5,11 @@
 Understanding how the Front Controller, Kernel and Environments Work together
 =============================================================================
 
-The section :doc:`/configuration/environments` explained the basics on how
-Symfony uses environments to run your application with different configuration
-settings. This section will explain a bit more in-depth what happens when your
-application is bootstrapped. To hook into this process, you need to understand
-three parts that work together:
+The :ref:`configuration environments <configuration-environments>` section
+explained the basics on how Symfony uses environments to run your application
+with different configuration settings. This section will explain a bit more
+in-depth what happens when your application is bootstrapped. To hook into this
+process, you need to understand three parts that work together:
 
 * `The Front Controller`_
 * `The Kernel Class`_
@@ -204,9 +204,9 @@ As mentioned above, the ``Kernel`` has to implement another method -
 This method is responsible for loading the application's configuration from the
 right *environment*.
 
-Environments have been covered extensively :doc:`in the previous article
-</configuration/environments>`, and you probably remember that the Symfony uses
-by default three of them - ``dev``, ``prod`` and ``test``.
+:ref:`Configuration environments <configuration-environments>` allow to execute
+the same code using different configuration. Symfony provides three environments
+by default called ``dev``, ``prod`` and ``test``.
 
 More technically, these names are nothing more than strings passed from the
 front controller to the ``Kernel``'s constructor. This name can then be used in
diff --git a/configuration/multiple_kernels.rst b/configuration/multiple_kernels.rst
@@ -16,7 +16,7 @@ request to generate the response.
 
 This single kernel approach is a convenient default, but Symfony applications
 can define any number of kernels. Whereas
-:doc:`environments </configuration/environments>` execute the same application
+:ref:`environments <configuration-environments>` execute the same application
 with different configurations, kernels can execute different parts of the same
 application.
 
diff --git a/controller/error_pages.rst b/controller/error_pages.rst
@@ -17,7 +17,7 @@ customize error pages, so run this command to make sure the bundle is installed:
 
     $ composer require twig
 
-In the :doc:`development environment </configuration/environments>`,
+In the :ref:`development environment <configuration-environments>`,
 Symfony catches all the exceptions and displays a special **exception page**
 with lots of debug information to help you discover the root problem:
 
diff --git a/reference/configuration/kernel.rst b/reference/configuration/kernel.rst
@@ -109,7 +109,7 @@ Cache Directory
 
 This returns the absolute path of the cache directory of your Symfony project.
 It's calculated automatically based on the current
-:doc:`environment </configuration/environments>`.
+:ref:`environment <configuration-environments>`.
 
 This value is exposed via the ``kernel.cache_dir`` configuration parameter and
 the :method:`Symfony\\Component\\HttpKernel\\Kernel::getCacheDir` method. To
@@ -123,7 +123,7 @@ Log Directory
 
 This returns the absolute path of the log directory of your Symfony project.
 It's calculated automatically based on the current
-:doc:`environment </configuration/environments>`.
+:ref:`environment <configuration-environments>`.
 
 This value is exposed via the ``kernel.log_dir`` configuration parameter and
 the :method:`Symfony\\Component\\HttpKernel\\Kernel::getLogDir` method. To
diff --git a/setup/upgrade_major.rst b/setup/upgrade_major.rst
@@ -37,7 +37,7 @@ using these deprecated features in the last version before the major (e.g.
 
 To help you with this, deprecation notices are triggered whenever you end up
 using a deprecated feature. When visiting your application in the
-:doc:`dev environment </configuration/environments>`
+:ref:`dev environment <configuration-environments>`
 in your browser, these notices are shown in the web dev toolbar:
 
 .. image:: /_images/install/deprecations-in-profiler.png
