Index: trunk/FACT++/www/schedule/index.html
===================================================================
--- trunk/FACT++/www/schedule/index.html	(revision 18720)
+++ trunk/FACT++/www/schedule/index.html	(revision 18722)
@@ -113,11 +113,28 @@
 
     <H3 style="font-family:arial;padding-top:20px;padding-bottom:10px;">Scheduling</H3>
-    Note that the last entry display in red will most probably the first one
-    executed by the scheduler. If the scheduling is running, it will just replace
-    the next entry in the schedule and be executed completely. If the scheduler is not
+    Note that the last entry display in red will most probably be the first one
+    executed by the scheduler. If the scheduler (Main.js) is running, it will just replace
+    the next entry in the schedule and be executed completely. If the scheduler (Main.js) is not
     running, still the last red entry will be the first one to be executed, but since
     it is the first one executed by the script, the script assumes that it failed and
-    was restarted. Therefore, only the last of its observations (usually <I>data</I>
+    was restarted. Therefore, only the last of its observations (usually <I>data</I>)
     is executed.
+
+    <H3 style="font-family:arial;padding-top:20px;padding-bottom:10px;">Suspend</H3>
+    If a <I>suspend</I> is scheduled, all further observations are discarded. The
+    <I>suspend</I> itself is just a <I>sleep</I>. If very soon, a new observation
+    will be started, it is best to schedule the <I>suspend</I> before it, otherwise
+    the observation might get started before the <I>suspend</I> is executed. Note
+    that a suspend does <b>not</b> interrupt the current observation, but will work
+    as a normal entry, i.e. the previous measurement (usually a <i>data</i> run) will
+    be finished before the suspend is executed.
+
+    <H3 style="font-family:arial;padding-top:20px;padding-bottom:10px;">Resume</H3>
+    If a <I>resume</I> is scheduled, it has the same effect as if the preceeding
+    <i>suspend</i> was removed. That effectively means that the last observation
+    which was scheduled before the <i>resume</i> will be executed as it if just became
+    valid. Consequently, if it is scheduled close to the change of observation, 
+    it makes sense to schedule it after this observation, to avoid that the previous
+    observation becomes effective.
 
     <H3 style="font-family:arial;padding-top:20px;padding-bottom:10px;">Options</H3>