Fixed #16863 -- Corrected ReST markup to avoid errors building docs.

Although directives such as "note" and "warning" will accept content
immediately following the directive, this is technically where arguments to the
directive should go (see http://sphinx.pocoo.org/rest.html#directives). Putting
the content there means that any lines beginning with an inline text role
(e.g. ":setting:`DEBUG`") will be mis-interpreted as an option block for the
directive. To avoid this error, there should always be a blank line between the
directive start and the directive content.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@16842 bcc190cf-cafb-0310-a4f2-bffc1f526a37

docs/topics/http/middleware.txt

@@ -98,13 +98,13 @@ view; it'll return that :class:`~django.http.HttpResponse`. Response
 middleware is always called on every response.
 
 .. note::
-    Accessing :attr:`request.POST <django.http.HttpRequest.POST>` or 
-    :attr:`request.REQUEST <django.http.HttpRequest.REQUEST>` inside 
-    middleware from ``process_request`` or ``process_view`` will prevent any
-    view running after the middleware from being able to
-    :ref:`modify the upload handlers for the 
-    request <modifying_upload_handlers_on_the_fly>`, and should normally be
-    avoided.
+
+    Accessing :attr:`request.POST <django.http.HttpRequest.POST>` or
+    :attr:`request.REQUEST <django.http.HttpRequest.REQUEST>` inside middleware
+    from ``process_request`` or ``process_view`` will prevent any view running
+    after the middleware from being able to :ref:`modify the upload handlers
+    for the request <modifying_upload_handlers_on_the_fly>`, and should
+    normally be avoided.
 
     The :class:`~django.middleware.csrf.CsrfViewMiddleware` class can be
     considered an exception, as it provides the