Skip to content

Commit 20bba4c

Browse files
committed
[book][templating] Rewording the section about formatting to be more clear after some changes
1 parent 7801de3 commit 20bba4c

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

book/templating.rst

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -419,13 +419,14 @@ that specify the *format* and *engine* for that template.
419419
* **BlogBundle:Blog:index.css.twig** - CSS format, Twig engine
420420

421421
By default, any Symfony2 template can be written in either Twig or PHP, and
422-
the second part of the extension specifies which of these two *engines*
423-
should be used. The first part of the extension, (e.g. HTML, CSS, etc)
424-
is the finished format that the template will generate. Unlike the engine,
425-
which determines how Symfony2 parses the template, this is simply an organizational
426-
tactic used in case the same content ever needs to be rendered as HTML
427-
(``index.html.twig``), XML (``index.xml.twig``), or any other format.
428-
For more information, read the :ref:`template-formats` section.
422+
the last part of the extension (e.g. ``.twig`` or ``.php``) specifies which
423+
of these two *engines* should be used. The first part of the extension,
424+
(e.g. ``.html``, ``.css``, etc) is the final format that the template will
425+
generate. Unlike the engine, which determines how Symfony2 parses the template,
426+
this is simply an organizational tactic used in case the same resource needs
427+
to be rendered as HTML (``index.html.twig``), XML (``index.xml.twig``),
428+
or any other format. For more information, read the :ref:`template-formats`
429+
section.
429430

430431
.. note::
431432

0 commit comments

Comments
 (0)