From bf5b6315e7a6907c6a95564e7042f90f9aed632a Mon Sep 17 00:00:00 2001
From: Laurent Bercot <ska-skaware@skarnet.org>
Date: Thu, 6 Apr 2023 17:34:06 +0000
Subject:  Doc typo fixes

Signed-off-by: Laurent Bercot <ska@appnovation.com>
---
 doc/s6-rc-update.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'doc/s6-rc-update.html')

diff --git a/doc/s6-rc-update.html b/doc/s6-rc-update.html
index 5b52a6b..0883a22 100644
--- a/doc/s6-rc-update.html
+++ b/doc/s6-rc-update.html
@@ -281,18 +281,18 @@ process in charge of it will still show up in the process list as
 <tt>s6-supervise <em>oldname</em></tt>. This is purely cosmetic and
 will have no impact on the service; nevertheless, if you wish to avoid that,
 simply force a restart on every longrun you rename. </li>
- <li> After a s6-rc-update invocation, the old compiled service database
+ <li> After an s6-rc-update invocation, the old compiled service database
 is left unchanged where it was, and the new compiled
 service database is used in-place. If the machine is rebooted, the
 <a href="s6-rc-init.html">s6-rc-init</a> invocation will still boot on the
 old compiled unless more work is performed. It is recommended to keep a
 <tt>current</tt> symbolic link to the current compiled, to always
 <a href="s6-rc-init.html">s6-rc-init</a> on <tt>current</tt>, and to
-make <tt>current</tt> a link to the new compiled right after a s6-rc-update
+make <tt>current</tt> a link to the new compiled right after an s6-rc-update
 invocation. </li>
  <li> s6-rc-update is the only way to "free" the old compiled database
 for displacement or deletion. A live compiled database must not be
-tampered with. After a s6-rc-update invocation, the old database isn't
+tampered with. After an s6-rc-update invocation, the old database isn't
 live anymore and can be moved or deleted; instead, <em>newdb</em> is
 live. </li>
 </ul>
-- 
cgit v1.3.1