minor #12208 Use Symfony 5 examples (OskarStark)

This PR was merged into the master branch.

Discussion
----------

Use Symfony 5 examples

<!--

If your pull request fixes a BUG, use the oldest maintained branch that contains
the bug (see https://symfony.com/roadmap for the list of maintained branches).

If your pull request documents a NEW FEATURE, use the same Symfony branch where
the feature was introduced (and `master` for features of unreleased versions).

-->

Commits
-------

ffbc179 Use Symfony 5 examples

Author: OskarStark

contributing/documentation/format.rst

@@ -175,14 +175,14 @@ If you are documenting a brand new feature, a change or a deprecation that's
 been made in Symfony, you should precede your description of the change with
 the corresponding directive and a short description:
 
-For a new feature or a behavior change use the ``.. versionadded:: 4.x``
+For a new feature or a behavior change use the ``.. versionadded:: 5.x``
 directive:
 
 .. code-block:: rst
 
-    .. versionadded:: 4.2
+    .. versionadded:: 5.2
 
-        Named autowiring aliases have been introduced in Symfony 4.2.
+        ... ... ... was introduced in Symfony 5.2.
 
 If you are documenting a behavior change, it may be helpful to *briefly*
 describe how the behavior has changed:
@@ -191,23 +191,23 @@ describe how the behavior has changed:
 
     .. versionadded:: 4.2
 
-       Support for ICU MessageFormat was introduced in Symfony 4.2. Prior to this,
-       pluralization was managed by the ``transChoice`` method.
+       ... ... ... was introduced in Symfony 5.2. Prior to this,
+       ... ... ... ... ... ... ... ... .
 
-For a deprecation use the ``.. deprecated:: 4.x`` directive:
+For a deprecation use the ``.. deprecated:: 5.x`` directive:
 
 .. code-block:: rst
 
-    .. deprecated:: 4.2
+    .. deprecated:: 5.2
 
-        Not passing the root node name to ``TreeBuilder`` was deprecated in Symfony 4.2.
+        ... ... ... was deprecated in Symfony 5.2.
 
-Whenever a new major version of Symfony is released (e.g. 5.0, 6.0, etc),
+Whenever a new major version of Symfony is released (e.g. 6.0, 7.0, etc),
 a new branch of the documentation is created from the ``master`` branch.
 At this point, all the ``versionadded`` and ``deprecated`` tags for Symfony
 versions that have a lower major version will be removed. For example, if
-Symfony 5.0 were released today, 4.0 to 4.4 ``versionadded`` and ``deprecated``
-tags would be removed from the new ``5.0`` branch.
+Symfony 6.0 were released today, 5.0 to 5.4 ``versionadded`` and ``deprecated``
+tags would be removed from the new ``6.0`` branch.
 
 .. _reStructuredText: http://docutils.sourceforge.net/rst.html
 .. _Sphinx: https://www.sphinx-doc.org/