@@ -346,13 +346,12 @@ path to reference these templates, e.g. ``@AcmeFormExtra/form/fields.html.twig``
346346Disabling usage of globally defined themes
347347..........................................
348348
349- Sometimes it is useful to disable usage of globally defined form themes in order
349+ Sometimes you may want to disable the use of the globally defined form themes in order
350350to have more control over rendering of a form. You might want this, for example,
351- when creating admin interface for a bundle which can be installed on a wide range
352- of Symfony apps and you can't control what themes are defined globally.
351+ when creating an admin interface for a bundle which can be installed on a wide range
352+ of Symfony apps ( and so you can't control what themes are defined globally) .
353353
354- You can do this by including the ``only `` keyword after the list of used form
355- themes:
354+ You can do this by including the ``only `` keyword after the list form themes:
356355
357356.. code-block :: html+twig
358357
@@ -364,9 +363,9 @@ themes:
364363
365364 When using the ``only `` keyword, none of Symfony's built-in form themes
366365 (``form_div_layout.html.twig ``, etc.) will be applied. In order to render
367- your forms correctly, you need to either provide a full -featured form theme
366+ your forms correctly, you need to either provide a fully -featured form theme
368367 yourself, or extend one of the built-in form themes with Twig's ``use ``
369- keyword instead of ``extends `` to reuse the original theme contents.
368+ keyword instead of ``extends `` to re-use the original theme contents.
370369
371370 .. code-block :: html+twig
372371
0 commit comments