Removed versionadded/changed annotations for 1.6.

docs/topics/http/middleware.txt

@@ -8,8 +8,8 @@ or output.
 
 Each middleware component is responsible for doing some specific function. For
 example, Django includes a middleware component,
-:class:`~django.middleware.transaction.TransactionMiddleware`, that wraps the
-processing of each HTTP request in a database transaction.
+:class:`~django.contrib.auth.middleware.AuthenticationMiddleware`, that
+associates users with requests using sessions.
 
 This document explains how middleware works, how you activate middleware, and
 how to write your own middleware. Django ships with some built-in middleware

docs/topics/http/sessions.txt

@@ -324,8 +324,6 @@ You can edit it multiple times.
 Session serialization
 ---------------------
 
-.. versionchanged:: 1.6
-
 Before version 1.6, Django defaulted to using :mod:`pickle` to serialize
 session data before storing it in the backend. If you're using the :ref:`signed
 cookie session backend<cookie-session-backend>` and :setting:`SECRET_KEY` is

docs/topics/http/views.txt

@@ -242,8 +242,6 @@ same way you can for the 404 and 500 views by specifying a
 The 400 (bad request) view
 --------------------------
 
-.. versionadded:: 1.6
-
 .. function:: django.views.defaults.bad_request(request, template_name='400.html')
 
 When a :exc:`~django.core.exceptions.SuspiciousOperation` is raised in Django,