minor.

1 files changed, 6 insertions, 4 deletions

diff --git a/doc/benefits.html b/doc/benefits.html
index fbe7846..c76cbef 100644
--- a/doc/benefits.html
+++ b/doc/benefits.html
@@ -45,9 +45,11 @@ By default a service is defined to be up, that means, if the service daemon
 dies, it will be restarted.
 Of course you can <a href="runsvctrl.8.html">tell runsv</a> otherwise.
 <p>
-You don't have such a control interface with sysv init for example.
+You don't have such a control interface with <i>sysv init</i> for example.
 Using the control interface to send signals to the service daemon saves a lot
 of extra (non trivial) work to reliably find out the daemon's process id.
+Also <i>sysv init</i> only supports 'respawning' of services started from
+<tt>inittab</tt>.
 
 <hr>
 <a name="state"><h3>Clean process state</h3></a>
@@ -56,7 +58,7 @@ service is activated for the first time, reactivated, or simply restarted.
 This means that the service always is started with the same environment,
 resource limits, open file descriptors, and controlling terminals.
 <p>
-You don't necessarily have that with sysv init scripts for example.
+You don't necessarily have that with <i>sysv init</i> scripts for example.
 It requires a carefully written init script that reliably cleans up and sets
 the initial process state before starting the service daemon.
 This adds even more complexity to the init script in comparison with a run
@@ -80,8 +82,8 @@ After rebooting the system this shows up on the screen:
 The <tt>food</tt> program is installed in <tt>/opt/foo/bin/</tt>.  When
 starting the service for the first time using the init script, the
 <tt>PATH</tt> environment variable contained <tt>/opt/foo/bin</tt>.
-After reboot init started the service using the init script, but with a
-different value for the <tt>PATH</tt> variable, not containing
+After reboot <tt>init</tt> started the service using the init script, but
+with a different value for the <tt>PATH</tt> variable, not containing
 <tt>/opt/foo/bin</tt>.
 Of course the init script should have set <tt>PATH</tt> before starting the
 daemon; the problem is that it worked in the first place, and that the error