[Springframework-cvs] spring/docs/reference/src jmx.xml,1.14,1.14.4.1 mvc.xml,1.46.4.1,1.46.4.2

[Juergen H. <jho...@us...>]

Update of /cvsroot/springframework/spring/docs/reference/src
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv18244/docs/reference/src

Modified Files:
      Tag: mbranch-1-2
	jmx.xml mvc.xml 
Log Message:
fixed typos

Index: mvc.xml
===================================================================
RCS file: /cvsroot/springframework/spring/docs/reference/src/mvc.xml,v
retrieving revision 1.46.4.1
retrieving revision 1.46.4.2
diff -C2 -d -r1.46.4.1 -r1.46.4.2
*** mvc.xml	23 Feb 2006 22:05:46 -0000	1.46.4.1
--- mvc.xml	21 Apr 2006 00:10:49 -0000	1.46.4.2
***************
*** 1346,1350 ****
  
        <para>It is sometimes desireable to issue an HTTP redirect back to the
!       client, before the view is rendered. This si desireable for example when
        one controller has been called with POSTed data, and the response is
        actually a delegation to another controller (for example on a successful
--- 1346,1350 ----
  
        <para>It is sometimes desireable to issue an HTTP redirect back to the
!       client, before the view is rendered. This is desireable for example when
        one controller has been called with POSTed data, and the response is
        actually a delegation to another controller (for example on a successful

Index: jmx.xml
===================================================================
RCS file: /cvsroot/springframework/spring/docs/reference/src/jmx.xml,v
retrieving revision 1.14
retrieving revision 1.14.4.1
diff -C2 -d -r1.14 -r1.14.4.1
*** jmx.xml	9 Aug 2005 09:39:57 -0000	1.14
--- jmx.xml	21 Apr 2006 00:10:49 -0000	1.14.4.1
***************
*** 110,114 ****
  beans with that. This is useful when your application is running inside a container such as Tomcat or IBM WebSphere that has its own
  <literal>MBeanServer</literal>.</para>
! 			<para>However, this is approach is no use for standalone environment, or when running inside a container that does not provide an
  <literal>MBeanServer</literal>. To overcome this you can create an
  <literal>MBeanServer</literal> instance declaratively by adding an
--- 110,114 ----
  beans with that. This is useful when your application is running inside a container such as Tomcat or IBM WebSphere that has its own
  <literal>MBeanServer</literal>.</para>
! 			<para>However, this approach is of no use in a standalone environment, or when running inside a container that does not provide an
  <literal>MBeanServer</literal>. To overcome this you can create an
  <literal>MBeanServer</literal> instance declaratively by adding an