From 2a4d8598123fece2614a64c40b28a403494b4576 Mon Sep 17 00:00:00 2001
From: Luke Taylor <luke.taylor@springsource.com>
Date: Tue, 13 May 2008 10:18:09 +0000
Subject: [PATCH] SEC-829: Minor doc fix

---
 src/docbkx/namespace-config.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/docbkx/namespace-config.xml b/src/docbkx/namespace-config.xml
index 6053a288bc..b189aa58f2 100644
--- a/src/docbkx/namespace-config.xml
+++ b/src/docbkx/namespace-config.xml
@@ -526,7 +526,7 @@
         entire application context. You should only declare one <literal>&lt;global-method-security&gt;</literal> element.
         The following declaration would enable support for both types of annotations:
 <programlisting><![CDATA[
-  <global-method-security secured-annotations="enabled" jsr250-annotations="true"/>
+  <global-method-security secured-annotations="enabled" jsr250-annotations="enabled"/>
   ]]>
 </programlisting>        
       </para>
@@ -536,9 +536,9 @@
           The use of <literal>protect-pointcut</literal> is particularly powerful, as it allows you to
           apply security to many beans with only a simple declaration. Consider the following example:
           <programlisting><![CDATA[
-	<global-method-security>
+  <global-method-security>
     <protect-pointcut expression="execution(* com.mycompany.*Service.*(..))" access="ROLE_USER"/>
-	</global-method-security>
+  </global-method-security>
 ]]>
           </programlisting>
           This will protect all methods on beans declared in the application context whose classes