Index: openacs-4/packages/acs-core-docs/www/rp-design.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/rp-design.adp,v
diff -u -r1.1.2.5 -r1.1.2.6
--- openacs-4/packages/acs-core-docs/www/rp-design.adp	19 Nov 2016 09:21:55 -0000	1.1.2.5
+++ openacs-4/packages/acs-core-docs/www/rp-design.adp	13 Feb 2017 07:33:15 -0000	1.1.2.6
@@ -90,7 +90,7 @@
 database.</p><p><span class="strong"><strong>Authentication and
 Authorization</strong></span></p><p>Once the request processor has located both the package_id and
 concrete file associated with the request, authentication is
-performed by the <a class="ulink" href="../sessions" target="_top">session</a> security system. After authentication has been
+performed by the <a class="ulink" href="security-design" target="_top">session</a> security system. After authentication has been
 performed the user is authorized to have read access for the given
 package by the <a class="xref" href="permissions-design" title="Permissions Design">OpenACS 4 Permissions Design</a>. If
 authorization succeeds then the request is served, otherwise it is
@@ -242,4 +242,4 @@
 and Libraries"
 		    homeLink="index" homeLabel="Home" 
 		    upLink="kernel-doc" upLabel="Up"> 
-		
\ No newline at end of file
+		
Index: openacs-4/packages/acs-core-docs/www/rp-design.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/rp-design.html,v
diff -u -r1.37.2.4 -r1.37.2.5
--- openacs-4/packages/acs-core-docs/www/rp-design.html	6 Jan 2017 09:18:42 -0000	1.37.2.4
+++ openacs-4/packages/acs-core-docs/www/rp-design.html	13 Feb 2017 07:33:15 -0000	1.37.2.5
@@ -44,7 +44,7 @@
 given package_url, and package mountings must be persistent across server
 restarts and users must be able to manipulate the mountings on a live site,
 therefore this mapping is stored in the database.</p><p><span class="strong"><strong>Authentication and Authorization</strong></span></p><p>Once the request processor has located both the package_id and concrete
-file associated with the request, authentication is performed by the <a class="ulink" href="../sessions.html" target="_top">session</a> security system. After authentication has
+file associated with the request, authentication is performed by the <a class="ulink" href="security-design.html" target="_top">session</a> security system. After authentication has
 been performed the user is authorized to have read access for the given
 package by the <a class="xref" href="permissions-design.html" title="Permissions Design">OpenACS 4 Permissions Design</a>.
 If authorization succeeds then the request is served, otherwise it is
Index: openacs-4/packages/acs-core-docs/www/xml/kernel/rp-design.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/rp-design.xml,v
diff -u -r1.10.14.1 -r1.10.14.2
--- openacs-4/packages/acs-core-docs/www/xml/kernel/rp-design.xml	11 Nov 2016 08:53:59 -0000	1.10.14.1
+++ openacs-4/packages/acs-core-docs/www/xml/kernel/rp-design.xml	13 Feb 2017 07:33:16 -0000	1.10.14.2
@@ -148,7 +148,7 @@
 <para><emphasis role="strong">Authentication and Authorization</emphasis></para>
 
 <para>Once the request processor has located both the package_id and concrete
-file associated with the request, authentication is performed by the <ulink url="../sessions.html">session</ulink> security system. After authentication has
+file associated with the request, authentication is performed by the <ulink url="security-design.html">session</ulink> security system. After authentication has
 been performed the user is authorized to have read access for the given
 package by the <xref linkend="permissions-design"/>.
 If authorization succeeds then the request is served, otherwise it is