symfony · wouterj · Jul 31, 2015 · Jul 31, 2015
diff --git a/book/forms.rst b/book/forms.rst
@@ -122,10 +122,6 @@ other things, determines which HTML form tag(s) is rendered for that field.
 Finally, you added a submit button with a custom label for submitting the form to
 the server.
 
-.. versionadded:: 2.3
-    Support for submit buttons was introduced in Symfony 2.3. Before that, you had
-    to add buttons to the form's HTML manually.
-
 Symfony comes with many built-in types that will be discussed shortly
 (see :ref:`book-forms-type-reference`).
 
@@ -240,12 +236,6 @@ controller::
         // ...
     }
 
-.. versionadded:: 2.3
-    The :method:`Symfony\\Component\\Form\\FormInterface::handleRequest` method
-    was introduced in Symfony 2.3. Previously, the ``$request`` was passed
-    to the ``submit`` method - a strategy which is deprecated and will be
-    removed in Symfony 3.0. For details on that method, see :ref:`cookbook-form-submit-request`.
-
 This controller follows a common pattern for handling forms, and has three
 possible paths:
 
@@ -294,9 +284,6 @@ possible paths:
 Submitting Forms with Multiple Buttons
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.3
-    Support for buttons in forms was introduced in Symfony 2.3.
-
 When your form contains more than one submit button, you will want to check
 which of the buttons was clicked to adapt the program flow in your controller.
 To do this, add a second button with the caption "Save and add" to your form::
@@ -470,10 +457,6 @@ you'll need to specify which validation group(s) your form should use::
         'validation_groups' => array('registration'),
     ))->add(...);
 
-.. versionadded:: 2.7
-    The ``configureOptions()`` method was introduced in Symfony 2.7. Previously,
-    the method was called ``setDefaultOptions()``.
-
 If you're creating :ref:`form classes <book-form-creating-form-classes>` (a
 good practice), then you'll need to add the following to the ``configureOptions()``
 method::
@@ -496,9 +479,6 @@ be used to validate the underlying object.
 Disabling Validation
 ~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.3
-    The ability to set ``validation_groups`` to false was introduced in Symfony 2.3.
-
 Sometimes it is useful to suppress the validation of a form altogether. For
 these cases you can set the ``validation_groups`` option to ``false``::
 
@@ -599,9 +579,6 @@ work in the book section about :ref:`validation groups <book-validation-validati
 Groups based on the Clicked Button
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.3
-    Support for buttons in forms was introduced in Symfony 2.3.
-
 When your form contains multiple submit buttons, you can change the validation
 group depending on which button is used to submit the form. For example,
 consider a form in a wizard that lets you advance to the next step or go back

diff --git a/book/templating.rst b/book/templating.rst
@@ -579,10 +579,6 @@ you set `with_context`_ to false).
     maps (i.e. an array with named keys). If you needed to pass in multiple
     elements, it would look like this: ``{'foo': foo, 'bar': bar}``.
 
-.. versionadded:: 2.3
-    The `include() function`_ is a new Twig feature that's available in Symfony
-    2.3. Prior, the `{% include %} tag`_ tag was used.
-
 .. index::
    single: Templating; Embedding action
 

diff --git a/book/testing.rst b/book/testing.rst
@@ -424,11 +424,6 @@ The Client supports many operations that can be done in a real browser::
 Accessing Internal Objects
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.3
-    The :method:`Symfony\\Component\\BrowserKit\\Client::getInternalRequest`
-    and :method:`Symfony\\Component\\BrowserKit\\Client::getInternalResponse`
-    methods were introduced in Symfony 2.3.
-
 If you use the client to test your application, you might want to access the
 client's internal objects::
 

diff --git a/book/validation.rst b/book/validation.rst
@@ -103,11 +103,6 @@ following:
     Protected and private properties can also be validated, as well as "getter"
     methods (see :ref:`validator-constraint-targets`).
 
-.. versionadded:: 2.7
-    As of Symfony 2.7, XML and Yaml constraint files located in the
-    ``Resources/config/validation`` sub-directory of a bundle are loaded. Prior
-    to 2.7, only ``Resources/config/validation.yml`` (or ``.xml``) were loaded.
-
 .. index::
    single: Validation; Using the validator
 

diff --git a/components/class_loader/debug_class_loader.rst b/components/class_loader/debug_class_loader.rst
diff --git a/components/class_loader/index.rst b/components/class_loader/index.rst
@@ -10,8 +10,3 @@ ClassLoader
     map_class_loader
     cache_class_loader
     class_map_generator
-
-.. toctree::
-    :hidden:
-
-    debug_class_loader
diff --git a/components/console/events.rst b/components/console/events.rst
@@ -4,9 +4,6 @@
 Using Events
 ============
 
-.. versionadded:: 2.3
-    Console events were introduced in Symfony 2.3.
-
 The Application class of the Console component allows you to optionally hook
 into the lifecycle of a console application via events. Instead of reinventing
 the wheel, it uses the Symfony EventDispatcher component to do the work::