fix typo

diff --git a/man/udevadm.xml b/man/udevadm.xml
index b0e448e5687555b7993086d3145ec5c428c27000..5994abde8eae60619c176a05bc30a3ad83a40f11 100644 (file)
--- a/man/udevadm.xml
+++ b/man/udevadm.xml
@@ -791,7 +791,7 @@
       </title>
 
       <para><command>udevadm lock</command> takes an (advisory) exclusive lock(s) on a block device (or
-      multiple therof), as per <ulink url="https://systemd.io/BLOCK_DEVICE_LOCKING">Locking Block Device
+      multiple thereof), as per <ulink url="https://systemd.io/BLOCK_DEVICE_LOCKING">Locking Block Device
       Access</ulink> and invokes a program with the lock(s) taken. When the invoked program exits the lock(s)
       are automatically released.</para>
 

diff --git a/src/udev/udevadm-lock.c b/src/udev/udevadm-lock.c
index fae464704f4b1e659aa92848c386cf48eb6c1b50..3e5d7b356f2072532e6a94ec1690fd7dc0dbe137 100644 (file)
--- a/src/udev/udevadm-lock.c
+++ b/src/udev/udevadm-lock.c
@@ -41,7 +41,7 @@ static int help(void) {
 
         printf("%s [OPTIONS...] COMMAND\n"
                "%s [OPTIONS...] --print\n"
-               "\n%sLock a block device and run a comand.%s\n\n"
+               "\n%sLock a block device and run a command.%s\n\n"
                "  -h --help            Print this message\n"
                "  -V --version         Print version of the program\n"
                "  -d --device=DEVICE   Block device to lock\n"
@@ -247,7 +247,7 @@ static int lock_device(
 
                         /* flock() doesn't support a time-out. Let's fake one then. The traditional way to do
                          * this is via alarm()/setitimer()/timer_create(), but that's racy, given that the
-                         * SIGALRM might aleady fire between the alarm() and the flock() in which case the
+                         * SIGALRM might already fire between the alarm() and the flock() in which case the
                          * flock() is never cancelled and we lock up (this is a short time window, but with
                          * short timeouts on a loaded machine we might run into it, who knows?). Let's
                          * instead do the lock out-of-process: fork off a child that does the locking, and