aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2026-02-23 08:58:12 +0000
committerLaurent Bercot <ska-skaware@skarnet.org>2026-02-23 08:58:12 +0000
commit0a0aa75f06da164a37fe6ed7929029d76e978355 (patch)
treed21ff978628b4fa33b85f91c11efa1c08671ede3
parent364fbf65882fcfbb2a772221cd0fbb27bc43b583 (diff)
downloads6-rc-0a0aa75f06da164a37fe6ed7929029d76e978355.tar.gz
doc typo fixes
-rw-r--r--doc/s6-rc-set-commit.html2
-rw-r--r--doc/s6-rc-set-install.html6
-rw-r--r--doc/s6-rc-set-status.html2
3 files changed, 5 insertions, 5 deletions
diff --git a/doc/s6-rc-set-commit.html b/doc/s6-rc-set-commit.html
index e1200a2..44987f8 100644
--- a/doc/s6-rc-set-commit.html
+++ b/doc/s6-rc-set-commit.html
@@ -72,7 +72,7 @@ default is <strong>default</strong>. </dd>
<dt> -h <em>fdhuser</em>, --fdholder-user=<em>fdhuser</em> </dt>
<dd> Specifies <em>fdhuser</em> as the user the fd-holder daemon will run
-at if the service database is installed and booted on. The default is
+as if the service database is installed and booted on. The default is
<strong>root</strong>, which is fine, but paranoid users may want to
specify a non-root account. </dd>
diff --git a/doc/s6-rc-set-install.html b/doc/s6-rc-set-install.html
index a9fb281..9c4d940 100644
--- a/doc/s6-rc-set-install.html
+++ b/doc/s6-rc-set-install.html
@@ -40,7 +40,7 @@ has been <a href="repodefs.html#commit">committed</a> and that no changes have o
<li> It takes the corresponding service database and copies it to the same directory as <em>bootdb</em>. </li>
<li> It calls <a href="s6-rc-update.html">s6-rc-update</a> on that copy of the compiled service
database, which makes it the new <em>live</em> database. Some services may be stopped, and
-other started, in the process. </li>
+others started, in the process. </li>
<li> It updates the <em>bootdb</em> link to point to the new database, so that
next boot uses it. </li>
</ul>
@@ -78,12 +78,12 @@ a conversion file, which should be correct in most cases. </dd>
<dt> -b, --block </dt>
<dd> Pass the <tt>-b</tt> option to <a href="s6-rc-update.html">s6-rc-update</a>,
which makes it block rather than fail when the live database is currently being
-used by another program - typically when an <a href="s6-rc.html">s6-rc change</a>
+used by another program &mdash; typically when an <a href="s6-rc.html">s6-rc change</a>
transition is under way. </dd>
<dt> -K, --keep-old </dt>
<dd> If this option is given, the old live database, after it has been
-replaced, is kapt around, and s6-rc-set-install prints a line to stdout that
+replaced, is kept around, and s6-rc-set-install prints a line to stdout that
is the path to that old database. It can e.g. be used by automation to keep
the possibility of rollbacks.
By default, s6-rc-set-install will delete the old live database after
diff --git a/doc/s6-rc-set-status.html b/doc/s6-rc-set-status.html
index 53c1b28..f63436b 100644
--- a/doc/s6-rc-set-status.html
+++ b/doc/s6-rc-set-status.html
@@ -62,7 +62,7 @@ essential. This is the default. </dd>
<dt> -e, --without-essentials </dt>
<dd> Ignore services in the <tt>always</tt> rx: do not print them. </dd>
- <dt> -L. --list </dt>
+ <dt> -L, --list </dt>
<dd> Do not print <tt>/<em>rx</em></tt> at the end of each line: only print the service names. </dd>
</dl>