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/jmx.xml

@@ -18,8 +18,7 @@
       <para>This chapter is not an introduction to JMX... it doesn't try to
       explain the motivations of why one might want to use JMX (or indeed what
       the letters JMX actually stand for). If you are new to JMX, check out
-      the section entitled <xref linkend="jmx-resources" /> at the end of this
-      chapter.</para>
+      <xref linkend="jmx-resources" /> at the end of this chapter.</para>
     </sidebar>
 
     <para>Specifically, Spring's JMX support provides four core
@@ -128,7 +127,7 @@ public class JmxTestBean implements IJmxTestBean {
     <literal>beans</literal> <interfacename>Map</interfacename> is used as the
     <classname>ObjectName</classname> for the bean referenced by the
     corresponding entry value. This behavior can be changed as described in
-    the section entitled <xref linkend="jmx-naming"/>.</para>
+    <xref linkend="jmx-naming"/>.</para>
 
     <para>With this configuration the <literal>testBean</literal> bean is
     exposed as an MBean under the <classname>ObjectName</classname>
@@ -270,8 +269,7 @@ public class JmxTestBean implements IJmxTestBean {
       already a valid JMX MBean and will be automatically registered by
       Spring. By default, beans that are autodetected for JMX registration
       have their bean name used as the <classname>ObjectName</classname>. This
-      behavior can be overridden as detailed in the section entitled
-      <xref linkend="jmx-naming" />.</para>
+      behavior can be overridden as detailed in <xref linkend="jmx-naming" />.</para>
     </section>
 
     <section id="jmx-exporting-registration-behavior">
@@ -954,8 +952,8 @@ public class AnnotationTestBean implements IJmxTestBean {
       to include it. The only problem with this approach is that the name of
       the <classname>JmxTestBean</classname> now has business meaning. You can
       address this issue by changing the default behavior for
-      <classname>ObjectName</classname> creation as defined in the section
-      entitled <xref linkend="jmx-naming" />.</para>
+      <classname>ObjectName</classname> creation as defined in
+      <xref linkend="jmx-naming" />.</para>
     </section>
 
     <section id="jmx-interface-java">
@@ -1760,4 +1758,4 @@ public class JmxTestBean implements IJmxTestBean, NotificationPublisherAware {
       </listitem>
     </itemizedlist>
   </section>
-</chapter>
+</chapter>