Merge branch '4.3' into 4.4

* 4.3:
  Update messenger.rst
  Update input.rst
  Update configuration.rst

Author: OskarStark

configuration.rst

@@ -321,7 +321,7 @@ a new ``locale`` parameter is added to the ``config/services.yaml`` file).
 .. seealso::
 
     Later in this article you can read how to
-    ref:`get configuration parameters in controllers and services <configuration-accessing-parameters>`.
+    :ref:`get configuration parameters in controllers and services <configuration-accessing-parameters>`.
 
 .. index::
    single: Environments; Introduction

console/input.rst

@@ -153,11 +153,11 @@ flag:
     Hi Fabien!
 
     $ php bin/console app:greet Fabien --iterations=5
-    Hi Fabien
-    Hi Fabien
-    Hi Fabien
-    Hi Fabien
-    Hi Fabien
+    Hi Fabien!
+    Hi Fabien!
+    Hi Fabien!
+    Hi Fabien!
+    Hi Fabien!
 
     # the order of options isn't important
     $ php bin/console app:greet Fabien --iterations=5 --yell

messenger.rst

@@ -50,8 +50,8 @@ serialized::
 
 .. _messenger-handler:
 
-A message handler is a PHP callable, the easiest way to create it is to create a class that implements
-``MessageHandlerInterface`` and has an ``__invoke()`` method that's
+A message handler is a PHP callable, the recommended way to create it is to create a class that
+implements ``MessageHandlerInterface`` and has an ``__invoke()`` method that's
 type-hinted with the message class (or a message interface)::
 
     // src/MessageHandler/SmsNotificationHandler.php
@@ -936,7 +936,7 @@ In Memory Transport
 
     The ``in-memory`` transport was introduced in Symfony 4.3.
 
-The ``in-memory`` transport does not actually delivery messages. Instead, it
+The ``in-memory`` transport does not actually deliver messages. Instead, it
 holds them in memory during the request, which can be useful for testing.
 For example, if you have an ``async_priority_normal`` transport, you could
 override it in the ``test`` environment to use this transport:
@@ -1298,7 +1298,7 @@ Middleware
 ~~~~~~~~~~
 
 What happens when you dispatch a message to a message bus depends on its
-collection of middleware (and their order). By default, the middleware configured
+collection of middleware and their order. By default, the middleware configured
 for each bus looks like this:
 
 #. ``add_bus_name_stamp_middleware`` - adds a stamp to record which bus this