From fb3d0b7f25bab7c228a8cfb197fe24bb30b9eeb3 Mon Sep 17 00:00:00 2001
From: Luke Taylor <luke.taylor@springsource.com>
Date: Thu, 7 Aug 2008 19:09:49 +0000
Subject: [PATCH] Fixed link

---
 src/docbkx/secured-objects.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/docbkx/secured-objects.xml b/src/docbkx/secured-objects.xml
index 3de7416305..000a783ad1 100644
--- a/src/docbkx/secured-objects.xml
+++ b/src/docbkx/secured-objects.xml
@@ -9,7 +9,7 @@
     <para>
       Prior to Spring Security 2.0, securing <literal>MethodInvocation</literal>s needed quite a 
       lot of boiler plate configuration. Now the recommended approach for method security 
-      is to use <link xlink:href="ns-method-security">namespace configuration</link>.
+      is to use <link xlink:href="#ns-method-security">namespace configuration</link>.
       This way the method security infrastructure beans are configured automatically for you so you don't really need to  
       know about the implementation classes. We'll just provide a quick overview of the classes that are involved here.
     </para>