From: David Joaquín Shourabi Porcel <david@djsp.eu>
Date: Fri, 12 Apr 2024 20:14:47 +0000 (+0200)
Subject: man: `systemd-nspawn(1)`: Fix some typos
X-Git-Tag: v257-rc1~297^2~1
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=f4e3c6e5b318d22a9c40144c6d52ae68a70c264c;p=thirdparty%2Fsystemd.git

man: `systemd-nspawn(1)`: Fix some typos
---

diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml
index 2645a6b217c..cd7d349b95c 100644
--- a/man/systemd-nspawn.xml
+++ b/man/systemd-nspawn.xml
@@ -369,7 +369,7 @@
       <varlistentry>
         <term><option>--read-only</option></term>
 
-        <listitem><para>Mount the container's root file system (and any other file systems container in the container
+        <listitem><para>Mount the container's root file system (and any other file systems contained in the container
         image) read-only. This has no effect on additional mounts made with <option>--bind=</option>,
         <option>--tmpfs=</option> and similar options. This mode is implied if the container image file or directory is
         marked read-only itself. It is also implied if <option>--volatile=</option> is used. In this case the container
@@ -404,7 +404,7 @@
         <filename>/efi/</filename> or <filename>/boot/</filename> are prohibited in case such a partition
         exists in the container image operated on, and even if <option>--volatile=state</option> is used the
         hypothetical file <filename index="false">/etc/foobar</filename> is potentially writable if
-        <option>--bind=/etc/foobar</option> if used to mount it from outside the read-only container
+        <option>--bind=/etc/foobar</option> is used to mount it from outside the read-only container
         <filename>/etc/</filename> directory.</para>
 
         <para>The <option>--ephemeral</option> option is closely related to this setting, and provides similar