Skip to content

Fixed some RST issues in the recently reworded Templates article #12307

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

Merged
merged 1 commit into from
Sep 12, 2019
Merged

Fixed some RST issues in the recently reworded Templates article #12307

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 templates.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -455,7 +455,7 @@ Rendering a Template Directly from a Route

Although templates are usually rendered in controllers and services, you can
render static pages that don't need any variables directly from the route
definition. Use the special ``TemplateController`` provided by Symfony::
definition. Use the special ``TemplateController`` provided by Symfony:

.. configuration-block::

Expand Down Expand Up @@ -595,7 +595,7 @@ Symfony provides a :ref:`dump() function <components-var-dumper-dump>` as an
improved alternative to PHP's ``var_dump()`` function. This function is useful
to inspect the contents of any variable and you can use it in Twig templates too.

First, make sure that the VarDumper component is installed in the application::
First, make sure that the VarDumper component is installed in the application:

.. code-block:: terminal

Expand Down Expand Up @@ -815,8 +815,8 @@ complex applications:

* ``templates/base.html.twig``, defines the common elements of all application
templates, such as ``<head>``, ``<header>``, ``<footer>``, etc.;
* ``templates/layout.html.twig``, extends from ``base.html.twig``and defines the
content structure used in all or most of the pages, such as a two-column
* ``templates/layout.html.twig``, extends from ``base.html.twig`` and defines
the content structure used in all or most of the pages, such as a two-column
content + sidebar layout. Some sections of the application can define their
own layouts (e.g. ``templates/blog/layout.html.twig``);
* ``templates/*.html.twig``, the application pages which extend from the main
Expand Down