move descriptions of ac_(in|out)_buffer_size to the right place

http://bugs.python.org/issue1053

Doc/library/asynchat.rst

@@ -36,6 +36,19 @@ connection requests.
    :class:`async_chat` object's methods are called by the event-processing
    framework with no action on the part of the programmer.
 
+   Two class attributes can be modified, to improve performance, or possibly
+   even to conserve memory.
+
+
+   .. data:: ac_in_buffer_size
+
+      The asynchronous input buffer size (default ``4096``).
+
+
+   .. data:: ac_out_buffer_size
+
+      The asynchronous output buffer size (default ``4096``).
+
    Unlike :class:`asyncore.dispatcher`, :class:`async_chat` allows you to
    define a first-in-first-out queue (fifo) of *producers*. A producer need
    have only one method, :meth:`more`, which should return data to be

Doc/library/asyncore.rst

@@ -71,19 +71,6 @@ any that have been added to the map during asynchronous service) is closed.
    which are called from the asynchronous loop.   Otherwise, it can be treated
    as a normal non-blocking socket object.
 
-   Two class attributes can be modified, to improve performance, or possibly
-   even to conserve memory.
-
-
-   .. data:: ac_in_buffer_size
-
-      The asynchronous input buffer size (default ``4096``).
-
-
-   .. data:: ac_out_buffer_size
-
-      The asynchronous output buffer size (default ``4096``).
-
    The firing of low-level events at certain times or in certain connection
    states tells the asynchronous loop that certain higher-level events have
    taken place.  For example, if we have asked for a socket to connect to