code style standardization on form type options

Author: Adam Szaraniec

reference/configuration/framework.rst

@@ -72,7 +72,7 @@ http_method_override
 .. versionadded:: 2.3
     The ``http_method_override`` option was introduced in Symfony 2.3.
 
-**type**: ``Boolean`` **default**: ``true``
+**type**: ``boolean`` **default**: ``true``
 
 This determines whether the ``_method`` request parameter is used as the intended
 HTTP method on POST requests. If enabled, the
@@ -143,7 +143,7 @@ is set, then the ``ide`` option will be ignored.
 test
 ~~~~
 
-**type**: ``Boolean``
+**type**: ``boolean``
 
 If this configuration parameter is present (and not ``false``), then the
 services related to testing your application (e.g. ``test.client``) are loaded.
@@ -251,14 +251,14 @@ to the cookie specification.
 cookie_secure
 .............
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 This determines whether cookies should only be sent over secure connections.
 
 cookie_httponly
 ...............
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 This determines whether cookies should only be accessible through the HTTP protocol.
 This means that the cookie won't be accessible by scripting languages, such
@@ -552,7 +552,7 @@ to implement the :class:`Symfony\\Component\\Validator\\Mapping\\Cache\\CacheInt
 enable_annotations
 ..................
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 If this option is enabled, validation constraints can be defined using annotations.
 

reference/configuration/security.rst

@@ -276,7 +276,7 @@ a separate firewall just for ``check_path`` URL).
 use_forward
 ...........
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 If you'd like the user to be forwarded to the login form instead of being
 redirected, set this option to ``true``.
@@ -302,7 +302,7 @@ will look for a POST parameter with this name.
 post_only
 .........
 
-**type**: ``Boolean`` **default**: ``true``
+**type**: ``boolean`` **default**: ``true``
 
 By default, you must submit your login form to the ``check_path`` URL as
 a POST request. By setting this option to ``false``, you can send a GET request
@@ -311,10 +311,10 @@ to the ``check_path`` URL.
 Redirecting after Login
 ~~~~~~~~~~~~~~~~~~~~~~~
 
-* ``always_use_default_target_path`` (type: ``Boolean``, default: ``false``)
+* ``always_use_default_target_path`` (type: ``boolean``, default: ``false``)
 * ``default_target_path`` (type: ``string``, default: ``/``)
 * ``target_path_parameter`` (type: ``string``, default: ``_target_path``)
-* ``use_referer`` (type: ``Boolean``, default: ``false``)
+* ``use_referer`` (type: ``boolean``, default: ``false``)
 
 .. _reference-security-pbkdf2:
 

reference/configuration/swiftmailer.rst

@@ -159,15 +159,15 @@ on the ``X-Swift-To``, ``X-Swift-Cc`` and ``X-Swift-Bcc`` headers.
 disable_delivery
 ~~~~~~~~~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 If true, the ``transport`` will automatically be set to ``null``, and no
 emails will actually be delivered.
 
 logging
 ~~~~~~~
 
-**type**: ``Boolean`` **default**: ``%kernel.debug%``
+**type**: ``boolean`` **default**: ``%kernel.debug%``
 
 If true, Symfony's data collector will be activated for Swift Mailer and the
 information will be available in the profiler.

reference/constraints/Choice.rst

@@ -281,7 +281,7 @@ for details on its usage.
 multiple
 ~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 If this option is true, the input value is expected to be an array instead
 of a single, scalar value. The constraint will check that each value of
@@ -344,7 +344,7 @@ too many options per the `max`_ option.
 strict
 ~~~~~~
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 If true, the validator will also check the type of the input value. Specifically,
 this value is passed to as the third argument to the PHP :phpfunction:`in_array` method

reference/constraints/Collection.rst

@@ -298,7 +298,7 @@ be executed against that element of the collection.
 allowExtraFields
 ~~~~~~~~~~~~~~~~
 
-**type**: ``Boolean`` **default**: false
+**type**: ``boolean`` **default**: false
 
 If this option is set to ``false`` and the underlying collection contains
 one or more elements that are not included in the `fields`_ option, a validation
@@ -307,14 +307,14 @@ error will be returned. If set to ``true``, extra fields are ok.
 extraFieldsMessage
 ~~~~~~~~~~~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``The fields {{ fields }} were not expected.``
+**type**: ``boolean`` **default**: ``The fields {{ fields }} were not expected.``
 
 The message shown if `allowExtraFields`_ is false and an extra field is detected.
 
 allowMissingFields
 ~~~~~~~~~~~~~~~~~~
 
-**type**: ``Boolean`` **default**: false
+**type**: ``boolean`` **default**: false
 
 If this option is set to ``false`` and one or more fields from the `fields`_
 option are not present in the underlying collection, a validation error will
@@ -324,7 +324,7 @@ option are not present in the underlying collection.
 missingFieldsMessage
 ~~~~~~~~~~~~~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``The fields {{ fields }} are missing.``
+**type**: ``boolean`` **default**: ``The fields {{ fields }} are missing.``
 
 The message shown if `allowMissingFields`_ is false and one or more fields
 are missing from the underlying collection.

reference/constraints/Email.rst

@@ -99,15 +99,15 @@ This message is shown if the underlying data is not a valid email address.
 checkMX
 ~~~~~~~
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 If true, then the :phpfunction:`checkdnsrr` PHP function will be used to
 check the validity of the MX record of the host of the given email.
 
 checkHost
 ~~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 If true, then the :phpfunction:`checkdnsrr` PHP function will be used to
 check the validity of the MX *or* the A *or* the AAAA record of the host

reference/constraints/Issn.rst

@@ -90,15 +90,15 @@ The message shown if the given value is not a valid ISSN.
 caseSensitive
 ~~~~~~~~~~~~~
 
-**type**: ``Boolean`` default: ``false``
+**type**: ``boolean`` default: ``false``
 
 The validator will allow ISSN values to end with a lower case 'x' by default.
 When switching this to ``true``, the validator requires an upper case 'X'.
 
 requireHyphen
 ~~~~~~~~~~~~~
 
-**type**: ``Boolean`` default: ``false``
+**type**: ``boolean`` default: ``false``
 
 The validator will allow non hyphenated ISSN values by default. When switching
 this to ``true``, the validator requires a hyphenated ISSN value.

reference/constraints/Regex.rst

@@ -264,7 +264,7 @@ Setting ``htmlPattern`` to false will disable client side validation.
 match
 ~~~~~
 
-**type**: ``Boolean`` default: ``true``
+**type**: ``boolean`` default: ``true``
 
 If ``true`` (or not set), this validator will pass if the given string matches
 the given `pattern`_ regular expression. However, when this option is set

reference/constraints/UniqueEntity.rst

@@ -257,7 +257,7 @@ Now, the message would be bound to the ``port`` field with this configuration.
 ignoreNull
 ~~~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``true``
+**type**: ``boolean`` **default**: ``true``
 
 .. versionadded:: 2.1
     The ``ignoreNull`` option was introduced in Symfony 2.1.

reference/forms/types/choice.rst

@@ -192,9 +192,9 @@ Field Variables
 +------------------------+--------------+-------------------------------------------------------------------+
 | Variable               | Type         | Usage                                                             |
 +========================+==============+===================================================================+
-| multiple               | ``Boolean``  | The value of the `multiple`_ option.                              |
+| multiple               | ``boolean``  | The value of the `multiple`_ option.                              |
 +------------------------+--------------+-------------------------------------------------------------------+
-| expanded               | ``Boolean``  | The value of the `expanded`_ option.                              |
+| expanded               | ``boolean``  | The value of the `expanded`_ option.                              |
 +------------------------+--------------+-------------------------------------------------------------------+
 | preferred_choices      | ``array``    | A nested array containing the ``ChoiceView`` objects of           |
 |                        |              | choices which should be presented to the user with priority.      |
@@ -210,7 +210,7 @@ Field Variables
 | is_selected            | ``callable`` | A callable which takes a ``ChoiceView`` and the selected value(s) |
 |                        |              | and returns whether the choice is in the selected value(s).       |
 +------------------------+--------------+-------------------------------------------------------------------+
-| empty_value_in_choices | ``Boolean``  | Whether the empty value is in the choice list.                    |
+| empty_value_in_choices | ``boolean``  | Whether the empty value is in the choice list.                    |
 +------------------------+--------------+-------------------------------------------------------------------+
 
 .. tip::

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

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

@@ -1,7 +1,7 @@
 expanded
 ~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 If set to true, radio buttons or checkboxes will be rendered (depending
 on the ``multiple`` value). If false, a select element will be rendered.

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

@@ -1,7 +1,7 @@
 multiple
 ~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 If true, the user will be able to select multiple options (as opposed
 to choosing just one option). Depending on the value of the ``expanded``

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

@@ -1,7 +1,7 @@
 read_only
 ~~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``false``
+**type**: ``boolean`` **default**: ``false``
 
 If this option is true, the field will be rendered with the ``readonly``
 attribute so that the field is not editable.

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

@@ -1,7 +1,7 @@
 required
 ~~~~~~~~
 
-**type**: ``Boolean`` **default**: ``true``
+**type**: ``boolean`` **default**: ``true``
 
 If true, an `HTML5 required attribute`_ will be rendered. The corresponding
 ``label`` will also render with a ``required`` class.

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

@@ -1,7 +1,7 @@
 trim
 ~~~~
 
-**type**: ``Boolean`` **default**: ``true``
+**type**: ``boolean`` **default**: ``true``
 
 If true, the whitespace of the submitted string value will be stripped
 via the ``trim()`` function when the data is bound. This guarantees that