More doc fixes

Signed-off-by: Laurent Bercot <ska@appnovation.com>

1 files changed, 3 insertions, 3 deletions

diff --git a/doc/s6-svunlink.html b/doc/s6-svunlink.html
index 7ec7a4b..7c01959 100644
--- a/doc/s6-svunlink.html
+++ b/doc/s6-svunlink.html
@@ -29,7 +29,7 @@ supervisor process managing the service has disappeared, then exits.
 <p>
  The point of <tt>s6-svunlink</tt> is to help integrate
 service directories into an existing service manager sequence and
-eliminating race conditions.
+eliminate race conditions.
 </p>
 
 <h2> Interface </h2>
@@ -75,10 +75,10 @@ The default is 0, meaning no time limit.. </li>
  <li> Using <tt>s6-svlink</tt> to stop services is a suboptimal pattern:
 starting and stopping supervisors is a heavier operation than just stopping
 services. The simpler, more efficient pattern is to simply perform
-<a href="s6-svc.html">s6-svc -dwD <em>scandir</em><tt>/</tt><em>name</em>,
+<a href="s6-svc.html">s6-svc -dwD <em>scandir</em><tt>/</tt><em>name</em></a>,
 which only commands, and waits for, the death of the service, without
 impacting the supervisor. Nevertheless, for symmetry with
-<a href="s6-svlink">s6-svlink</a>, this program is provided. </li>
+<a href="s6-svlinki.html">s6-svlink</a>, this program is provided. </li>
  <li> <tt>s6-svunlink</tt> is a destructor; as is, it returns 0 even in
 situations that are nominally a failure. For instance, it returns 0 even
 if its timeout expires; the rationale is that there is no sensible action