From d633c1590c01e03b4e748a5e962a732cb017daa6 Mon Sep 17 00:00:00 2001
From: "benjamin.franksen" <benjamin.franksen@helmholtz-berlin.de>
Date: Tue, 16 Apr 2013 09:08:02 +0000
Subject: [PATCH] docs: explain builtin delay as synonym for elapsed

---
 documentation/Tutorial.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/Tutorial.txt b/documentation/Tutorial.txt
index 6f90bc64..a94be8d4 100644
--- a/documentation/Tutorial.txt
+++ b/documentation/Tutorial.txt
@@ -700,7 +700,7 @@ it tells the sequencer to compare the value specified by the
 state is entered or whenever the state is entered from another state.
 If the timer matches or exceeds the value of the expression the
 :c:func:`delay` function returns ``TRUE`` otherwise it returns
-``FALSE``.
+``FALSE``.  Think of the operation as `elapsed(s)` rather than `delay(s)`.
 
 If your action statements have any sort of polling loops or calls to
 ``epicsThreadSleep`` you should reconsider your design. The presence
-- 
GitLab