doc: more spelling fixes

diff --git a/man/portablectl.xml b/man/portablectl.xml
index 1ed57e861acbbf1d452e199c8d6399cdc0f878b2..91c048e009f57e44ad54f9fdc29012f869b810cf 100644 (file)
--- a/man/portablectl.xml
+++ b/man/portablectl.xml
@@ -196,7 +196,7 @@
 
         <para>By default all unit files whose names start with a prefix generated from the image's file name are copied
         out. Specifically, the prefix is determined from the image file name with any suffix such as
-        <filename>.raw</filename> removed, truncated at the first occurence of and underscore character
+        <filename>.raw</filename> removed, truncated at the first occurrence of and underscore character
         (<literal>_</literal>), if there is one. The underscore logic is supposed to be used to versioning so that the
         an image file <filename>foobar_47.11.raw</filename> will result in a unit file matching prefix of
         <filename>foobar</filename>. This prefix is then compared with all unit files names contained in the image in
@@ -269,7 +269,7 @@
               </row>
               <row>
                 <entry><option>attached-runtime</option></entry>
-                <entry>Like <option>attached</option>, but the the unit files have been made available transiently only, i.e. the <command>attach</command> command has been invoked with the <option>--runtime</option> option.</entry>
+                <entry>Like <option>attached</option>, but the unit files have been made available transiently only, i.e. the <command>attach</command> command has been invoked with the <option>--runtime</option> option.</entry>
               </row>
               <row>
                 <entry><option>enabled</option></entry>
@@ -306,12 +306,12 @@
         <term><command>remove</command> <replaceable>IMAGE</replaceable>…</term>
 
         <listitem><para>Removes one or more portable service images. Note that this command will only remove the
-        specified image path itself — it it refers to a symbolic link then the symbolic link is removed and not the
+        specified image path itself — it refers to a symbolic link then the symbolic link is removed and not the
         image it points to.</para></listitem>
       </varlistentry>
 
       <varlistentry>
-        <term><command>set-limit</command> [<replaceable>NAME</replaceable>] <replaceable>BYTES</replaceable></term>
+        <term><command>set-limit</command> [<replaceable>IMAGE</replaceable>] <replaceable>BYTES</replaceable></term>
 
         <listitem><para>Sets the maximum size in bytes that a specific portable service image, or all images, may grow
         up to on disk (disk quota). Takes either one or two parameters. The first, optional parameter refers to a

diff --git a/man/sd_bus_request_name.xml b/man/sd_bus_request_name.xml
index 5da6e2e6267e9a4dbf286c1c8dce79fbf369a3b7..1b76fe133a523b8ec4d483d25eddcfed3a341ca0 100644 (file)
--- a/man/sd_bus_request_name.xml
+++ b/man/sd_bus_request_name.xml
@@ -111,7 +111,7 @@
     <para><function>sd_bus_request_name()</function> operates in a synchronous fashion: a message requesting the name
     is sent to the bus broker, and the call waits until the broker responds.</para>
 
-    <para><function>sd_bus_request_name_async()</function> is an asynchronous version of of
+    <para><function>sd_bus_request_name_async()</function> is an asynchronous version of
     <function>sd_bus_release_name()</function>. Instead of waiting for the request to complete, the request message is
     enqueued. The specified <parameter>callback</parameter> will be called when the broker's response is received. If
     the parameter is specified as <constant>NULL</constant> a default implementation is used instead which will

diff --git a/man/sd_bus_slot_set_floating.xml b/man/sd_bus_slot_set_floating.xml
index ae733e95de13325199fa32593719476b3c178504..a2a134e9f418d05b8f9486a7f46c684a98028fc5 100644 (file)
--- a/man/sd_bus_slot_set_floating.xml
+++ b/man/sd_bus_slot_set_floating.xml
@@ -50,7 +50,7 @@
     itself and is freed automatically when the bus object is freed. Regular (i.e. non-floating) bus slot objects keep
     the bus referenced, hence the bus object remains allocated at least as long as there remains at least one
     referenced bus slot object around. The floating state hence controls the direction of referencing between the bus
-    object and the bus slot objects: if floating the bus pins the the bus slot, and otherwise the bus slot pins the bus
+    object and the bus slot objects: if floating the bus pins the bus slot, and otherwise the bus slot pins the bus
     objects. Use <function>sd_bus_slot_set_floating()</function> to switch between both modes: if the
     <parameter>b</parameter> parameter is zero, the slot object is considered floating, otherwise it is made a regular
     (non-floating) slot object.</para>