Merge branch '3.1'

* 3.1: (35 commits)
  [KnpU] Making common 3.0 changes (e.g. app/console -> bin/console)
  using shorter command name
  fixing app/console
  Fixing heading styles that I just messed up!
  Minor tweaks!
  Tweaks!
  Fixed some misconfigured redirections
  Tweaks thanks to comments
  minor tweaks
  Completely updating the configuration main chapter to talk about parameters and a few other details
  more tweaks
  Moving configuration/configuration.rst -> configuration.rst
  Tweaks thanks to Javier
  Updating and massively shortening page creation
  Moving http_fundamentals into introduction
  Moving web server configuration out of configuration - it has nothing to do with Symfony configuration
  Fixing references
  Moving logging/monolog.rst to /logging.rst, removing some sections from it, rewriting others
  Another batch of build error fixes
  language tweak
  ...

Author: weaverryan

_includes/_rewrite_rule_tip.rst.inc

@@ -1,6 +1,6 @@
 .. tip::
 
     By using rewrite rules in your
-    :doc:`web server configuration </configuration/web_server_configuration>`,
+    :doc:`web server configuration </setup/web_server_configuration>`,
     the ``index.php`` won't be needed and you will have beautiful, clean URLs
     (e.g. ``/show``).

best_practices/creating-the-project.rst

@@ -12,7 +12,7 @@ Installer**, which has to be installed before creating your first project.
 
     Use the Symfony Installer to create new Symfony-based projects.
 
-Read the :doc:`installation chapter </installation>` of the Symfony Book to
+Read the :doc:`installation & setup chapter </setup>` of the Symfony Book to
 learn how to install and use the Symfony Installer.
 
 .. _linux-and-mac-os-x-systems:

bundles/override.rst

@@ -12,7 +12,7 @@ Templates
 
 For information on overriding templates, see
 
-* :ref:`overriding-bundle-templates`.
+* :doc:`/templating/overriding`.
 * :doc:`/bundles/inheritance`
 
 Routing

cache/form_csrf_caching.rst

@@ -8,7 +8,7 @@ CSRF tokens are meant to be different for every user. This is why you
 need to be cautious if you try to cache pages with forms including them.
 
 For more information about how CSRF protection works in Symfony, please
-check :ref:`CSRF Protection <forms-csrf>`.
+check :doc:`CSRF Protection </form/csrf_protection>`.
 
 Why Caching Pages with a CSRF token is Problematic
 --------------------------------------------------

cache/varnish.rst

@@ -77,7 +77,7 @@ If you know for sure that the backend never uses sessions or basic
 authentication, have Varnish remove the corresponding header from requests to
 prevent clients from bypassing the cache. In practice, you will need sessions
 at least for some parts of the site, e.g. when using forms with
-:ref:`CSRF Protection <forms-csrf>`. In this situation, make sure to
+:doc:`CSRF Protection </form/csrf_protection>`. In this situation, make sure to
 :doc:`only start a session when actually needed </session/avoid_session_start>`
 and clear the session when it is no longer needed. Alternatively, you can look
 into :doc:`/cache/form_csrf_caching`.

components/form.rst

@@ -514,7 +514,7 @@ That's it! By printing ``form_widget(form)``, each field in the form is
 rendered, along with a label and error message (if there is one). As easy
 as this is, it's not very flexible (yet). Usually, you'll want to render each
 form field individually so you can control how the form looks. You'll learn how
-to do that in the ":ref:`form-rendering-template`" section.
+to do that in the ":doc:`/form/rendering`" section.
 
 Changing a Form's Method and Action
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -720,15 +720,6 @@ method to access the list of errors. It returns a
     // a FormErrorIterator instance representing the form tree structure
     $errors = $form->getErrors(true, false);
 
-Learn More
-----------
-
-.. toctree::
-    :maxdepth: 1
-    :glob:
-
-    form/*
-
 .. _Packagist: https://packagist.org/packages/symfony/form
 .. _Twig: http://twig.sensiolabs.org
 .. _`Twig Configuration`: http://twig.sensiolabs.org/doc/intro.html