Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minor corrections #6369

Closed
wants to merge 1 commit into from
Closed

Minor corrections #6369

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions book/templating.rst
View file
Open in desktop
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/``
The applications ``views`` directory can contain application-wide base 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 :ref:`overriding-bundle-templates`).
Expand Down Expand Up @@ -616,7 +616,7 @@ articles::
}
}

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

.. configuration-block::

Expand Down Expand 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 Down Expand 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 be cached when deployed. For example, ``/images/logo.png`` might
assets won't be loaded 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