svn commit: r897334 - in /websites/staging/isis/trunk: cgi-bin/ content/ content/reference/Security.html

[bu...@apache.org]

Author: buildbot
Date: Tue Feb 11 00:53:59 2014
New Revision: 897334

Log:
Staging update by buildbot for isis

Modified:
    websites/staging/isis/trunk/cgi-bin/   (props changed)
    websites/staging/isis/trunk/content/   (props changed)
    websites/staging/isis/trunk/content/reference/Security.html

Propchange: websites/staging/isis/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb 11 00:53:59 2014
@@ -1 +1 @@
-1566928
+1566929

Propchange: websites/staging/isis/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb 11 00:53:59 2014
@@ -1 +1 @@
-1566928
+1566929

Modified: websites/staging/isis/trunk/content/reference/Security.html
==============================================================================
--- websites/staging/isis/trunk/content/reference/Security.html (original)
+++ websites/staging/isis/trunk/content/reference/Security.html Tue Feb 11 00:53:59 2014
@@ -305,7 +305,7 @@ is a snapshot of their credentials at th
 
 <h3><code>BackgroundService</code>s and <code>CommandContext</code></h3>
 
-<p>If using the <a href="../services/background-service.html">BackgroundService</a>, then it is possible to persist commands that will execute corresponding actions in the background (for example under the control of a scheduler).</p>
+<p>If using the <a href="./services/background-service.html">BackgroundService</a>, then it is possible to persist commands that will execute corresponding actions in the background (for example under the control of a scheduler).</p>
 
 <p>In this situation, the <code>user</code> obtained from <code>DomainObjectContainer</code> will be that of the scheduler process, which may not be what you want.</p>