code style standardization on form type options

Author: Adam Szaraniec

reference/forms/types/collection.rst

@@ -214,7 +214,7 @@ Field Options
 allow_add
 ~~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 If set to ``true``, then if unrecognized items are submitted to the collection,
 they will be added as new items. The ending array will contain the existing
@@ -235,7 +235,7 @@ client side. For more information, see the above example and :ref:`cookbook-form
 allow_delete
 ~~~~~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 If set to ``true``, then if an existing item is not contained in the submitted
 data, it will be correctly absent from the final array of items. This means
@@ -280,7 +280,7 @@ you'd need to at least pass the ``choices`` option to the underlying type::
 prototype
 ~~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``true``
+**type**: ``boolean`` **default**: ``true``
 
 This option is useful when using the `allow_add`_ option. If ``true`` (and
 if `allow_add`_ is also ``true``), a special "prototype" attribute will be
@@ -319,7 +319,7 @@ as :ref:`cookbook-form-collections-new-prototype`.
 prototype_name
 ~~~~~~~~~~~~~~
 
-**type**: ``String`` **default**: ``__name__``
+**type**: ``string`` **default**: ``__name__``
 
 If you have several collections in your form, or worse, nested collections
 you may want to change the placeholder so that unrelated placeholders are not
@@ -359,7 +359,7 @@ The default value is ``array()`` (empty array).
 error_bubbling
 ~~~~~~~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``true``
+**type**: ``boolean`` **default**: ``true``
 
 .. include:: /reference/forms/types/options/_error_bubbling_body.rst.inc
 
@@ -379,6 +379,6 @@ Field Variables
 ============  ===========  ========================================
 Variable      Type         Usage
 ============  ===========  ========================================
-allow_add     ``Boolean``  The value of the `allow_add`_ option.
-allow_delete  ``Boolean``  The value of the `allow_delete`_ option.
+allow_add     ``boolean``  The value of the `allow_add`_ option.
+allow_delete  ``boolean``  The value of the `allow_delete`_ option.
 ============  ===========  ========================================

reference/forms/types/entity.rst

@@ -183,7 +183,7 @@ directly.
 choices
 ~~~~~~~
 
-**type**:  array | ``\Traversable`` **default**: ``null``
+**type**:  ``array`` | ``\Traversable`` **default**: ``null``
 
 Instead of allowing the `class`_ and `query_builder`_ options to fetch the
 entities to include for you, you can pass the ``choices`` option directly.

reference/forms/types/options/attr.rst.inc

@@ -1,7 +1,7 @@
 attr
 ~~~~
 
-**type**: array **default**: Empty array
+**type**: ``array`` **default**: ``array()``
 
 If you want to add extra attributes to an HTML field representation
 you can use the ``attr`` option. It's an associative array with HTML attributes

reference/forms/types/options/button_attr.rst.inc

@@ -1,7 +1,7 @@
 attr
 ~~~~
 
-**type**: array **default**: Empty array
+**type**: ``array`` **default**: ``array()``
 
 If you want to add extra attributes to the HTML representation of the button,
 you can use ``attr`` option. It's an associative array with HTML attribute

reference/forms/types/options/by_reference.rst.inc

@@ -1,7 +1,7 @@
 by_reference
 ~~~~~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``true``
+**type**: ``boolean`` **default**: ``true``
 
 In most cases, if you have a ``name`` field, then you expect ``setName()``
 to be called on the underlying object. In some cases, however, ``setName()``

reference/forms/types/options/cascade_validation.rst.inc

@@ -1,7 +1,7 @@
 cascade_validation
 ~~~~~~~~~~~~~~~~~~
 
-**type**: Boolean **default**: false
+**type**: ``boolean`` **default**: ``false``
 
 Set this option to ``true`` to force validation on embedded form types.
 For example, if you have a ``ProductType`` with an embedded ``CategoryType``,

reference/forms/types/options/constraints.rst.inc

@@ -1,7 +1,7 @@
 constraints
 ~~~~~~~~~~~
 
-**type**: array or :class:`Symfony\\Component\\Validator\\Constraint` **default**: ``null``
+**type**: ``array`` or :class:`Symfony\\Component\\Validator\\Constraint` **default**: ``null``
 
 Allows you to attach one or more validation constraints to a specific field.
 For more information, see :ref:`Adding Validation<form-option-constraints>`.

reference/forms/types/options/data.rst.inc

@@ -1,7 +1,7 @@
 data
 ~~~~
 
-**type**: mixed **default**: Defaults to field of the underlying object (if there is one)
+**type**: ``mixed`` **default**: Defaults to field of the underlying object (if there is one)
 
 When you create a form, each field initially displays the value of the
 corresponding property of the form's domain object (if an object is bound

reference/forms/types/options/empty_value.rst.inc

@@ -5,7 +5,7 @@ empty_value
     Since Symfony 2.3, empty values are also supported if the ``expanded``
     option is set to true.
 
-**type**: ``string`` or ``Boolean``
+**type**: ``string`` or ``boolean``
 
 This option determines whether or not a special "empty" option (e.g. "Choose an option")
 will appear at the top of a select widget. This option only applies if the

reference/forms/types/options/error_bubbling.rst.inc

@@ -1,6 +1,6 @@
 error_bubbling
 ~~~~~~~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``false`` unless the form is ``compound``
+**type**: ``boolean`` **default**: ``false`` unless the form is ``compound``
 
 .. include:: /reference/forms/types/options/_error_bubbling_body.rst.inc