From c26b476060353355b43d251dbb8a624c19c5ec30 Mon Sep 17 00:00:00 2001
From: Laurent Bercot <ska-skaware@skarnet.org>
Date: Mon, 23 Feb 2026 09:11:41 +0000
Subject:  Doc typo fixes

---
 doc/overview.html                |  2 +-
 doc/s6-frontend-helper-kill.html |  2 +-
 doc/s6-frontend.conf.html        | 10 +++++-----
 doc/s6.html                      |  6 +++---
 doc/s6_live.html                 |  1 -
 doc/s6_process.html              |  2 +-
 doc/s6_set.html                  |  4 ++--
 7 files changed, 13 insertions(+), 14 deletions(-)

diff --git a/doc/overview.html b/doc/overview.html
index e83b81a..c8646f8 100644
--- a/doc/overview.html
+++ b/doc/overview.html
@@ -158,7 +158,7 @@ the sshd upstream, but service definitions are <em>policy</em> not
 software authors.) </li>
    <li> Essential services, i.e. how to boot a machine and bring it to
 the state where it can accept logins and run services provided by packages,
-should be provided by the distribution in a specific package. </li>
+should be provided by the distribution in a specific package.
     <ul>
      <li> systemd comes with a big list of unit files: it provides some policy
 itself. </li>
diff --git a/doc/s6-frontend-helper-kill.html b/doc/s6-frontend-helper-kill.html
index e32840c..1a3a315 100644
--- a/doc/s6-frontend-helper-kill.html
+++ b/doc/s6-frontend-helper-kill.html
@@ -22,7 +22,7 @@
  <tt>s6-frontend-helper-kill</tt> is a small utility to send numerical
 signals to a given list of pids. It is not meant to be called directly,
 although nothing bad will happen if you do. It is used in command lines crafted by
-<a href="s6_process_kill.html">s6 process kill</a> instead of the POSIX
+<a href="s6_process_kill.html#kill">s6 process kill</a> instead of the POSIX
 <a href="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/kill.html">kill</a>
 program, because the latter does not support sending arbitrary numerical signals.
 </p>
diff --git a/doc/s6-frontend.conf.html b/doc/s6-frontend.conf.html
index b5ee708..938b3c0 100644
--- a/doc/s6-frontend.conf.html
+++ b/doc/s6-frontend.conf.html
@@ -30,7 +30,7 @@ are located).
 
 <p>
  For instance, this is what allows the
-<a href="s6_process_restart">s6 process restart foobar</a> command to send
+<a href="s6_process_restart#restart">s6 process restart foobar</a> command to send
 <a href="//skarnet.org/software/s6/s6-svc.html">s6-svc -r</a> to the
 <em>foobar</em> service without the user needing to type, or even remember,
 what the full path to the <em>foobar</em> service directory is.
@@ -57,27 +57,27 @@ simple <code>key = value</code> lines, comments permitted.
 <dd> The directory where <a href="//skarnet.org/software/s6/s6-svscan.html">s6-svscan</a>
 is running.
 The default is <tt>/run/service</tt> (possibly overridden by the <tt>--scandir</tt> build-time configure option to
-<a href="//skarnet.org/software/s6-linux-init/"></a> or to
+<a href="//skarnet.org/software/s6-linux-init/">s6-linux-init</a> or to
 <a href="//skarnet.org/software/s6-frontend/">s6-frontend</a>). </dd>
 
 <dt> livedir </dt>
 <dd> The directory hosting the live service database managed by
 <a href="//skarnet.org/software/s6-rc/s6-rc.html">s6-rc</a>.
 The default is <tt>/run/s6-rc</tt> (possibly overridden by the <tt>--livedir</tt> build-time configure option to
-<a href="//skarnet.org/software/s6-rc/"></a> or to
+<a href="//skarnet.org/software/s6-rc/">s6-rc</a> or to
 <a href="//skarnet.org/software/s6-frontend/">s6-frontend</a>). </dd>
 
 <dt> repodir </dt>
 <dd> The directory hosting the repository of service sets managed by the
 <a href="//skarnet.org/software/s6-rc/repodefs.html">s6-rc <em>repo</em> commands</a>.
 The default is <tt>/var/lib/s6-rc/repository</tt> (possibly overridden by the <tt>--repodir</tt> build-time configure option to
-<a href="//skarnet.org/software/s6-rc/"></a> or to
+<a href="//skarnet.org/software/s6-rc/">s6-rc</a> or to
 <a href="//skarnet.org/software/s6-frontend/">s6-frontend</a>). </dd>
 
 <dt> bootdb </dt>
 <dd> The path to the boot-time compiled service database.
 The default is <tt>/etc/s6-rc/compiled/current</tt> (possibly overridden by the <tt>--bootdb</tt> build-time configure option to
-<a href="//skarnet.org/software/s6-rc/"></a> or to
+<a href="//skarnet.org/software/s6-rc/">s6-rc</a> or to
 <a href="//skarnet.org/software/s6-frontend/">s6-frontend</a>). </dd>
 
 <dt> stmpdir </dt>
diff --git a/doc/s6.html b/doc/s6.html
index 3b2a6fb..42a9cf0 100644
--- a/doc/s6.html
+++ b/doc/s6.html
@@ -90,7 +90,7 @@ Any given command or subcommand is ignored. </dd>
 
  <dt> -V, --version </dt>
  <dd> Run the <a href="#version"><tt>s6 version</tt></a> command.
- <dd> Any given command or subcommand is ignored. </dd>
+Any given command or subcommand is ignored. </dd>
 
  <dt> -s <em>scandir</em>, --scandir=<em>scandir</em> </dt>
  <dd> Use <em>scandir</em> as scan directory (i.e. the directory where
@@ -111,7 +111,7 @@ and manipulate their service sets). </dd>
  <dt> -c <em>bootdb</em>, --bootdb=<em>bootdb</em> </dt>
  <dd> Use <em>bootdb</em> as the name of the compiled service database
 used by s6-rc at boot time (i.e. the directory where
-the <a href="//skarnet.org/software/s6-rc/s6-rc.html">s6-rc</a> reads
+<a href="//skarnet.org/software/s6-rc/s6-rc.html">s6-rc</a> reads
 information on how to start all the wanted services). </dd>
 
  <dt> --stmpdir=<em>stmpdir</em> </dt>
@@ -220,7 +220,7 @@ The details are available <a href="s6_system.html">here</a>.
 <ul>
  <li> <tt>s6</tt> does not perform real operations itself. Instead, after
 finding the path to its <a href="s6-frontend.conf.html">configuration file</a>
-<em>conf</em>, it rewrites itself into <code>envfile -I <em>conf</em></code> -- s6-frontend
+<em>conf</em>, it rewrites itself into <code>envfile -I <em>conf</em> -- s6-frontend
 <em>global_options...</em> <em>command</em> <em>subcommand</em> <em>subcommand_options...</em> <em>args...</em></code>
   <ul>
    <li> <a href="//skarnet.org/software/execline/envfile.html">envfile</a> reads and parses <em>conf</em> </li>
diff --git a/doc/s6_live.html b/doc/s6_live.html
index dc3b299..89b99fd 100644
--- a/doc/s6_live.html
+++ b/doc/s6_live.html
@@ -193,7 +193,6 @@ milliseconds, stop waiting and don't attempt to perform the remaining
 transitions. By default, <em>timeout</em> is 0, meaning infinite: the
 command can wait forever. </dd>
 
-<dl>
 <dt> -D <em>bundle</em>, --default-bundle=<em>bundle</em> </dt>
 <dd> Start the bundle of services named <em>bundle</em> instead.
 The default is <tt>default</tt>, possibly overridden by the
diff --git a/doc/s6_process.html b/doc/s6_process.html
index 9247716..0445d2d 100644
--- a/doc/s6_process.html
+++ b/doc/s6_process.html
@@ -230,7 +230,7 @@ issuing a stop followed by a start command on the targeted service(s). </li>
 
 <dl>
 <dt> -W, --no-wait </dt>
-<dd> Exit immediately, do not wait until the service has restarted
+<dd> Exit immediately, do not wait until the service has restarted.
 This is the default. </dd>
 
 <dt> -w, --wait </dt>
diff --git a/doc/s6_set.html b/doc/s6_set.html
index c20fbd1..b29c189 100644
--- a/doc/s6_set.html
+++ b/doc/s6_set.html
@@ -224,7 +224,7 @@ make the set inconsistent. </li>
 
 <dl>
 <dt> -f, --ignore-dependencies </dt>
-<dd> Only change the services listed in <em>services</em>, don't compute dependencies </dd>
+<dd> Only change the services listed in <em>services</em>, don't compute dependencies. </dd>
 
 <dt> -n, --dry-run </dt>
 <dd> Do not perform the change; only show what would be done and check whether the set
@@ -296,7 +296,7 @@ change <tt>B</tt> to be unmasked or enabled as well. </dd>
 <h4> Interface </h4>
 
 <pre>
-     s6 set commit [ -f ] [ -K ] [ -D <em>defaultbundle</em> [ -h <em>fdhuser</em> ]
+     s6 set commit [ -f ] [ -K ] [ -D <em>defaultbundle</em> ] [ -h <em>fdhuser</em> ]
 </pre>
 
 <ul>
-- 
cgit v1.3.1