minor #9936 Removed a short article about overriding bundle templates (javiereguiluz)

This PR was squashed before being merged into the 4.0 branch (closes #9936).

Discussion
----------

Removed a short article about overriding bundle templates

Spotted while fixing #9923.

@stof I have a question for you. I left this caution but I don't know if it's still needed:

```rst
.. caution::

    If you add a template in a new location, you *may* need to clear your
    cache (``php bin/console cache:clear``), even if you are in debug mode.
```

I tested in a Symfony 4 app. If I add a new template in my app, there's no need to clear the cache in `dev`. Does this caution only applies when adding new templates to override bundles? Or is it something no longer relevant in Symfony 4? Thanks!

Commits
-------

44a33a4 Removed a short article about overriding bundle templates

Author: javiereguiluz

_build/redirection_map

@@ -388,3 +388,4 @@
 /quick_tour/the_controller /quick_tour/the_big_picture
 /quick_tour/the_view /quick_tour/flex_recipes
 /service_container/service_locators /service_container/service_subscribers_locators
+/templating/overriding /bundles/override

bundles/override.rst

@@ -16,10 +16,33 @@ features of a bundle.
     and call the :ref:`locateResource() method <http-kernel-resource-locator>`
     to turn them into physical paths when needed.
 
+.. _override-templates:
+
 Templates
 ---------
 
-See :doc:`/templating/overriding`.
+Third-party bundle templates can be overridden in the
+``<your-project>/templates/bundles/<bundle-name>/`` directory. The new templates
+must use the same name and path (relative to ``<bundle>/Resources/views/``) as
+the original templates.
+
+For example, to override the ``Resources/views/Registration/confirmed.html.twig``
+template from the FOSUserBundle, create this template:
+``<your-project>/templates/bundles/FOSUserBundle/Registration/confirmed.html.twig``
+
+.. caution::
+
+    If you add a template in a new location, you *may* need to clear your
+    cache (``php bin/console cache:clear``), even if you are in debug mode.
+
+.. _templating-overriding-core-templates:
+
+.. tip::
+
+    Symfony internals use some bundles too, so you can apply the same technique
+    to override the core Symfony templates. For example, you can
+    :doc:`customize error pages </controller/error_pages>` overriding TwigBundle
+    templates.
 
 Routing
 -------

controller/error_pages.rst

@@ -65,8 +65,8 @@ logic to determine the template filename:
 
 .. _overriding-or-adding-templates:
 
-To override these templates, simply rely on the standard Symfony method for
-:doc:`overriding templates that live inside a bundle </templating/overriding>`:
+To override these templates, rely on the standard Symfony method for
+:ref:`overriding templates that live inside a bundle <override-templates>` and
 put them in the ``templates/bundles/TwigBundle/Exception/`` directory.
 
 A typical project that returns HTML and JSON pages, might look like this:

templating.rst

@@ -360,8 +360,7 @@ By default, templates can live in two different locations:
 ``templates/``
     The application's ``views`` directory can contain application-wide base templates
     (i.e. your application's layouts and templates of the application bundle) as
-    well as templates that override third party bundle templates
-    (see :doc:`/templating/overriding`).
+    well as templates that :ref:`override third party bundle templates <override-templates>`.
 
 ``vendor/path/to/CoolBundle/Resources/views/``
     Each third party bundle houses its templates in its ``Resources/views/``
@@ -405,10 +404,8 @@ for several types of templates, each which lives in a specific location:
   is missing (e.g. ``Blog``), the template lives at
   ``Resources/views/layout.html.twig`` inside AcmeBlogBundle.
 
-In the :doc:`/templating/overriding` section, you'll find out how each
-template living inside the AcmeBlogBundle, for example, can be overridden
-by placing a template of the same name in the ``templates/bundles/AcmeBlogBundle/``
-directory. This gives the power to override templates from any vendor bundle.
+Using this namespaced syntax instead of the real file paths allows applications
+to :ref:`override templates that live inside any bundle <override-templates>`.
 
 Template Suffix
 ~~~~~~~~~~~~~~~