summaryrefslogtreecommitdiffabout
authorSergey Poznyakoff <gray@gnu.org>2019-12-16 06:04:11 (GMT)
committer Sergey Poznyakoff <gray@gnu.org>2019-12-16 06:04:11 (GMT)
commit06031d3add92479fce6b02971a23ad5931ee26dd (patch) (side-by-side diff)
tree55cc44c9609a4f5c041fb780fb2d0db691845c3f
parent8296834f757ae2479327100acb41184c051f8850 (diff)
downloadslackupgrade-06031d3add92479fce6b02971a23ad5931ee26dd.tar.gz
slackupgrade-06031d3add92479fce6b02971a23ad5931ee26dd.tar.bz2
Fix typos
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--README2
-rw-r--r--slackupgrade2
-rw-r--r--slackupgrade.84
3 files changed, 4 insertions, 4 deletions
diff --git a/README b/README
index 5f6bef3..13c7fd4 100644
--- a/README
+++ b/README
@@ -20,7 +20,7 @@ Usage
=====
Before upgrade, please make sure you backup all sensitive data on your
-system. When upgrading a remote machine, it advisable to have a KVM
+system. When upgrading a remote machine, it is advisable to have a KVM
console attached to it, so that you can intervene if the box refuses
to boot.
diff --git a/slackupgrade b/slackupgrade
index d29d0ad..662b325 100644
--- a/slackupgrade
+++ b/slackupgrade
@@ -272,7 +272,7 @@ function version_gt() {
# Before, rename each file matching the pattern FILE~<N>, where <N> is a
# decimal digit, to FILE~<N+1>. Rename FILE~ to FILE~1.
#
-# Second argument, if prresent, enables the dry-run mode
+# Second argument, if present, enables the dry-run mode.
#
function backup() {
local dir=$(dirname $1)
diff --git a/slackupgrade.8 b/slackupgrade.8
index 724e592..8d88b58 100644
--- a/slackupgrade.8
+++ b/slackupgrade.8
@@ -204,12 +204,12 @@ on a separate line. Lines consist of two or more columns separated
with any amount of whitespace. Column one contains the name of the
package in the version \fIOLD\fR of Slackware. Column two contains
the name of the corresponding package in Slackware version \fINEW\fR.
-If the package was spli into several packages, additional packages can
+If the package was split into several packages, additional packages can
be listed on the same line.
.PP
Excessively long lines can be
split over several physical lines by using the traditional UNIX
-approach: prefix and each line that must be joined with the next one
+approach, by ending each line that must be joined with the next one
with a backslash immediately followed by a newline character.
.PP
Comments are introduced with the hash sign (\fB#\fR) and extend to the

Return to:

Send suggestions and report system problems to the System administrator.