Various fixes for typos found by lintian (#3705)

5 files changed, 5 insertions, 5 deletions

diff --git a/man/libudev.xml b/man/libudev.xml
index 7ef978463c..53b68dcc89 100644
--- a/man/libudev.xml
+++ b/man/libudev.xml
@@ -81,7 +81,7 @@
     <para>To introspect a local device on a system, a udev device
     object can be created via
     <citerefentry><refentrytitle>udev_device_new_from_syspath</refentrytitle><manvolnum>3</manvolnum></citerefentry>
-    and friends. The device object allows to query current state,
+    and friends. The device object allows one to query current state,
     read and write attributes and lookup properties of the device in
     question.</para>
 
diff --git a/man/sd_event_add_time.xml b/man/sd_event_add_time.xml
index 2c0bd0ba10..5496b71529 100644
--- a/man/sd_event_add_time.xml
+++ b/man/sd_event_add_time.xml
@@ -123,7 +123,7 @@
     regarding the various types of clocks. The <parameter>usec</parameter> parameter specifies the earliest time, in
     microseconds (µs), relative to the clock's epoch, when the timer shall be triggered. If a time already in the past
     is specified (including <constant>0</constant>), this timer source "fires" immediately and is ready to be
-    dispatched. If the paramater is specified as <constant>UINT64_MAX</constant> the timer event will never elapse,
+    dispatched. If the parameter is specified as <constant>UINT64_MAX</constant> the timer event will never elapse,
     which may be used as an alternative to explicitly disabling a timer event source with
     <citerefentry><refentrytitle>sd_event_source_set_enabled</refentrytitle><manvolnum>3</manvolnum></citerefentry>. The
     <parameter>accuracy</parameter> parameter specifies an additional accuracy value in µs specifying how much the
diff --git a/man/systemd-socket-activate.xml b/man/systemd-socket-activate.xml
index 5d7f157c72..2cf3a7d377 100644
--- a/man/systemd-socket-activate.xml
+++ b/man/systemd-socket-activate.xml
@@ -142,7 +142,7 @@
         <varname>FileDescriptorName=</varname> in socket unit files, and enables use of
         <citerefentry><refentrytitle>sd_listen_fds_with_names</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
         Multiple entries may be specifies using separate options or by separating names with colons
-        (<literal>:</literal>) in one option. In case more names are given than descriptors, superflous ones willl be
+        (<literal>:</literal>) in one option. In case more names are given than descriptors, superfluous ones willl be
         ignored. In case less names are given than descriptors, the remaining file descriptors will be unnamed.
         </para></listitem>
       </varlistentry>
diff --git a/man/systemd.special.xml b/man/systemd.special.xml
index 19ca6d6837..9d79315069 100644
--- a/man/systemd.special.xml
+++ b/man/systemd.special.xml
@@ -473,7 +473,7 @@
           <citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>3</manvolnum></citerefentry>
           and
           <citerefentry><refentrytitle>systemd-gpt-auto-generator</refentrytitle><manvolnum>3</manvolnum></citerefentry>
-          automatically setup the appropiate dependencies to make this happen.
+          automatically setup the appropriate dependencies to make this happen.
           </para>
         </listitem>
       </varlistentry>
diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml
index 0fa95e97a8..4fe140e4bc 100644
--- a/man/systemd.timer.xml
+++ b/man/systemd.timer.xml
@@ -76,7 +76,7 @@
 
     <para>Note that in case the unit to activate is already active at the time the timer elapses it is not restarted,
     but simply left running. There is no concept of spawning new service instances in this case. Due to this, services
-    with <varname>RemainAfterExit=</varname> set (which stay around continously even after the service's main process
+    with <varname>RemainAfterExit=</varname> set (which stay around continuously even after the service's main process
     exited) are usually not suitable for activation via repetitive timers, as they will only be activated once, and
     then stay around forever.</para>
   </refsect1>