summaryrefslogtreecommitdiff
path: root/doc/api/signals.texi
diff options
context:
space:
mode:
Diffstat (limited to 'doc/api/signals.texi')
-rw-r--r--doc/api/signals.texi5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/api/signals.texi b/doc/api/signals.texi
index 9f674e1..0d8c589 100644
--- a/doc/api/signals.texi
+++ b/doc/api/signals.texi
@@ -8,7 +8,7 @@ number of callback procedures are registered to respond to events
which mutate the relevant data structures. However, this approach,
while simple and effective, comes at the price of readability,
reproducibility, and expression. Instead of explicitly mutating data
-and entering ``callback hell'', Sly abstracts and formalizes the
+and entering ``callback hell,'' Sly abstracts and formalizes the
process using a functional reactive programming style.
In Sly, time-varying values are called ``signals'', and they are
@@ -34,7 +34,8 @@ player move faster. Finally, the scaled vector is added to the
previous player position via @code{signal-fold}. The player's
position is at (320, 240) initially. As you can see, there are no
callbacks and explicit mutation needed, and the position seems to
-magically change with the passage of time.
+magically change with the passage of time and pushing of the arrow
+keys.
@deffn {Scheme Procedure} signal? @var{obj}
Return @code{#t} if @var{obj} is a signal.