Asciidoc: Incorporate latest changes in rfkill.8 and umount.8

diff --git a/sys-utils/rfkill.8.adoc b/sys-utils/rfkill.8.adoc
index 1963bf4ee1e491aaf12d49f574d8cc14a9f99f57..30ae74d37de78be051711ca2151d9b000c757a44 100644 (file)
--- a/sys-utils/rfkill.8.adoc
+++ b/sys-utils/rfkill.8.adoc
@@ -62,6 +62,9 @@ The default output is subject to change. So whenever possible, you should avoid
 **unblock id**|*type* [...]::
   Enable the corresponding device. If the device is hard-blocked, for example via a hardware switch, it will remain unavailable though it is now soft-unblocked.
 
+**toggle id**|*type* [...]::
+  Enable or disable the the corresponding device.
+
 == EXAMPLE
 ....
   rfkill --output ID,TYPE

diff --git a/sys-utils/umount.8.adoc b/sys-utils/umount.8.adoc
index e9e90850da51cc0c0e3840c87f452e9b03f5c1eb..4201fe13bea8a0210a970f73056281a9a7ddb304 100644 (file)
--- a/sys-utils/umount.8.adoc
+++ b/sys-utils/umount.8.adoc
@@ -100,7 +100,7 @@ Note that a filesystem cannot be unmounted when it is 'busy' - for example, when
   Suppress "not mounted" error messages.
 
 *-R*, *--recursive*::
-  Recursively unmount each specified directory. Recursion for each directory will stop if any unmount operation in the chain fails for any reason. The relationship between mountpoints is determined by _/proc/self/mountinfo_ entries. The filesystem must be specified by mountpoint path; a recursive unmount by device name (or UUID) is unsupported.
+  Recursively unmount each specified directory. Recursion for each directory will stop if any unmount operation in the chain fails for any reason. The relationship between mountpoints is determined by _/proc/self/mountinfo_ entries. The filesystem must be specified by mountpoint path; a recursive unmount by device name (or UUID) is unsupported. Since version 2.37 it umounts also all over-mounted filesystems (more filesystems on the same mountpoint).
 
 *-r*, *--read-only*::
   When an unmount fails, try to remount the filesystem read-only.