Merge branch '4.4' into 5.1

* 4.4:
  fix link to `ChainAdapter::prune` method
  [Messenger] rename message recorder file
  [PropertyAccess] Backport typed property support to 4.4
  Fix minor typo

_build/redirection_map

@@ -508,3 +508,4 @@
 /frontend/encore/versus-assetic /frontend
 /components/http_client /http_client
 /components/mailer /mailer
+/messenger/message-recorder messenger/dispatch_after_current_bus

components/cache/adapters/chain_adapter.rst

@@ -44,7 +44,7 @@ slowest storage engines, :class:`Symfony\\Component\\Cache\\Adapter\\ApcuAdapter
         new FilesystemAdapter(),
     ]);
 
-When calling this adapter's :method:`Symfony\\Component\\Cache\\ChainAdapter::prune` method,
+When calling this adapter's :method:`Symfony\\Component\\Cache\\Adapter\\ChainAdapter::prune` method,
 the call is delegated to all its compatible cache adapters. It is safe to mix both adapters
 that *do* and do *not* implement :class:`Symfony\\Component\\Cache\\PruneableInterface`, as
 incompatible adapters are silently ignored::

components/property_info.rst

@@ -293,9 +293,9 @@ string values: ``array``, ``bool``, ``callable``, ``float``, ``int``,
 Constants inside the :class:`Symfony\\Component\\PropertyInfo\\Type`
 class, in the form ``Type::BUILTIN_TYPE_*``, are provided for convenience.
 
-.. versionadded:: 5.1
+.. versionadded:: 4.4
 
-    Support for typed properties (added in PHP 7.4) was introduced in Symfony 5.1.
+    Support for typed properties (added in PHP 7.4) was introduced in Symfony 4.4.
 
 ``Type::isNullable()``
 ~~~~~~~~~~~~~~~~~~~~~~

messenger.rst

@@ -1491,7 +1491,7 @@ for each bus looks like this:
 #. ``add_bus_name_stamp_middleware`` - adds a stamp to record which bus this
    message was dispatched into;
 
-#. ``dispatch_after_current_bus``- see :doc:`/messenger/message-recorder`;
+#. ``dispatch_after_current_bus``- see :doc:`/messenger/dispatch_after_current_bus`;
 
 #. ``failed_message_processing_middleware`` - processes messages that are being
    retried via the :ref:`failure transport <messenger-failure-transport>` to make

migration.rst

@@ -188,7 +188,7 @@ that different paths were handled by different PHP files.
 In any case you have to create a ``public/index.php`` that will start
 your Symfony application by either copying the file from the
 ``FrameworkBundle``-recipe or by using Flex and requiring the
-FrameworkBundle. You will also likely have to update you web server
+FrameworkBundle. You will also likely have to update your web server
 (e.g. Apache or nginx) to always use this front controller. You can
 look at :doc:`Web Server Configuration </setup/web_server_configuration>`
 for examples on how this might look. For example when using Apache you can