diff --git a/man/sd_bus_process.xml b/man/sd_bus_process.xml
index f16b30ec6c..8e142dd97a 100644
--- a/man/sd_bus_process.xml
+++ b/man/sd_bus_process.xml
@@ -41,14 +41,14 @@
   <refsect1>
     <title>Description</title>
 
-    <para><function>sd_bus_process()</function> drives the connection between the client and the message bus. That is,
-    it handles connecting, authentication, and message processing. When invoked pending I/O work is executed, and
-    queued incoming messages are dispatched to registered callbacks. Each time it is invoked a single operation is
-    executed. It returns zero when no operations were pending and positive if a message was processed. When zero is
-    returned the caller should synchronously poll for I/O events before calling into
-    <function>sd_bus_process()</function> again. For that either use the simple, synchronous
-    <citerefentry><refentrytitle>sd_bus_wait</refentrytitle><manvolnum>3</manvolnum></citerefentry> call, or hook up
-    the bus connection object to an external or manual event loop using
+    <para><function>sd_bus_process()</function> drives the connection between the client and the message bus.
+    That is, it handles connecting, authentication, and processing of messages. When invoked, pending I/O
+    work is executed, and queued incoming messages are dispatched to registered callbacks. Each time it is
+    invoked a single operation is executed. It returns zero when no operations were pending and positive if a
+    message was processed. When zero is returned the caller should poll for I/O events before calling into
+    <function>sd_bus_process()</function> again. For that either use the simple, blocking
+    <citerefentry><refentrytitle>sd_bus_wait</refentrytitle><manvolnum>3</manvolnum></citerefentry> call, or
+    hook up the bus connection object to an external or manual event loop using
     <citerefentry><refentrytitle>sd_bus_get_fd</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
     </para>
 
diff --git a/man/systemd.service.xml b/man/systemd.service.xml
index 123f1db30d..b43ec14c37 100644
--- a/man/systemd.service.xml
+++ b/man/systemd.service.xml
@@ -1421,9 +1421,9 @@
     systems using split <filename>/usr/bin/</filename> and <filename>/bin/</filename> directories, and their
     <filename>sbin/</filename> counterparts on systems using split <filename>bin/</filename> and
     <filename>sbin/</filename>. It is thus safe to use just the executable name in case of executables
-    located in any of the "standard" directories, and an absolute path must be used in other cases. Using an
-    absolute path is recommended to avoid ambiguity. Hint: this search path may be queried using
-    <command>systemd-path search-binaries-default</command>.</para>
+    located in any of the "standard" directories, and an absolute path must be used in other cases.
+    Hint: this search path may be queried using <command>systemd-path search-binaries-default</command>.
+    </para>
 
     <para>The command line accepts <literal>%</literal> specifiers as described in
     <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>