s6

commit 3ea0b28892de170c5de281529613531dfa15eaa8
parent 70586b4a4ae15e008ee0a86dcb42602cc87744df
Author: Laurent Bercot <ska-skaware@skarnet.org>
Date:   Sun, 17 Jun 2018 00:52:05 +0000

 Doc clarification

Diffstat:
M
doc/s6-svscan-1.html
 | 
2
+-

1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/s6-svscan-1.html b/doc/s6-svscan-1.html
@@ -190,7 +190,7 @@ one-time initialization, with a big advantage over the "init-stage1"
 process: s6-svscan is running, as well as a few vital services, and if
 something bad happens, there's a getty for the administrator to log on.
 No need to play fancy tricks with <tt>/dev/console</tt> anymore! Yes,
-the theoretical separation in 3 stages is a bit more supple in practice:
+the theoretical separation in 3 stages is a bit more flexible in practice:
 the "stage 2" process 1 can be already running when a part of the
 "stage 1" one-time tasks are still being run.
 </p>