Correct "umount" to "unmount" in a couple of places

This is admittedly a nitpicky change, but `umount` is the command that
performs an *unmount*. So if we are talking about unmounting something
we should phrase it that way.

Signed-off-by: Simon Howard <fraggle@gmail.com>
Reviewed-by: Tony Hutter <hutter2@llnl.gov>
Reviewed-by: Alexander Motin <mav@FreeBSD.org>
This commit is contained in:
Simon Howard 2025-03-12 19:24:57 +00:00 committed by Tony Hutter
parent 1d4505d7a1
commit e759a86fa5
2 changed files with 2 additions and 2 deletions

View File

@ -1329,7 +1329,7 @@ as it was before.
Controls whether the file system should be mounted with
.Sy nbmand
.Pq Non-blocking mandatory locks .
Changes to this property only take effect when the file system is umounted and
Changes to this property only take effect when the file system is unmounted and
remounted.
This was only supported by Linux prior to 5.15, and was buggy there,
and is not supported by

View File

@ -206,7 +206,7 @@ diff subcommand Allows lookup of paths within a dataset given an object number,
hold subcommand Allows adding a user hold to a snapshot
load-key subcommand Allows loading and unloading of encryption key (see \fBzfs load-key\fR and \fBzfs unload-key\fR).
change-key subcommand Allows changing an encryption key via \fBzfs change-key\fR.
mount subcommand Allows mounting/umounting ZFS datasets
mount subcommand Allows mounting/unmounting ZFS datasets
promote subcommand Must also have the \fBmount\fR and \fBpromote\fR ability in the origin file system
receive subcommand Must also have the \fBmount\fR and \fBcreate\fR ability, required for \fBzfs receive -F\fR (see also \fBreceive:append\fR for limited, non forced receive)
release subcommand Allows releasing a user hold which might destroy the snapshot