summaryrefslogtreecommitdiffstats
path: root/klaptopdaemon/xautolock_engine.c
diff options
context:
space:
mode:
Diffstat (limited to 'klaptopdaemon/xautolock_engine.c')
-rw-r--r--klaptopdaemon/xautolock_engine.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/klaptopdaemon/xautolock_engine.c b/klaptopdaemon/xautolock_engine.c
index 08094e7..c293d9e 100644
--- a/klaptopdaemon/xautolock_engine.c
+++ b/klaptopdaemon/xautolock_engine.c
@@ -380,7 +380,7 @@ evaluateTriggers (Display* d)
* Nevertheless, simply resetting the screensaver is a
* convenience action that aids many xlock users, and doesn't
* harm anyone (*). The problem with older versions of xlock
- * is that they can be told to tqreplace (= disable) the real
+ * is that they can be told to replace (= disable) the real
* screensaver, but forget to reset that same screensaver if
* it was already active at the time xlock starts. I guess
* xlock initially wasn't designed to be run without a user