summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2020-10-09 17:13:30 +0000
committerLaurent Bercot <ska-skaware@skarnet.org>2020-10-09 17:13:30 +0000
commit7d992838c709b6caada3c0b6134a969ba185f42f (patch)
tree2e68599b52053bab4c50155cd27ca91566509059
parent163b9d565057c7e55912b40f98fc190da85f142f (diff)
downloads6-7d992838c709b6caada3c0b6134a969ba185f42f.tar.xz
Better wording
-rw-r--r--doc/notifywhenup.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/notifywhenup.html b/doc/notifywhenup.html
index a979f94..c7a0478 100644
--- a/doc/notifywhenup.html
+++ b/doc/notifywhenup.html
@@ -168,7 +168,7 @@ written in the <tt>notification-fd</tt> file. </li>
<li> And that is all. <strong>Do not</strong> use <tt>s6-notifyoncheck</tt>
in this case, because you do not need to poll to know whether <em>foo</em>
is ready; instead, <em>foo</em> will directly communicate its readiness to
-<a href="s6-supervise.html">s6-supervise</a>, which is a much more efficient
+<a href="s6-supervise.html">s6-supervise</a>, and that is a much more efficient
mechanism. </li>
</ul>
@@ -185,8 +185,8 @@ readiness event to programs that are waiting for it - for instance the
make sure that other programs only start when the daemon is ready. For
instance, the
<a href="//skarnet.org/software/s6-rc/">s6-rc</a> service manager uses
-that mechanism to handle dependencies when starting services that depend
-on daemons. </li>
+that mechanism to bring sets of services up or down: a service starts as
+soon as all its dependencies are ready, but never earlier. </li>
</ul>
</body>