Fixed doc build issues

Author: javiereguiluz

components/console/helpers/formatterhelper.rst

@@ -62,4 +62,4 @@ messages and 2 spaces on the left and right).
 
 The exact "style" you use in the block is up to you. In this case, you're using
 the pre-defined ``error`` style, but there are other styles, or you can create
-your own. See :ref:`components-console-coloring`.
+your own. See :doc:`/console/coloring`.

setup.rst

@@ -274,11 +274,10 @@ Learn More
     setup/web_server_configuration
     setup/composer
     setup/*
-    install/*
 
 .. _`Composer`: https://getcomposer.org/
 .. _`Symfony Standard Edition`: https://github.com/symfony/symfony-standard
-.. _`Symfony CMF Standard Edition`: https://github.com/symfony-cmf/symfony-cmf-standard
+.. _`The Symfony CMF Standard Edition`: https://github.com/symfony-cmf/symfony-cmf-standard
 .. _`Symfony CMF`: http://cmf.symfony.com/
 .. _`Symfony REST Edition`: https://github.com/gimler/symfony-rest-edition
 .. _`FOSRestBundle`: https://github.com/FriendsOfSymfony/FOSRestBundle

setup/upgrade_major.rst

@@ -25,7 +25,7 @@ There are a couple of steps to upgrading a major version:
 
 During the lifecycle of a major release, new features are added and method
 signatures and public API usages are changed. However,
-:doc:`minor versions </install/upgrade_minor>` should not contain any
+:doc:`minor versions </setup/upgrade_minor>` should not contain any
 backwards incompatible changes. To accomplish this, the "old" (e.g. functions,
 classes, etc) code still works, but is marked as *deprecated*, indicating that
 it will be removed/changed in the future and that you should stop using it.

setup/upgrade_patch.rst

@@ -23,4 +23,4 @@ update.
     It is recommended to update to a new patch version as soon as possible, as
     important bugs and security leaks may be fixed in these new releases.
 
-.. include:: /install/_update_all_packages.rst.inc
+.. include:: /setup/_update_all_packages.rst.inc