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