svn commit: r1688675 - /sling/site/trunk/content/documentation/bundles/scheduler-service-commons-scheduler.mdtext

[kw...@apache.org]

Author: kwin
Date: Wed Jul  1 15:58:22 2015
New Revision: 1688675

URL: http://svn.apache.org/r1688675
Log:
fix link

Modified:
    sling/site/trunk/content/documentation/bundles/scheduler-service-commons-scheduler.mdtext

Modified: sling/site/trunk/content/documentation/bundles/scheduler-service-commons-scheduler.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/scheduler-service-commons-scheduler.mdtext?rev=1688675&r1=1688674&r2=1688675&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/scheduler-service-commons-scheduler.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/scheduler-service-commons-scheduler.mdtext Wed Jul  1 15:58:22 2015
@@ -83,7 +83,7 @@ or
 
     @Property(name="scheduler.runOn", value="SINGLE");
 
-Since in contrast to [Sling Jobs]([{{ refs.apache-sling-eventing-and-job-handling.path }}]) the scheduler queue is only held in memory, there will be no distribution of jobs. So if job '1' was scheduled on instance 'a' with the option to run on the leader only, but the leader is instance 'b', which hasn't the job in the queue, the job will never be executed by any instance!
+Since in contrast to [Sling Jobs]({{ refs.apache-sling-eventing-and-job-handling.path }}) the scheduler queue is only held in memory, there will be no distribution of jobs. So if job '1' was scheduled on instance 'a' with the option to run on the leader only, but the leader is instance 'b', which hasn't the job in the queue, the job will never be executed by any instance!
 
 ## The Scheduler API