Fix typos when "set up" is used as a verb

The noun is "setup" while the verb is "set up".

diff --git a/disk-utils/fsck.c b/disk-utils/fsck.c
index beccb17508f3eb3e3fe3c0c71b7a8dd88b7aa436..02ddaedae947f9e0d42e09799fd377f1c201d158 100644 (file)
--- a/disk-utils/fsck.c
+++ b/disk-utils/fsck.c
@@ -442,7 +442,7 @@ static struct libmnt_fs *add_dummy_fs(const char *device)
        }
 
        mnt_unref_fs(fs);
-       err(FSCK_EX_ERROR, _("failed to setup description for %s"), device);
+       err(FSCK_EX_ERROR, _("failed to set up description for %s"), device);
 }
 
 static void fs_interpret_type(struct libmnt_fs *fs)

diff --git a/libmount/src/context_mount.c b/libmount/src/context_mount.c
index c6d854f7a639b702d7cc99898a6e2c791f1c804e..2de6766cda53777f1ee83382b3235c473df79ee1 100644 (file)
--- a/libmount/src/context_mount.c
+++ b/libmount/src/context_mount.c
@@ -1584,7 +1584,7 @@ int mnt_context_get_mount_excode(
                        return MNT_EX_USAGE;
                case -MNT_ERR_LOOPDEV:
                        if (buf)
-                               snprintf(buf, bufsz, _("failed to setup loop device for %s"), src);
+                               snprintf(buf, bufsz, _("failed to set up loop device for %s"), src);
                        return MNT_EX_FAIL;
                case -MNT_ERR_LOOPOVERLAP:
                        if (buf)

diff --git a/libmount/src/hook_idmap.c b/libmount/src/hook_idmap.c
index 5095de1f6acd6941872c42c9c3ecee763ad4b7d1..821269f1e91add0d11c49ce18cd17d716336400f 100644 (file)
--- a/libmount/src/hook_idmap.c
+++ b/libmount/src/hook_idmap.c
@@ -492,7 +492,7 @@ done:
        return 0;
 
 err:
-       DBG(HOOK, ul_debugobj(hs, " failed to setup idmap"));
+       DBG(HOOK, ul_debugobj(hs, " failed to set up idmap"));
        free_hook_data(hd);
        free(buf);
        return -MNT_ERR_MOUNTOPT;

diff --git a/libmount/src/hook_loopdev.c b/libmount/src/hook_loopdev.c
index b72164535c5594e7c85afee575d01c3a34d71201..0bb97e59b4e1618774106c1d9a954b8f6bf7d18d 100644 (file)
--- a/libmount/src/hook_loopdev.c
+++ b/libmount/src/hook_loopdev.c
@@ -138,7 +138,7 @@ static int setup_loopdev(struct libmnt_context *cxt,
        if (!backing_file)
                return -EINVAL;
 
-       DBG(LOOP, ul_debugobj(cxt, "trying to setup device for %s", backing_file));
+       DBG(LOOP, ul_debugobj(cxt, "trying to set up device for %s", backing_file));
 
        if (mnt_optlist_is_rdonly(ol)) {
                DBG(LOOP, ul_debugobj(cxt, "enabling READ-ONLY flag"));
@@ -332,7 +332,7 @@ static int setup_loopdev(struct libmnt_context *cxt,
                        break;          /* success */
 
                if (loopdev || rc != -EBUSY) {
-                       DBG(LOOP, ul_debugobj(cxt, "failed to setup device"));
+                       DBG(LOOP, ul_debugobj(cxt, "failed to set up device"));
                        rc = -MNT_ERR_LOOPDEV;
                        goto done;
                }

diff --git a/sys-utils/losetup.8.adoc b/sys-utils/losetup.8.adoc
index cecc09618d514305d047054bbd0582fcbec5804a..54a825c63ea16edb67a11a791330d9992799959d 100644 (file)
--- a/sys-utils/losetup.8.adoc
+++ b/sys-utils/losetup.8.adoc
@@ -148,7 +148,7 @@ The *--remove* option completely removes the loop device node from the system us
 
 == NOTES
 
-Since version 2.37 *losetup* uses *LOOP_CONFIGURE* ioctl to setup a new loop device by one ioctl call. The old versions use *LOOP_SET_FD* and *LOOP_SET_STATUS64* ioctls to do the same.
+Since version 2.37 *losetup* uses *LOOP_CONFIGURE* ioctl to set up a new loop device by one ioctl call. The old versions use *LOOP_SET_FD* and *LOOP_SET_STATUS64* ioctls to do the same.
 
 == ENVIRONMENT
 

diff --git a/sys-utils/rtcwake.8.adoc b/sys-utils/rtcwake.8.adoc
index b118534c836d308599143ebdc2ddc65b3be63d40..5164a23a3789044a5defe2fb2287098035811392 100644 (file)
--- a/sys-utils/rtcwake.8.adoc
+++ b/sys-utils/rtcwake.8.adoc
@@ -24,7 +24,7 @@ This is normally used like the old *apmsleep* utility, to wake from a suspend st
 
 On some systems, this can also be used like *nvram-wakeup*, waking from states like ACPI S4 (suspend to disk). Not all systems have persistent media that are appropriate for such suspend modes.
 
-Note that alarm functionality depends on hardware; not every RTC is able to setup an alarm up to 24 hours in the future.
+Note that alarm functionality depends on hardware; not every RTC is able to set up an alarm up to 24 hours in the future.
 
 The suspend setup may be interrupted by active hardware; for example wireless USB input devices that continue to send events for some fraction of a second after the return key is pressed. *rtcwake* tries to avoid this problem and it waits to the terminal to settle down before entering a system sleep.
 

diff --git a/tests/expected/libmount/loop-o-loop-val-conflict b/tests/expected/libmount/loop-o-loop-val-conflict
index 0eb732214544b70df645ec560d166fe1c517d14e..faedb3b9bc1b877159d7d8bc5019c91fc5662a8b 100644 (file)
--- a/tests/expected/libmount/loop-o-loop-val-conflict
+++ b/tests/expected/libmount/loop-o-loop-val-conflict
@@ -1,2 +1,2 @@
-mount: <target> failed to setup loop device for <source>
+mount: <target> failed to set up loop device for <source>
 Success