use boolean instead of Boolean

Author: Christian Flothmann

book/forms.rst

@@ -198,7 +198,7 @@ it into a format that's suitable for being rendered in an HTML form.
    ``task`` property via the ``getTask()`` and ``setTask()`` methods on the
    ``Task`` class. Unless a property is public, it *must* have a "getter" and
    "setter" method so that the Form component can get and put data onto the
-   property. For a Boolean property, you can use an "isser" or "hasser" method
+   property. For a boolean property, you can use an "isser" or "hasser" method
    (e.g. ``isPublished()`` or ``hasReminder()``) instead of a getter (e.g.
    ``getPublished()`` or ``getReminder()``).
 

components/yaml/yaml_format.rst

@@ -119,7 +119,7 @@ Nulls in YAML can be expressed with ``null`` or ``~``.
 Booleans
 ~~~~~~~~
 
-Booleans in YAML are expressed with ``true`` and ``false``.
+booleans in YAML are expressed with ``true`` and ``false``.
 
 Dates
 ~~~~~

contributing/code/standards.rst

@@ -79,7 +79,7 @@ example containing most features described below:
 
             throw new \RuntimeException(sprintf('Unrecognized dummy option "%s"', $dummy));
         }
-        
+
         private function reverseBoolean($value = null, $theSwitch = false)
         {
             if (!$theSwitch) {
@@ -95,7 +95,7 @@ Structure
 
 * Add a single space after each comma delimiter;
 
-* Add a single space around binary operators (``==``, ``&&``, ...), with 
+* Add a single space around binary operators (``==``, ``&&``, ...), with
   the exception of the concatenation (``.``) operator;
 
 * Place unary operators (``!``, ``--``, ...) adjacent to the affected variable;

cookbook/configuration/using_parameters_in_dic.rst

@@ -105,7 +105,7 @@ be injected with this parameter via the extension as follows::
 
         public function  __construct($debug)
         {
-            $this->debug = (Boolean) $debug;
+            $this->debug = (bool) $debug;
         }
 
         public function getConfigTreeBuilder()

cookbook/doctrine/registration_form.rst

@@ -194,7 +194,7 @@ Start by creating a simple class which represents the "registration"::
 
         public function setTermsAccepted($termsAccepted)
         {
-            $this->termsAccepted = (Boolean) $termsAccepted;
+            $this->termsAccepted = (bool) $termsAccepted;
         }
     }
 

cookbook/security/voters_data_permission.rst

@@ -121,7 +121,7 @@ edit a particular object. Here's an example implementation::
             switch($attribute) {
                 case self::VIEW:
                     // the data object could have for example a method isPrivate()
-                    // which checks the Boolean attribute $private
+                    // which checks the boolean attribute $private
                     if (!$post->isPrivate()) {
                         return VoterInterface::ACCESS_GRANTED;
                     }

reference/configuration/framework.rst

@@ -67,7 +67,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
@@ -138,7 +138,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.
@@ -235,14 +235,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

reference/configuration/security.rst

@@ -265,7 +265,7 @@ The Login Form and Process
     Be sure that this URL is covered by your main firewall (i.e. don't create
     a separate firewall just for ``check_path`` URL).
 
-*   ``use_forward`` (type: ``Boolean``, default: ``false``)
+*   ``use_forward`` (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``.
 
@@ -279,18 +279,18 @@ The Login Form and Process
     your login form. When you submit the form to ``check_path``, the security
     system will look for a POST parameter with this name.
 
-*   ``post_only`` (type: ``Boolean``, default: ``true``)
+*   ``post_only`` (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 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

@@ -89,11 +89,11 @@ If your valid choice list is simple, you can pass them in directly via the
 
         use Symfony\Component\Validator\Mapping\ClassMetadata;
         use Symfony\Component\Validator\Constraints as Assert;
-        
+
         class Author
         {
             protected $gender;
-            
+
             public static function loadValidatorMetadata(ClassMetadata $metadata)
             {
                 $metadata->addPropertyConstraint('gender', new Assert\Choice(array(
@@ -176,11 +176,11 @@ constraint.
 
         use Symfony\Component\Validator\Mapping\ClassMetadata;
         use Symfony\Component\Validator\Constraints as Assert;
-        
+
         class Author
         {
             protected $gender;
-            
+
             public static function loadValidatorMetadata(ClassMetadata $metadata)
             {
                 $metadata->addPropertyConstraint('gender', new Assert\Choice(array(
@@ -244,11 +244,11 @@ you can pass the class name and the method as an array.
 
         use Symfony\Component\Validator\Mapping\ClassMetadata;
         use Symfony\Component\Validator\Constraints as Assert;
-        
+
         class Author
         {
             protected $gender;
-            
+
             public static function loadValidatorMetadata(ClassMetadata $metadata)
             {
                 $metadata->addPropertyConstraint('gender', new Assert\Choice(array(
@@ -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