summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2021-08-30 19:20:08 +0000
committerLaurent Bercot <ska@appnovation.com>2021-08-30 19:20:08 +0000
commit93ec5714f75f54be285a9a2d347985a44f0bfedd (patch)
tree1608b2182c405759c0b15aa745c737e774c71b0f
parentbbfb27dc3c94ac128e2cb38309d5ce49f55e4fa6 (diff)
downloads6-93ec5714f75f54be285a9a2d347985a44f0bfedd.tar.xz
More more doc fixes
Signed-off-by: Laurent Bercot <ska@appnovation.com>
-rw-r--r--doc/s6-svlink.html2
-rw-r--r--doc/s6-svunlink.html4
2 files changed, 3 insertions, 3 deletions
diff --git a/doc/s6-svlink.html b/doc/s6-svlink.html
index f31e5f0..f2ea80f 100644
--- a/doc/s6-svlink.html
+++ b/doc/s6-svlink.html
@@ -93,7 +93,7 @@ limit. </li>
<ul>
<li> Using <tt>s6-svlink</tt> to start services is a suboptimal pattern: it
-requires precise manipulations involving use of <a href="s6-ftrigrd.html">s6-ftrigrd</a>
+requires precise manipulations involving use of <a href="libs6/s6-ftrigrd.html">s6-ftrigrd</a>
in order to avoid race conditions, so it is relatively expensive. The simpler,
more efficient pattern is to have all the supervisors already started at boot
time, so the existence of the supervisor can be relied on, and starting the
diff --git a/doc/s6-svunlink.html b/doc/s6-svunlink.html
index 7c01959..f3642be 100644
--- a/doc/s6-svunlink.html
+++ b/doc/s6-svunlink.html
@@ -78,9 +78,9 @@ 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>,
which only commands, and waits for, the death of the service, without
impacting the supervisor. Nevertheless, for symmetry with
-<a href="s6-svlinki.html">s6-svlink</a>, this program is provided. </li>
+<a href="s6-svlink.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
+situations that are nominal failures. For instance, it returns 0 even
if its timeout expires; the rationale is that there is no sensible action
for the user to do if this error is reported. <tt>s6-svunlink</tt> only
reports errors when they uncover a deeper problem in the system. </li>