Remove reference to 2.x, 3.x, 4.x versions

components/browser_kit.rst

@@ -8,13 +8,6 @@ The BrowserKit Component
     The BrowserKit component simulates the behavior of a web browser, allowing
     you to make requests, click on links and submit forms programmatically.
 
-.. note::
-
-    In Symfony versions prior to 4.3, the BrowserKit component could only make
-    internal requests to your application. Starting from Symfony 4.3, this
-    component can also :ref:`make HTTP requests to any public site <component-browserkit-external-requests>`
-    when using it in combination with the :doc:`HttpClient component </http_client>`.
-
 Installation
 ------------
 

components/config/definition.rst

@@ -780,7 +780,7 @@ the following ways:
 - ``ifTrue()``
 - ``ifString()``
 - ``ifNull()``
-- ``ifEmpty()`` (since Symfony 3.2)
+- ``ifEmpty()``
 - ``ifArray()``
 - ``ifInArray()``
 - ``ifNotInArray()``

contributing/code/bc.rst

@@ -12,11 +12,6 @@ that release branch (5.x in the previous example).
 We also provide deprecation message triggered in the code base to help you with
 the migration process across major releases.
 
-.. caution::
-
-    This promise was introduced with Symfony 2.3 and does not apply to previous
-    versions of Symfony.
-
 However, backward compatibility comes in many different flavors. In fact, almost
 every change that we make to the framework can potentially break an application.
 For example, if we add a new method to a class, this will break an application

profiler.rst

@@ -110,16 +110,12 @@ need to create a custom data collector. Instead, use the built-in utilities to
     Consider using a professional profiler such as `Blackfire`_ to measure and
     analyze the execution of your application in detail.
 
-Enabling the Profiler Conditionally
------------------------------------
+.. _enabling-the-profiler-conditionally:
 
-.. caution::
-
-    The possibility to use a matcher to enable the profiler conditionally was
-    removed in Symfony 4.0.
+Enabling the Profiler Programmatically
+--------------------------------------
 
-Symfony Profiler cannot be enabled/disabled conditionally using matchers, because
-that feature was removed in Symfony 4.0. However, you can use the ``enable()``
+Symfony Profiler can be enabled and disabled programmatically. You can use the ``enable()``
 and ``disable()`` methods of the :class:`Symfony\\Component\\HttpKernel\\Profiler\\Profiler`
 class in your controllers to manage the profiler programmatically::
 

service_container.rst

@@ -1074,11 +1074,8 @@ unique string as the key of each service config:
 Explicitly Configuring Services and Arguments
 ---------------------------------------------
 
-Prior to Symfony 3.3, all services and (typically) arguments were explicitly configured:
-it was not possible to :ref:`load services automatically <service-container-services-load-example>`
-and :ref:`autowiring <services-autowire>` was much less common.
-
-Both of these features are optional. And even if you use them, there may be some
+:ref:`Loading services automatically <service-container-services-load-example>`
+and :ref:`autowiring <services-autowire>` are optional. And even if you use them, there may be some
 cases where you want to manually wire a service. For example, suppose that you want
 to register *2* services for the ``SiteUpdateManager`` class - each with a different
 admin email. In this case, each needs to have a unique service id: