Merge branch '7.0' into 7.1

* 7.0:
  -
  use option name as link label

Author: OskarStark

bundles/configuration.rst

@@ -61,10 +61,6 @@ There are two different ways of creating friendly configuration for a bundle:
 Using the AbstractBundle Class
 ------------------------------
 
-.. versionadded:: 6.1
-
-    The ``AbstractBundle`` class was introduced in Symfony 6.1.
-
 In bundles extending the :class:`Symfony\\Component\\HttpKernel\\Bundle\\AbstractBundle`
 class, you can add all the logic related to processing the configuration in that class::
 

bundles/extension.rst

@@ -20,10 +20,6 @@ There are two different ways of doing it:
 Loading Services Directly in your Bundle Class
 ----------------------------------------------
 
-.. versionadded:: 6.1
-
-    The ``AbstractBundle`` class was introduced in Symfony 6.1.
-
 In bundles extending the :class:`Symfony\\Component\\HttpKernel\\Bundle\\AbstractBundle`
 class, you can define the :method:`Symfony\\Component\\HttpKernel\\Bundle\\AbstractBundle::loadExtension`
 method to load service definitions from configuration files::

forms.rst

@@ -773,7 +773,7 @@ to the ``form()`` or the ``form_start()`` helper functions:
     that stores this method. The form will be submitted in a normal ``POST``
     request, but :doc:`Symfony's routing </routing>` is capable of detecting the
     ``_method`` parameter and will interpret it as a ``PUT``, ``PATCH`` or
-    ``DELETE`` request. The :ref:`configuration-framework-http_method_override`
+    ``DELETE`` request. The :ref:`http_method_override <configuration-framework-http_method_override>`
     option must be enabled for this to work.
 
 Changing the Form Name