Merge branch '6.1' into 6.2

* 6.1:
  docs: Add the mime type in the example
  [IntegerType] fix rounding_mode default value
  Minor (language) improvements
  [Messenger] Removing note docblock for MessageHandlerInterface

Author: javiereguiluz

forms.rst

@@ -872,13 +872,13 @@ Form Type Guessing
 ~~~~~~~~~~~~~~~~~~
 
 If the object handled by the form includes validation constraints, Symfony can
-introspect that metadata to guess the type of your field and set it up for you.
-In the above example, Symfony can guess from the validation rules that both the
+introspect that metadata to guess the type of your field.
+In the above example, Symfony can guess from the validation rules that the
 ``task`` field is a normal ``TextType`` field and the ``dueDate`` field is a
 ``DateType`` field.
 
-When building the form, omit the second argument to the ``add()`` method, or
-pass ``null`` to it, to enable Symfony's "guessing mechanism"::
+To enable Symfony's "guessing mechanism", omit the second argument to the ``add()`` method, or
+pass ``null`` to it::
 
     // src/Form/Type/TaskType.php
     namespace App\Form\Type;
@@ -913,23 +913,21 @@ pass ``null`` to it, to enable Symfony's "guessing mechanism"::
 Form Type Options Guessing
 ..........................
 
-When the guessing mechanism is enabled for some field (i.e. you omit or pass
-``null`` as the second argument to ``add()``), in addition to its form type,
-the following options can be guessed too:
+When the guessing mechanism is enabled for some field, in addition to its form type,
+the following options will be guessed too:
 
 ``required``
-    The ``required`` option can be guessed based on the validation rules (i.e. is
+    The ``required`` option is guessed based on the validation rules (i.e. is
     the field ``NotBlank`` or ``NotNull``) or the Doctrine metadata (i.e. is the
     field ``nullable``). This is very useful, as your client-side validation will
     automatically match your validation rules.
 
 ``maxlength``
     If the field is some sort of text field, then the ``maxlength`` option attribute
-    can be guessed from the validation constraints (if ``Length`` or ``Range`` is used)
+    is guessed from the validation constraints (if ``Length`` or ``Range`` is used)
     or from the :doc:`Doctrine </doctrine>` metadata (via the field's length).
 
-If you'd like to change one of the guessed values, override it by passing the
-option in the options field array::
+If you'd like to change one of the guessed values, override it in the options field array::
 
     ->add('task', null, ['attr' => ['maxlength' => 4]])
 

mailer.rst

@@ -478,9 +478,9 @@ file or stream::
     $email = (new Email())
         // ...
         // get the image contents from a PHP resource
-        ->embed(fopen('/path/to/images/logo.png', 'r'), 'logo')
+        ->embed(fopen('/path/to/images/logo.png', 'r'), 'logo', 'image/png')
         // get the image contents from an existing file
-        ->embedFromPath('/path/to/images/signature.gif', 'footer-signature')
+        ->embedFromPath('/path/to/images/signature.gif', 'footer-signature', 'image/gif')
     ;
 
 The second optional argument of both methods is the image name ("Content-ID" in
@@ -489,8 +489,8 @@ images inside the HTML contents::
 
     $email = (new Email())
         // ...
-        ->embed(fopen('/path/to/images/logo.png', 'r'), 'logo')
-        ->embedFromPath('/path/to/images/signature.gif', 'footer-signature')
+        ->embed(fopen('/path/to/images/logo.png', 'r'), 'logo', 'image/png')
+        ->embedFromPath('/path/to/images/signature.gif', 'footer-signature', 'image/gif')
 
         // reference images using the syntax 'cid:' + "image embed name"
         ->html('<img src="cid:logo"> ... <img src="cid:footer-signature"> ...')

messenger.rst

@@ -70,12 +70,6 @@ message class (or a message interface)::
         }
     }
 
-.. note::
-
-    You can also create a class without the attribute (e.g. if you're
-    using PHP 7.4), by implementing :class:`Symfony\\Component\\Messenger\\Handler\\MessageHandlerInterface`
-    instead.
-
 .. tip::
 
     You can also use the ``#[AsMessageHandler]`` attribute on individual class

reference/forms/types/integer.rst

@@ -35,7 +35,7 @@ Field Options
 ``rounding_mode``
 ~~~~~~~~~~~~~~~~~
 
-**type**: ``integer`` **default**: ``\NumberFormatter::ROUND_HALFUP``
+**type**: ``integer`` **default**: ``\NumberFormatter::ROUND_DOWN``
 
 By default, if the user enters a non-integer number, it will be rounded
 down. You have several configurable options for that rounding. Each option