Fixing heading styles that I just messed up!

Author: weaverryan

form/embedded.rst

@@ -12,7 +12,7 @@ is easy and natural with the Form component.
 .. _forms-embedding-single-object:
 
 Embedding a Single Object
-~~~~~~~~~~~~~~~~~~~~~~~~~
+-------------------------
 
 Suppose that each ``Task`` belongs to a simple ``Category`` object. Start,
 of course, by creating the ``Category`` object::
@@ -140,7 +140,7 @@ The ``Category`` instance is accessible naturally via ``$task->getCategory()``
 and can be persisted to the database or used however you need.
 
 Embedding a Collection of Forms
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+-------------------------------
 
 You can also embed a collection of forms into one form (imagine a ``Category``
 form with many ``Product`` sub-forms). This is done by using the ``collection``

form/form_themes.rst

@@ -100,7 +100,7 @@ For a more extensive discussion, see :doc:`/form/form_customization`.
 .. _form-template-blocks:
 
 Form Fragment Naming
-~~~~~~~~~~~~~~~~~~~~
+--------------------
 
 In Symfony, every part of a form that is rendered - HTML form elements, errors,
 labels, etc. - is defined in a base theme, which is a collection of blocks
@@ -151,7 +151,7 @@ to be overridden (e.g. ``textarea_widget``).
    single: Forms; Template fragment inheritance
 
 Template Fragment Inheritance
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+-----------------------------
 
 In some cases, the fragment you want to customize will appear to be missing.
 For example, there is no ``textarea_errors`` fragment in the default themes
@@ -180,7 +180,7 @@ override the default error rendering for *all* fields, copy and customize the
 .. _book-forms-theming-global:
 
 Global Form Theming
-~~~~~~~~~~~~~~~~~~~
+-------------------
 
 In the above example, you used the ``form_theme`` helper (in Twig) to "import"
 the custom form fragments into *just* that form. You can also tell Symfony

form/rendering.rst

@@ -63,7 +63,7 @@ output can be customized on many different levels.
    single: Forms; Rendering each field by hand
 
 Rendering each Field by Hand
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+----------------------------
 
 The ``form_row`` helper is great because you can very quickly render each
 field of your form (and the markup used for the "row" can be customized as
@@ -179,7 +179,7 @@ the ``full_name`` value:
         <?php echo $form['task']->vars['full_name'] ?>
 
 Twig Template Function Reference
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+--------------------------------
 
 If you're using Twig, a full reference of the form rendering functions is
 available in the :doc:`reference manual </reference/forms/twig_reference>`.

form/validation_groups.rst

@@ -5,7 +5,7 @@ How to Define the Validation Groups to Use
 ==========================================
 
 Validation Groups
-~~~~~~~~~~~~~~~~~
+-----------------
 
 If your object takes advantage of :doc:`validation groups </validation/groups>`,
 you'll need to specify which validation group(s) your form should use::

form/without_class.rst

@@ -63,7 +63,7 @@ an array.
 .. _booking-validation-forms:
 
 Adding Validation
-~~~~~~~~~~~~~~~~~
+-----------------
 
 The only missing piece is validation. Usually, when you call ``$form->isValid()``,
 the object is validated by reading the constraints that you applied to that