@@ -387,7 +387,7 @@ Template Naming and Locations
387
387
By default, templates can live in two different locations:
388
388
389
389
``app/Resources/views/ ``
390
- The applications ``views `` directory can contain application-wide base templates
390
+ The application's ``views `` directory can contain application-wide base templates
391
391
(i.e. your application's layouts and templates of the application bundle) as
392
392
well as templates that override third party bundle templates
393
393
(see :ref: `overriding-bundle-templates `).
@@ -625,7 +625,7 @@ articles::
625
625
}
626
626
}
627
627
628
- The ``recentList `` template is perfectly straightforward:
628
+ The ``recent_list `` template is perfectly straightforward:
629
629
630
630
.. configuration-block ::
631
631
@@ -990,7 +990,7 @@ route:
990
990
991
991
In this case, you need to specify both the route name (``article_show ``) and
992
992
a value for the ``{slug} `` parameter. Using this route, revisit the
993
- ``recentList `` template from the previous section and link to the articles
993
+ ``recent_list `` template from the previous section and link to the articles
994
994
correctly:
995
995
996
996
.. configuration-block ::
@@ -1074,8 +1074,8 @@ being used and generating the correct paths accordingly.
1074
1074
1075
1075
Additionally, if you use the ``asset `` function, Symfony can automatically
1076
1076
append a query string to your asset, in order to guarantee that updated static
1077
- assets won't be cached when deployed. For example, ``/images/logo.png `` might
1078
- look like ``/images/logo.png?v2 ``. For more information, see the :ref: `ref -framework-assets-version `
1077
+ assets won't be loaded from cache after being deployed. For example, ``/images/logo.png `` might
1078
+ look like ``/images/logo.png?v2 ``. For more information, see the :ref: `reference -framework-assets-version `
1079
1079
configuration option.
1080
1080
1081
1081
.. index ::
0 commit comments