Mar 14, 2016
diff --git a/book/templating.rst b/book/templating.rst
 By default, templates can live in two different locations:

 ``app/Resources/views/``
    Theapplications ``views`` directory can contain application-wide base templates
    Theapplication'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 :ref:`overriding-bundle-templates`).
        }
    }

 The ``recentList`` template is perfectly straightforward:
 The ``recent_list`` template is perfectly straightforward:

 .. configuration-block::


 In this case, you need to specify both the route name (``article_show``) and
 a value for the ``{slug}`` parameter. Using this route, revisit the
 ``recentList`` template from the previous section and link to the articles
 ``recent_list`` template from the previous section and link to the articles
 correctly:

 .. configuration-block::

 Additionally, if you use the ``asset`` function, Symfony can automatically
 append a query string to your asset, in order to guarantee that updated static
 assets won't becached when deployed. For example, ``/images/logo.png`` might
 assets won't beloaded from cache after being deployed. For example, ``/images/logo.png`` might
 look like ``/images/logo.png?v2``. For more information, see the :ref:`reference-framework-assets-version`
 configuration option.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -382,7 +382,7 @@ Template Naming and Locations
		By default, templates can live in two different locations:

		``app/Resources/views/``
		Theapplications ``views`` directory can contain application-wide base templates
		Theapplication'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 :ref:`overriding-bundle-templates`).
Expand DownExpand Up		@@ -616,7 +616,7 @@ articles::
		}
		}

		The ``recentList`` template is perfectly straightforward:
		The ``recent_list`` template is perfectly straightforward:

		.. configuration-block::

Expand DownExpand Up		@@ -975,7 +975,7 @@ route:

		In this case, you need to specify both the route name (``article_show``) and
		a value for the ``{slug}`` parameter. Using this route, revisit the
		``recentList`` template from the previous section and link to the articles
		``recent_list`` template from the previous section and link to the articles
		correctly:

		.. configuration-block::
Expand DownExpand Up		@@ -1053,7 +1053,7 @@ being used and generating the correct paths accordingly.

		Additionally, if you use the ``asset`` function, Symfony can automatically
		append a query string to your asset, in order to guarantee that updated static
		assets won't becached when deployed. For example, ``/images/logo.png`` might
		assets won't beloaded from cache after being deployed. For example, ``/images/logo.png`` might
		look like ``/images/logo.png?v2``. For more information, see the :ref:`reference-framework-assets-version`
		configuration option.

Expand Down