summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2016-02-27 09:22:56 +0000
committerLaurent Bercot <ska-skaware@skarnet.org>2016-02-27 09:22:56 +0000
commit6078e31ea595fcc9b23efa04c437efad8a42c1bf (patch)
tree2bd288fb254ab8b921cb75ef7e86ad64c7edff4b
parent098816337707427d85a50ce190935c29ab72e076 (diff)
downloads6-rc-6078e31ea595fcc9b23efa04c437efad8a42c1bf.tar.xz
Doc typo fixes
-rw-r--r--doc/s6-rc-update.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/s6-rc-update.html b/doc/s6-rc-update.html
index f683952..e424f98 100644
--- a/doc/s6-rc-update.html
+++ b/doc/s6-rc-update.html
@@ -115,7 +115,7 @@ bundle.
<p>
s6-rc-update examines atomic services, as defined in the old compiled,
that are up at invocation time, and computes what is necessary for the
-"same" service, as defined in the new compiled, to be up. Barring
+"same" services, as defined in the new compiled, to be up. Barring
instructions from the conversion file, the service is "the same" if it has the
same name in the new compiled, no matter its type.
</p>
@@ -159,7 +159,7 @@ exist or that was previously down. </li>
<ul>
<li> Invoke <a href="s6-rc.html">s6-rc</a> to stop old services. </li>
<li> Update the live directory with the data from the new compiled.
-This is the critical part; s6-rc should not be interrupted at this point.
+This is the critical part; s6-rc-update should not be interrupted at this point.
It does its best to avoid risking leaving behind an inconsistent state,
but a 100% atomicity guarantee is impossible to achieve. </li>
<li> Adjust pipe names for the existing pipelines, if needed. </li>