removed more obsolete versionadded directives

Author: OskarStark

configuration/external_parameters.rst

@@ -12,10 +12,6 @@ example. The flexibility of the Symfony service container allows you to do this.
 Environment Variables
 ---------------------
 
-.. versionadded:: 3.2
-
-    ``env()`` parameters were introduced in Symfony 3.2.
-
 You can reference environment variables by using special parameters named after
 the variables you want to use enclosed between ``env()``. Their actual values
 will be resolved at runtime (once per request), so that dumped containers can be
@@ -122,13 +118,6 @@ of the following:
 
 .. tip::
 
-    .. versionadded:: 3.3
-
-        The support of the special ``SYMFONY__`` environment variables was
-        deprecated in Symfony 3.3 and it will be removed in 4.0. Instead of
-        using those variables, define regular environment variables and get
-        their values using the ``%env(...)%`` syntax in your config files.
-
     You can also define the default value of any existing parameters using
     special environment variables named after their corresponding parameter
     prefixed with ``SYMFONY__`` after replacing dots by double underscores

form/unit_testing.rst

@@ -218,8 +218,3 @@ guessers using the :method:`Symfony\\Component\\Form\\Test\\FormIntegrationTestC
 :method:`Symfony\\Component\\Form\\Test\\FormIntegrationTestCase::getTypeExtensions`
 and :method:`Symfony\\Component\\Form\\Test\\FormIntegrationTestCase::getTypeGuessers`
 methods.
-
-.. versionadded:: 3.3
-
-    The ``getTypes()``, ``getTypeExtensions()`` and ``getTypeGuessers()``
-    methods were introduced in Symfony 3.3.