From 9ca09aa020aa898c5e13d2e1d9da9ac010c88fa3 Mon Sep 17 00:00:00 2001
From: Hiroyuki Yasuhara <h.yasuhara@fujitsu.com>
Date: Tue, 3 Mar 2026 16:05:14 +0900
Subject: [PATCH] cloud-setup/man: fix typo in `man nm-cloud-setup`

---
 man/nm-cloud-setup.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/man/nm-cloud-setup.xml b/man/nm-cloud-setup.xml
index af98b592ff..efbfc7668f 100644
--- a/man/nm-cloud-setup.xml
+++ b/man/nm-cloud-setup.xml
@@ -143,7 +143,7 @@
       script is to automatically pick up changes to the network.</para>
 
       <para>The dispatcher script will do nothing, unless the systemd service is
-      enabled. To use the dispatcher script you should therefor run
+      enabled. To use the dispatcher script you should therefore run
       <command>systemctl enable nm-cloud-setup.service</command> once.</para>
     </refsect2>
 
@@ -197,7 +197,7 @@
     <para>Enable debug logging by setting <literal>NM_CLOUD_SETUP_LOG</literal> environment variable to <literal>TRACE</literal>.</para>
     <para>In the common case where nm-cloud-setup is running as systemd service, this can be done via <command>systemctl edit nm-cloud-setup.service</command>
     and add <literal>Environment=NM_CLOUD_SETUP_LOG=TRACE</literal> to the <literal>[Service]</literal> section. Afterwards, the log can
-    be found in syslog via <literal>journalctl</literal>. You may also want to enable debug logging in NetworkManager as descibed
+    be found in syslog via <literal>journalctl</literal>. You may also want to enable debug logging in NetworkManager as described
     in the DEBUGGING section in <link linkend='NetworkManager'><citerefentry><refentrytitle>NetworkManager</refentrytitle><manvolnum>5</manvolnum></citerefentry></link>
     manual. When sharing logs, it's best to share complete logs and not preemptively filter for NetworkManager or nm-cloud-setup logs.</para>
   </refsect1>