updates made during my review of beans.xml:

* eliminated all usage of "the section entitled", because <xref> links already render including "the section called ".  This was resulting in sentences like 'see also the section entitled the section called "@Autowired"'. This issue affected nearly all sections of the documentation, so went beyond just beans.xml

* fixed table overflow in the "Using filters to customize scanning" section (approx. p.90)

* fixed all code overflows in <programlisting/> elements

* corrected a couple minor syntax errors with SpEL examples (missing closing braces)

* added 'language="..."' element to <programlisting> elements where appropriate to enable syntax highlighting.

* normalized all code indention to four-space (some code listings were using one- and two-space)

* updated all code listings to use same-line opening braces.

* eliminated section regarding backward compatibility with Spring DTDs and singleton=true|false.  This seems like cruft to me, and we shouldn't keep historical notes around forever.

* Added <note> regarding the new thread scope (SimpleThreadScope) to Section 3.5 Bean Scopes.  Also updated the section on registering a custom Scope implementation to use the SimpleThreadScope as an example.

* updated the new-in-3.xml section to improve the @Configuration example

spring-framework-reference/src/aop.xml

@@ -271,8 +271,8 @@
         indication that the Spring team favors the @AspectJ annotation-style
         approach over the Spring XML configuration-style.</para>
 
-        <para>See the section entitled <xref linkend="aop-choosing" /> for a
-        fuller discussion of the whys and wherefores of each style.</para>
+        <para>See <xref linkend="aop-choosing" /> for a
+        more complete discussion of the whys and wherefores of each style.</para>
       </note>
     </section>
 
@@ -294,7 +294,7 @@
       to a method as a concrete type.</para>
 
       <para>It is important to grasp the fact that Spring AOP is
-      <emphasis>proxy-based</emphasis>. See the section entitled <xref
+      <emphasis>proxy-based</emphasis>. See <xref
       linkend="aop-understanding-aop-proxies" /> for a thorough examination of
       exactly what this implementation detail actually means.</para>
     </section>