summaryrefslogtreecommitdiff
path: root/man/systemd.timer.xml
diff options
context:
space:
mode:
authorMichael Biebl <mbiebl@gmail.com>2016-07-12 12:52:11 +0200
committerLennart Poettering <lennart@poettering.net>2016-07-12 12:52:11 +0200
commit595bfe7df2999cfb99b274ce510695aed4aba6d5 (patch)
treeaa62c48d1ad662171930306e6af077626350937b /man/systemd.timer.xml
parent037a3ded54f72338fc95285d7971b61f695e3c1a (diff)
Various fixes for typos found by lintian (#3705)
Diffstat (limited to 'man/systemd.timer.xml')
-rw-r--r--man/systemd.timer.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml
index 0fa95e97a8..4fe140e4bc 100644
--- a/man/systemd.timer.xml
+++ b/man/systemd.timer.xml
@@ -76,7 +76,7 @@
<para>Note that in case the unit to activate is already active at the time the timer elapses it is not restarted,
but simply left running. There is no concept of spawning new service instances in this case. Due to this, services
- with <varname>RemainAfterExit=</varname> set (which stay around continously even after the service's main process
+ with <varname>RemainAfterExit=</varname> set (which stay around continuously even after the service's main process
exited) are usually not suitable for activation via repetitive timers, as they will only be activated once, and
then stay around forever.</para>
</refsect1>