Language fixes.

diff --git a/blog/data/2011-07-30-rcS.txt b/blog/data/2011-07-30-rcS.txt
index 6190cc22abbf6019f6d103bf594345f48e37e80b..c9ea24c826dedf201a11c3802787cebc1a21ce9f 100644 (file)
--- a/blog/data/2011-07-30-rcS.txt
+++ b/blog/data/2011-07-30-rcS.txt
@@ -11,10 +11,10 @@ runlevel 1.  One need to actually reboot to get the machine back to
 the expected state.  The other is that single user boot will sometimes
 run into problems because some of the subsystems are activated before
 the root login is presented, causing problems when trying to recover a
-machine.  A minor point is that moving more scripts out of rcS.d/ and
-into the other rc#.d/ directories will increase the amount of scripts
-that can run in parallel during boot, and thus increase the speed
-time.</p>
+machine from a problem in that subsystem.  A minor additional point is
+that moving more scripts out of rcS.d/ and into the other rc#.d/
+directories will increase the amount of scripts that can run in
+parallel during boot, and thus decrease the speed time.</p>
 
 <p>So, which scripts should start from rcS.d/.  In short, only the
 scripts that _have_ to execute before the root login prompt is
@@ -22,7 +22,7 @@ presented during a single user boot should go there.  Everything else
 should go into the numeric runlevels.  This means things like
 lm-sensors, fuse and x11-common should not run from rcS.d, but from
 the numeric runlevels.  Today in Debian, there are around 115 init.d
-scripts that are starte from rcS.d/, and most of them should be moved
+scripts that are started from rcS.d/, and most of them should be moved
 out.  Do your package have one of them?  Please help us make single
 user and runlevel 1 better by moving it.</p>
 
@@ -36,7 +36,7 @@ Debian systems working while scripts migrate and during upgrades, the
 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
 and the next ones can only be moved when their dependencies have been
-moved first.  This migration must be done sequencially while we ensure
+moved first.  This migration must be done sequentially while we ensure
 that the package system upgrade packages in the right order to keep
 the system state correct.  This will require some coordination when it
 comes to network related packages, but most of the packages with