From abf41bc282cda25fb661e5a96e55468d1b091f8b Mon Sep 17 00:00:00 2001
From: Beniamino Galvani <bgalvani@redhat.com>
Date: Tue, 3 Oct 2023 11:10:35 +0200
Subject: [PATCH] man: improve NM-dispatcher man page

---
 man/NetworkManager-dispatcher.xml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/man/NetworkManager-dispatcher.xml b/man/NetworkManager-dispatcher.xml
index a8380991ab..f6e1d22d76 100644
--- a/man/NetworkManager-dispatcher.xml
+++ b/man/NetworkManager-dispatcher.xml
@@ -59,9 +59,9 @@
       device an operation just happened on, and second the action. For device actions,
       the interface is the name of the kernel interface suitable for IP configuration.
       Thus it is either VPN_IP_IFACE, DEVICE_IP_IFACE, or DEVICE_IFACE, as applicable.
-      For the <varname>hostname</varname> action the device name is always <literal>"none"</literal>.
-      For <varname>connectivity-change</varname> it is empty.
-      For <varname>dns-change</varname> it is empty.
+      For the <varname>hostname</varname> action the device name is always
+      <literal>"none"</literal>. For <varname>connectivity-change</varname> and
+      <varname>dns-change</varname> it is empty.
     </para>
     <para>The actions are:</para>
     <variablelist class="dispatcher-options">
@@ -169,7 +169,7 @@
             NetworkManager is configured to not manage resolv.conf (for example,
             via dns=none). In such case, the dispatch script can discover the
             DNS configuration provided by currently active connections by
-            looking at file /run/NetworkManager/resolv.conf
+            looking at file <filename>/run/NetworkManager/resolv.conf</filename>
         </para></listitem>
       </varlistentry>
     </variablelist>