man: don't claim BindPaths= file systems would remain "in memory", they are just...

Follow-up for: 947d836a6e86f1936250ff8e3c67fa33b92a597f

(I guess in the original patch authors usecase the root fs actually
*does* remain in memory, but that's a special case and does not belong
in the man pages this way).

diff --git a/man/systemd-soft-reboot.service.xml b/man/systemd-soft-reboot.service.xml
index 711cd6e3e987ab62c9f29e11dd03b693ede54e2b..f7908d3f032f05b5d17c8e3e3e32c81cf31db00e 100644 (file)
--- a/man/systemd-soft-reboot.service.xml
+++ b/man/systemd-soft-reboot.service.xml
@@ -119,9 +119,9 @@
     processes running during a soft-reboot operation requires disconnecting the service comprehensively from
     the rest of the OS, i.e. minimizing IPC and reducing sharing of resources with the rest of the OS. A
     possible mechanism to achieve this is the concept of <ulink
-    url="https://systemd.io/PORTABLE_SERVICES">Portable Services</ulink>, but make sure no resource from
-    the host's root filesystem is pinned via <varname>BindPaths=</varname> or similar unit settings,
-    otherwise the old root filesystem will be kept in memory as long as the unit is running.</para>
+    url="https://systemd.io/PORTABLE_SERVICES">Portable Services</ulink>, but make sure no resource from the
+    host's OS filesystems is pinned via <varname>BindPaths=</varname> or similar unit settings, otherwise the
+    old, originating filesystem will remain mounted as long as the unit is running.</para>
   </refsect1>
 
   <refsect1>