s6

commit 7d992838c709b6caada3c0b6134a969ba185f42f
parent 163b9d565057c7e55912b40f98fc190da85f142f
Author: Laurent Bercot <ska-skaware@skarnet.org>
Date:   Fri,  9 Oct 2020 17:13:30 +0000

 Better wording

Diffstat:
M
doc/notifywhenup.html
 | 
6
+++---

1 file changed, 3 insertions(+), 3 deletions(-)
diff --git 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>