diff --git a/cddl/usr.sbin/zfsd/zfsd.8 b/cddl/usr.sbin/zfsd/zfsd.8
index d6b0e1d4bd22..d668e0e8ee9e 100644
--- a/cddl/usr.sbin/zfsd/zfsd.8
+++ b/cddl/usr.sbin/zfsd/zfsd.8
@@ -1,184 +1,183 @@
 .\"-
 .\" Copyright (c) 2016 Allan Jude
 .\" All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
 .\" are met:
 .\" 1. Redistributions of source code must retain the above copyright
 .\"    notice, this list of conditions and the following disclaimer.
 .\" 2. Redistributions in binary form must reproduce the above copyright
 .\"    notice, this list of conditions and the following disclaimer in the
 .\"    documentation and/or other materials provided with the distribution.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
 .Dd February 20, 2024
 .Dt ZFSD 8
 .Os
 .Sh NAME
 .Nm zfsd
 .Nd ZFS fault management daemon
 .Sh SYNOPSIS
 .Nm
 .Op Fl d
 .Sh DESCRIPTION
 .Nm
 attempts to resolve ZFS faults that the kernel can't resolve by itself.
 It listens to
 .Xr devctl 4
 events, which are how the kernel notifies userland of events such as I/O
 errors and disk removals.
 .Nm
 attempts to resolve these faults by activating or deactivating hot spares
 and onlining offline vdevs.
 .Pp
 The following options are available:
 .Bl -tag -width indent
 .It Fl d
 Run in the foreground instead of daemonizing.
 .El
 .Pp
 System administrators never interact with
 .Nm
 directly.
 Instead, they control its behavior indirectly through zpool configuration.
 There are two ways to influence
 .Nm :
 assigning hot spares and setting pool properties.
 Currently, only the
 .Em autoreplace
 property has any effect.
 See
 .Xr zpool 8
 for details.
 .Pp
 .Nm
 will attempt to resolve the following types of fault:
 .Bl -tag -width a
 .It device removal
 When a leaf vdev disappears,
 .Nm
 will activate any available hot spare.
 .It device arrival
 When a new GEOM device appears,
 .Nm
 will attempt to read its ZFS label, if any.
 If it matches a previously removed vdev on an active pool,
 .Nm
 will online it.
 Once resilvering completes, any active hot spare will detach automatically.
 .Pp
 If the new device has no ZFS label but its physical path matches the
 physical path of a previously removed vdev on an active pool, and that
 pool has the autoreplace property set, then
 .Nm
 will replace the missing vdev with the newly arrived device.
 Once resilvering completes, any active hot spare will detach automatically.
 .It vdev degrade or fault events
 If a vdev becomes degraded or faulted,
 .Nm
 will activate any available hot spare.
 .It I/O errors
 By default, if a leaf vdev generates more than 50 I/O errors in a 60 second
 period, then
 .Nm
 will mark that vdev as
 .Em FAULTED .
 ZFS will no longer issue any I/Os to it.
 .Nm
 will activate a hot spare if one is available. The defaults can be changed by
 setting the
 .Em io_n
 and/or
 .Em io_t
 vdev properties. See
 .Xr vdevprops 7
 for details.
 .It I/O delays
 By default, if a leaf vdev generates more than delayed 8 I/O events in a 60
 second period, then
 .Nm
 will mark that vdev as
 .Em FAULTED .
 ZFS will no longer issue any I/Os to it.
 .Nm
 will activate a hot spare if one is available. The defaults can be changed by
 setting the
 .Em slow_io_n
 and/or
 .Em slow_io_t
 vdev properties. See
 .Xr vdevprops 7
 for details.
 .It Checksum errors
 By default, if a leaf vdev generates more than 50 checksum errors in a 60
 second period, then
 .Nm
 will mark that vdev as
 .Em DEGRADED .
 ZFS will still use it, but zfsd will also activate a hot spare if one is
 available. The defaults can be changed by setting the
 .Em checksum_n
 and/or
 .Em checksum_t
 vdev properties. See
 .Xr vdevprops 7
 for details.
 .It Spare addition
 If the system administrator adds a hot spare to a pool that is already degraded,
 .Nm
 will activate the spare.
 .It Resilver complete
 .Nm
 will detach any hot spare once a permanent replacement finishes resilvering.
 .It Physical path change
 If the physical path of an existing disk changes,
 .Nm
 will attempt to replace any missing disk with the same physical path,
 if its pool's autoreplace property is set.
 .El
 .Pp
 .Nm
 will log interesting events and its actions to syslog with facility
 .Em daemon
 and identity
 .Op zfsd .
-.El
 .Sh FILES
 .Bl -tag -width a -compact
 .It Pa /var/db/zfsd/cases
 When
 .Nm
 exits, it serializes any unresolved casefiles here,
 then reads them back in when next it starts up.
 .El
 .Sh SEE ALSO
 .Xr devctl 4 ,
 .Xr vdevprops 7 ,
 .Xr zpool 8
 .Sh HISTORY
 .Nm
 first appeared in
 .Fx 11.0 .
 .Sh AUTHORS
 .Nm
 was originally written by
 .An Justin Gibbs Aq Mt gibbs@FreeBSD.org
 and
 .An Alan Somers Aq Mt asomers@FreeBSD.org
 .Sh TODO
 In the future,
 .Nm
 should be able to resume a pool that became suspended due to device
 removals, if enough missing devices have returned.
diff --git a/share/man/man4/gve.4 b/share/man/man4/gve.4
index 9bb1be1b9a53..7dba99e68773 100644
--- a/share/man/man4/gve.4
+++ b/share/man/man4/gve.4
@@ -1,215 +1,213 @@
 .\" SPDX-License-Identifier: BSD-3-Clause
 .\"
 .\" Copyright (c) 2023 Google LLC
 .\"
 .\" Redistribution and use in source and binary forms, with or without modification,
 .\" are permitted provided that the following conditions are met:
 .\"
 .\" 1. Redistributions of source code must retain the above copyright notice, this
 .\"    list of conditions and the following disclaimer.
 .\"
 .\" 2. Redistributions in binary form must reproduce the above copyright notice,
 .\"    this list of conditions and the following disclaimer in the documentation
 .\"    and/or other materials provided with the distribution.
 .\"
 .\" 3. Neither the name of the copyright holder nor the names of its contributors
 .\"    may be used to endorse or promote products derived from this software without
 .\"    specific prior written permission.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
 .\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
 .\" DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
 .\" ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
 .\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
 .\" LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
 .\" ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
 .\" SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .Dd April 26, 2023
 .Dt GVE 4
 .Os
 .Sh NAME
 .Nm gve
 .Nd "Ethernet driver for Google Virtual NIC (gVNIC)"
 .Sh SYNOPSIS
 To compile this driver into the kernel,
 place the following lines in your
 kernel configuration file:
 .Bd -ragged -offset indent
 .Cd "device gve"
 .Ed
 .Pp
 Alternatively, to load the driver as a
 module at boot time, place the following line in
 .Xr loader.conf 5 :
 .Bd -literal -offset indent
 if_gve_load="YES"
 .Ed
 .Sh DESCRIPTION
 gVNIC is a virtual network interface designed specifically for Google Compute Engine (GCE).
 It is required to support per-VM Tier-1 networking performance, and for using certain VM shapes on GCE.
 .Pp
 .Nm
 is the driver for gVNIC.
 It supports the following features:
 .Pp
 .Bl -bullet -compact
 .It
 RX checksum offload
 .It
 TX chesksum offload
 .It
 TCP Segmentation Offload (TSO)
 .It
 Large Receive Offload (LRO) in software
 .It
 Jumbo frames
 .It
 Receive Side Scaling (RSS)
 .El
 .Pp
 For more information on configuring this device, see
 .Xr ifconfig 8 .
 .Sh HARDWARE
 .Nm
 binds to a single PCI device ID presented by gVNIC:
 .Pp
 .Bl -bullet -compact
 .It
 0x1AE0:0x0042
 .El
 .Sh DIAGNOSTICS
 The following messages are recorded during driver initialization:
 .Bl -diag
 .It "Enabled MSIX with %d vectors"
 .It "Configured device resources"
 .It "Successfully attached %s"
 .It "Deconfigured device resources"
 .El
 .Pp
 These messages are seen if driver initialization fails.
 Global (across-queues) allocation failures:
 .Bl -diag
 .It "Failed to configure device resources: err=%d"
 .It "No compatible queue formats"
 .It "Failed to allocate ifnet struct"
 .It "Failed to allocate admin queue mem"
 .It "Failed to alloc DMA mem for DescribeDevice"
 .It "Failed to allocate QPL page"
 .El
 .Pp
 irq and BAR allocation failures:
 .Bl -diag
 .It "Failed to acquire any msix vectors"
 .It "Tried to acquire %d msix vectors, got only %d"
 .It "Failed to setup irq %d for Tx queue %d "
 .It "Failed to setup irq %d for Rx queue %d "
 .It "Failed to allocate irq %d for mgmnt queue"
 .It "Failed to setup irq %d for mgmnt queue, err: %d"
 .It "Failed to allocate BAR0"
 .It "Failed to allocate BAR2"
 .It "Failed to allocate msix table"
 .El
 .Pp
 Rx queue-specific allocation failures:
 .Bl -diag
 .It "No QPL left for rx ring %d"
 .It "Failed to alloc queue resources for rx ring %d"
 .It "Failed to alloc desc ring for rx ring %d"
 .It "Failed to alloc data ring for rx ring %d"
 .El
 .Pp
 Tx queue-specific allocation failures:
 .Bl -diag
 .It "No QPL left for tx ring %d"
 .It "Failed to alloc queue resources for tx ring %d"
 .It "Failed to alloc desc ring for tx ring %d"
 .It "Failed to vmap fifo, qpl_id = %d"
 .El
-.El
 .Pp
 The following messages are recorded when the interface detach fails:
 .Bl -diag
 .It "Failed to deconfigure device resources: err=%d"
 .El
 .Pp
 If bootverbose is on, the following messages are recorded when the interface is being brought up:
 .Bl -diag
 .It "Created %d rx queues"
 .It "Created %d tx queues"
 .It "MTU set to %d"
 .El
 .Pp
 The following messages are recorded when the interface is being brought down:
 .Bl -diag
 .It "Destroyed %d rx queues"
 .It "Destroyed %d tx queues"
 .El
 .Pp
 These messages are seen if errors are encountered when bringing the interface up or down:
 .Bl -diag
 .It "Failed to destroy rxq %d, err: %d"
 .It "Failed to destroy txq %d, err: %d"
 .It "Failed to create rxq %d, err: %d"
 .It "Failed to create txq %d, err: %d"
 .It "Failed to set MTU to %d"
 .It "Invalid new MTU setting. new mtu: %d max mtu: %d min mtu: %d"
 .It "Cannot bring the iface up when detached"
 .It "Reached max number of registered pages %lu > %lu"
 .It "Failed to init lro for rx ring %d"
 .El
 .Pp
 These messages are seen if any admin queue command fails:
 .Bl -diag
 .It "AQ command(%u): failed with status %d"
 .It "AQ command(%u): unknown status code %d"
 .It "AQ commands timed out, need to reset AQ"
 .It "Unknown AQ command opcode %d"
 .El
 .Pp
 These messages are recorded when the device is being reset due to an error:
 .Bl -diag
 .It "Scheduling reset task!"
 .It "Waiting until admin queue is released."
 .It "Admin queue released"
 .El
 .Pp
 If it was the NIC that requested the reset, this message is recorded:
 .Bl -diag
 .It "Device requested reset"
 .El
 .Pp
 If the reset fails during the reinitialization phase, this message is recorded:
 .Bl -diag
 .It "Restore failed!"
 .El
 .Pp
 These two messages correspoond to the NIC alerting the driver to link state changes:
 .Bl -diag
 .It "Device link is up."
 .It "Device link is down."
 .El
 .Pp
 Apart from these messages, the driver exposes per-queue packet and error counters as sysctl nodes.
 Global (across queues) counters can be read using
 .Xr netstat 8 .
 .Sh LIMITATIONS
 .Nm
 does not support the transmission of VLAN-tagged packets.
 All VLAN-tagged traffic is dropped.
 .Sh SUPPORT
 Please email gvnic-drivers@google.com with the specifics of the issue encountered.
-.El
 .Sh SEE ALSO
 .Xr ifconfig 8 ,
 .Xr netstat 8
 .Sh HISTORY
 The
 .Nm
 device driver first appeared in
 .Fx 14.0 .
 .Sh AUTHORS
 The
 .Nm
 driver was written by Google.
diff --git a/share/man/man4/mem.4 b/share/man/man4/mem.4
index 5df074acc8f3..3132b7f3cf86 100644
--- a/share/man/man4/mem.4
+++ b/share/man/man4/mem.4
@@ -1,317 +1,316 @@
 .\" Copyright (c) 1991 The Regents of the University of California.
 .\" All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
 .\" are met:
 .\" 1. Redistributions of source code must retain the above copyright
 .\"    notice, this list of conditions and the following disclaimer.
 .\" 2. Redistributions in binary form must reproduce the above copyright
 .\"    notice, this list of conditions and the following disclaimer in the
 .\"    documentation and/or other materials provided with the distribution.
 .\" 3. Neither the name of the University nor the names of its contributors
 .\"    may be used to endorse or promote products derived from this software
 .\"    without specific prior written permission.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
 .\"	@(#)mem.4	5.3 (Berkeley) 5/2/91
 .\"
 .Dd March 24, 2024
 .Dt MEM 4
 .Os
 .Sh NAME
 .Nm mem ,
 .Nm kmem
 .Nd memory files
 .Sh SYNOPSIS
 .Cd "device mem"
 .Sh DESCRIPTION
 The special file
 .Pa /dev/mem
 is an interface to the physical memory of the computer.
 Byte offsets in this file are interpreted as physical memory addresses.
 Reading and writing this file is equivalent to reading and writing
 memory itself.
 Only offsets within the bounds of
 .Pa /dev/mem
 are allowed.
 .Pp
 Kernel virtual memory is accessed through the interface
 .Pa /dev/kmem
 in the same manner as
 .Pa /dev/mem .
 Only kernel virtual addresses that are currently mapped to memory are allowed.
 .Pp
 On ISA the I/O memory space begins at physical address 0x000a0000
 and runs to 0x00100000.
 The
 per-process data
 size
 for the current process
 is
 .Dv UPAGES
 long, and ends at virtual
 address 0xf0000000.
 .Sh IOCTL INTERFACE
 .Ss Address Properties
 The
 .Dv MEM_EXTRACT_PADDR
 ioctl can be used to look up the physical address and NUMA domain of a given
 virtual address in the calling process' address space.
 The request is described by
 .Bd -literal
 struct mem_extract {
 	uint64_t	me_vaddr;	/* input */
 	uint64_t	me_paddr;	/* output */
 	int		me_domain;	/* output */
 	int		me_state;	/* output */
 };
 .Ed
 .Pp
 The ioctl returns an error if the address is not valid.
 The information returned by
 .Dv MEM_EXTRACT_PADDR
 may be out of date by the time that the ioctl call returns.
 Specifically, concurrent system calls, page faults, or system page reclamation
 activity may have unmapped the virtual page or replaced the backing physical
 page before the ioctl call returns.
 Wired pages, e.g., those locked by
 .Xr mlock 2 ,
 will not be reclaimed by the system.
 .Pp
 The
 .Fa me_state
 field provides information about the state of the virtual page:
 .Bl -tag -width indent
 .It Dv ME_STATE_INVALID
 The virtual address is invalid.
 .It Dv ME_STATE_VALID
 The virtual address is valid but is not mapped at the time of the ioctl call.
 .It Dv ME_STATE_MAPPED
 The virtual address corresponds to a physical page mapping, and the
 .Fa me_paddr
 and
 .Fa me_domain
 fields are valid.
 .El
 .Ss Memory Ranges
 .Pp
 Several architectures allow attributes to be associated with ranges of physical
 memory.
 These attributes can be manipulated via
 .Fn ioctl
 calls performed on
 .Pa /dev/mem .
 Declarations and data types are to be found in
 .In sys/memrange.h .
 .Pp
 The specific attributes, and number of programmable ranges may vary between
 architectures.
 The full set of supported attributes is:
 .Bl -tag -width indent
 .It Dv MDF_UNCACHEABLE
 The region is not cached.
 .It Dv MDF_WRITECOMBINE
 Writes to the region may be combined or performed out of order.
 .It Dv MDF_WRITETHROUGH
 Writes to the region are committed synchronously.
 .It Dv MDF_WRITEBACK
 Writes to the region are committed asynchronously.
 .It Dv MDF_WRITEPROTECT
 The region cannot be written to.
 .El
 .Pp
 Memory ranges are described by
 .Bd -literal
 struct mem_range_desc {
 	uint64_t	mr_base;	/* physical base address */
 	uint64_t	mr_len;		/* physical length of region */
 	int		mr_flags;	/* attributes of region */
 	char		mr_owner[8];
 };
 .Ed
 .Pp
 In addition to the region attributes listed above, the following flags
 may also be set in the
 .Fa mr_flags
 field:
 .Bl -tag -width indent
 .It MDF_FIXBASE
 The region's base address cannot be changed.
 .It MDF_FIXLEN
 The region's length cannot be changed.
 .It MDF_FIRMWARE
 The region is believed to have been established by the system firmware.
 .It MDF_ACTIVE
 The region is currently active.
 .It MDF_BOGUS
 We believe the region to be invalid or otherwise erroneous.
 .It MDF_FIXACTIVE
 The region cannot be disabled.
 .It MDF_BUSY
 The region is currently owned by another process and may not be
 altered.
 .El
 .Pp
 Operations are performed using
 .Bd -literal
 struct mem_range_op {
 	struct mem_range_desc	*mo_desc;
 	int			mo_arg[2];
 };
 .Ed
 .Pp
 The
 .Dv MEMRANGE_GET
 ioctl is used to retrieve current memory range attributes.
 If
 .Va mo_arg[0]
 is set to 0, it will be updated with the total number of memory range
 descriptors.
 If greater than 0, the array at
 .Va mo_desc
 will be filled with a corresponding number of descriptor structures,
 or the maximum, whichever is less.
 .Pp
 The
 .Dv MEMRANGE_SET
 ioctl is used to add, alter and remove memory range attributes.
 A range
 with the
 .Dv MDF_FIXACTIVE
 flag may not be removed; a range with the
 .Dv MDF_BUSY
 flag may not be removed or updated.
 .Pp
 .Va mo_arg[0]
 should be set to
 .Dv MEMRANGE_SET_UPDATE
 to update an existing or establish a new range, or to
 .Dv MEMRANGE_SET_REMOVE
 to remove a range.
-.El
 .Ss Live Kernel Dumps
 .Pp
 The
 .Dv MEM_KERNELDUMP
 ioctl will initiate a kernel dump against the running system, the contents of
 which will be written to a process-owned file descriptor.
 The resulting dump output will be in minidump format.
 The request is described by
 .Bd -literal
 struct mem_livedump_arg {
 	int	fd;		/* input */
 	int	flags		/* input */
 	uint8_t	compression	/* input */
 };
 .Ed
 .Pp
 The
 .Va fd
 field is used to pass the file descriptor.
 .Pp
 The
 .Va flags
 field is currently unused and must be set to zero.
 .Pp
 The
 .Va compression
 field can be used to specify the desired compression to
 be applied to the dump output.
 The supported values are defined in
 .In sys/kerneldump.h ;
 that is,
 .Dv KERNELDUMP_COMP_NONE ,
 .Dv KERNELDUMP_COMP_GZIP ,
 or
 .Dv KERNELDUMP_COMP_ZSTD .
 .Pp
 Kernel dumps taken against the running system may have inconsistent kernel data
 structures due to allocation, deallocation, or modification of memory
 concurrent to the dump procedure.
 Thus, the resulting core dump is not guaranteed to be usable.
 A system under load is more likely to produce an inconsistent result.
 Despite this, live kernel dumps can be useful for offline debugging of certain
 types of kernel bugs, such as deadlocks, or in inspecting a particular part of
 the system's state.
 .Sh RETURN VALUES
 .Ss MEM_EXTRACT_PADDR
 The
 .Dv MEM_EXTRACT_PADDR
 ioctl always returns a value of zero.
 .Ss MEMRANGE_GET/MEMRANGE_SET
 .Bl -tag -width Er
 .It Bq Er EOPNOTSUPP
 Memory range operations are not supported on this architecture.
 .It Bq Er ENXIO
 No memory range descriptors are available (e.g., firmware has not enabled
 any).
 .It Bq Er EINVAL
 The memory range supplied as an argument is invalid or overlaps another
 range in a fashion not supported by this architecture.
 .It Bq Er EBUSY
 An attempt to remove or update a range failed because the range is busy.
 .It Bq Er ENOSPC
 An attempt to create a new range failed due to a shortage of hardware
 resources (e.g., descriptor slots).
 .It Bq Er ENOENT
 An attempt to remove a range failed because no range matches the descriptor
 base/length supplied.
 .It Bq Er EPERM
 An attempt to remove a range failed because the range is permanently
 enabled.
 .El
 .Ss MEM_KERNELDUMP
 .Bl -tag -width Er
 .It Bq Er EOPNOTSUPP
 Kernel minidumps are not supported on this architecture.
 .It Bq Er EPERM
 An attempt to begin the kernel dump failed because the calling thread lacks the
 .It Bq Er EBADF
 The supplied file descriptor was invalid, or does not have write permission.
 .It Bq Er EBUSY
 An attempt to begin the kernel dump failed because one is already in progress.
 .It Bq Er EINVAL
 An invalid or unsupported value was specified in
 .Va flags .
 .It Bq Er EINVAL
 An invalid or unsupported compression type was specified.
 .Dv PRIV_KMEM_READ
 privilege.
 .El
 .Sh FILES
 .Bl -tag -width /dev/kmem -compact
 .It Pa /dev/mem
 .It Pa /dev/kmem
 .El
 .Sh SEE ALSO
 .Xr kvm 3 ,
 .Xr memcontrol 8
 .Sh HISTORY
 The
 .Pa /dev/mem
 file appeared in
 .At v1
 and
 .Pa /dev/kmem
 in
 .At v5 .
 The ioctl interface for memory range attributes was added in
 .Fx 3.2 .
 .Sh BUGS
 Busy range attributes are not yet managed correctly.
 .Pp
 This device is required for all users of
 .Xr kvm 3
 to operate.
diff --git a/usr.sbin/pnfsdskill/pnfsdskill.8 b/usr.sbin/pnfsdskill/pnfsdskill.8
index a08492fdb966..97919bd65a83 100644
--- a/usr.sbin/pnfsdskill/pnfsdskill.8
+++ b/usr.sbin/pnfsdskill/pnfsdskill.8
@@ -1,76 +1,75 @@
 .\" Copyright (c) 2018 Rick Macklem
 .\"
 .\" Redistribution and use in source and binary forms, with or without
 .\" modification, are permitted provided that the following conditions
 .\" are met:
 .\" 1. Redistributions of source code must retain the above copyright
 .\"    notice, this list of conditions and the following disclaimer.
 .\" 2. Redistributions in binary form must reproduce the above copyright
 .\"    notice, this list of conditions and the following disclaimer in the
 .\"    documentation and/or other materials provided with the distribution.
 .\"
 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
 .Dd July 9, 2018
 .Dt PNFSDSKILL 8
 .Os
 .Sh NAME
 .Nm pnfsdskill
 .Nd
 disables a pNFS data storage server (DS)
 .Sh SYNOPSIS
 .Nm
 .Op Fl f
 .Ar mounted-on-DS-dir
 .Sh DESCRIPTION
 The
 .Nm
 command disables one DS when mirroring is enabled.
 If one mirrored DS is malfunctioning, a system administrator
 may use this command on the metadata server (MDS) to disable use of this mirror.
 This command must be used on the MDS and the
 .Ar mounted-on-DS-dir
 must be the exact pathname used when mounting the DS on the MDS.
 Normally this command will fail if there is no valid mirror for the DS
 available.
 .Pp
 The following option is available:
 .Bl -tag -width Ds
 .It Fl f
 This option forces the DS to be disabled even if there is no valid mirror
 for the DS available.
 It should only be used to allow the
 .Xr nfsd 8
 threads to be terminated.
 .El
 .Pp
 If this command fails with
 .Dq Device not configured
 (ENXIO), it probably
 means that the DS has already been disabled due to an error either detected
 by the MDS or reported to the MDS by a client.
 .Pp
 The pNFS service should continue to run normally so long as the number of
 operational DSs is at least as many as the level of mirroring.
-.El
 .Sh SEE ALSO
 .Xr nfsv4 4 ,
 .Xr pnfs 4 ,
 .Xr nfsd 8 ,
 .Xr pnfsdscopymr 8 ,
 .Xr pnfsdsfile 8
 .Sh HISTORY
 The
 .Nm
 command first appeared in
 .Fx 12.0 .