From a3cdeecf0033919e3b5a79c17c19b5ac98719256 Mon Sep 17 00:00:00 2001
From: Laurent Bercot <ska-skaware@skarnet.org>
Date: Mon, 20 Jul 2015 20:20:54 +0000
Subject:  - Add timeout-finish support and "down-readiness"  - LOTS of
 refactoring to make this work  - Remove s6-notifywhenup  - s6-supervise now
 rocks the casbah  - rc for 2.2.0.0

---
 doc/notifywhenup.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'doc/notifywhenup.html')

diff --git a/doc/notifywhenup.html b/doc/notifywhenup.html
index 9a288ac..6bc8b99 100644
--- a/doc/notifywhenup.html
+++ b/doc/notifywhenup.html
@@ -67,16 +67,16 @@ a generic mechanism that some daemons already implement.
 <a href="servicedir.html">service directory</a> for the daemon contains
 a valid <tt>notification-fd</tt> file, the daemon's supervisor, i.e. the
 <a href="s6-supervise.html">s6-supervise</a> program, will properly catch
-the daemon's message, update a state file (<tt>supervise/ready</tt>), then
+the daemon's message, update the status file (<tt>supervise/status</tt>),
 then notify all the subscribers
-with a 'U' event, meaning that the service is now up and ready.
+with a <tt>'U'</tt> event, meaning that the service is now up and ready.
 </p>
 
 <p>
  This method should really be implemented in every long-running
 program providing a service. When it is not the case, it's impossible
 to provide reliable startup notifications, and subscribers should then
-be content with the unreliable 'u' events provided by s6-supervise.
+be content with the unreliable <tt>'u'</tt> events provided by s6-supervise.
 </p>
 
 </body>
-- 
cgit v1.2.3