aboutsummaryrefslogtreecommitdiff
path: root/doc/foot.5.scd
diff options
context:
space:
mode:
authorDaniel Eklöf <daniel@ekloef.se>2020-07-26 10:40:00 +0000
committerDaniel Eklöf <daniel@ekloef.se>2020-07-26 10:40:00 +0000
commit82d7cfdfe4e53a5c8b104195ead8f8994304748d (patch)
treebfc5a85fa5265446aca63afd03293393d74253c7 /doc/foot.5.scd
parentrender: scrollback indicator: add top margin (diff)
parentdoc: benchmark: update 'laptop' results after foot-1.4.0 (diff)
Merge branch 'master' into scrollback-position-indicator
Diffstat (limited to 'doc/foot.5.scd')
-rw-r--r--doc/foot.5.scd2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/foot.5.scd b/doc/foot.5.scd
index c348391b..1202e203 100644
--- a/doc/foot.5.scd
+++ b/doc/foot.5.scd
@@ -348,7 +348,7 @@ any of these options.
Now, that was a lof of text. But what is it foot actually does?
When receiving client data, it schedules a timer, the
- *delayed-render-lower*. If we do not recieve any more client data
+ *delayed-render-lower*. If we do not receive any more client data
before the timer has run out, we render the frame. If however, we
do receive more data, the timer is re-scheduled. That is, each
time we receive client data, frame rendering is delayed another