Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 8c4bcc8

Browse filesBrowse files
committed
[#8495] some minor tweaks
1 parent 0719bb1 commit 8c4bcc8
Copy full SHA for 8c4bcc8

File tree

1 file changed

+3
-3
lines changed
Filter options

1 file changed

+3
-3
lines changed

‎form/form_customization.rst

Copy file name to clipboardExpand all lines: form/form_customization.rst
+3-3Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -297,15 +297,15 @@ name of all the templates as an array using the ``with`` keyword:
297297
The templates can also be located in different bundles, use the Twig namespaced
298298
path to reference these templates, e.g. ``@AcmeFormExtra/form/fields.html.twig``.
299299

300-
Disabling usage of globally defined themes
300+
Disabling Usage of Globally Defined Themes
301301
..........................................
302302

303303
Sometimes you may want to disable the use of the globally defined form themes in order
304-
to have more control over rendering of a form. You might want this, for example,
304+
to have more control over the rendering of a form. You might want this, for example,
305305
when creating an admin interface for a bundle which can be installed on a wide range
306306
of Symfony apps (and so you can't control what themes are defined globally).
307307

308-
You can do this by including the ``only`` keyword after the list form themes:
308+
You can do this by including the ``only`` keyword after the list of form themes:
309309

310310
.. code-block:: html+twig
311311

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.