git: 3e5025ea3a5f - stable/14 - bhyve.8: Fix consistency and terms in manpage

The branch stable/14 has been updated by michaelo:

URL: https://cgit.FreeBSD.org/src/commit/?id=3e5025ea3a5f46d74bc1b9a2f793e25694e744c1

commit 3e5025ea3a5f46d74bc1b9a2f793e25694e744c1
Author:     Michael Osipov <michaelo@FreeBSD.org>
AuthorDate: 2025-12-21 16:41:41 +0000
Commit:     Michael Osipov <michaelo@FreeBSD.org>
CommitDate: 2025-12-26 10:48:19 +0000

    bhyve.8: Fix consistency and terms in manpage
    
    Correct inconsistent spelling of terms and duplication.
    
    Reviewed by:    ziaee
    MFC after:      3 days
    Differential Revision:  https://reviews.freebsd.org/D54332
    
    (cherry picked from commit 5819f8b285fc55a75e5dea56ffe73b376525150c)
---
 usr.sbin/bhyve/bhyve.8 | 61 +++++++++++++++++++++++++++-----------------------
 1 file changed, 33 insertions(+), 28 deletions(-)

diff --git a/usr.sbin/bhyve/bhyve.8 b/usr.sbin/bhyve/bhyve.8
index 90f34b3314f8..9f2934e27c6d 100644
--- a/usr.sbin/bhyve/bhyve.8
+++ b/usr.sbin/bhyve/bhyve.8
@@ -22,7 +22,7 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.Dd November 20, 2023
+.Dd December 23, 2025
 .Dt BHYVE 8
 .Os
 .Sh NAME
@@ -374,7 +374,7 @@ PCI 16550 serial device.
 .It Cm lpc
 LPC PCI-ISA bridge with COM1, COM2, COM3, and COM4 16550 serial ports,
 a boot ROM, and,
-optionally, a TPM module, a fwcfg type, and the debug/test device.
+optionally, a TPM module, a fw_cfg type, and the debug/test device.
 The LPC bridge emulation can only be configured on bus 0.
 .It Cm fbuf
 Raw framebuffer device attached to VNC server.
@@ -509,10 +509,10 @@ Disable emulation of guest trim requests via
 .Dv DIOCGDELETE
 requests.
 .It Li bootindex= Ns Ar index
-Add the device to the bootorder at
+Add the device to the boot order at
 .Ar index .
-A fwcfg file is used to specify the bootorder.
-The guest firmware may ignore or doesn't support this fwcfg file.
+A fw_cfg file is used to specify the boot order.
+The guest firmware may ignore or doesn't support this fw_cfg file.
 In that case, this feature doesn't work as expected.
 .El
 .Pp
@@ -532,10 +532,10 @@ are:
 Initiator ID to use when sending requests to specified CTL port.
 The default value is 0.
 .It Li bootindex= Ns Ar index
-Add the device to the bootorder at
+Add the device to the boot order at
 .Ar index .
-A fwcfg file is used to specify the bootorder.
-The guest firmware may ignore or doesn't support this fwcfg file.
+A fw_cfg file is used to specify the boot order.
+The guest firmware may ignore or not support this fw_cfg file.
 In that case, this feature doesn't work as expected.
 .El
 .Pp
@@ -611,10 +611,11 @@ address space, and any modifications the guest makes will be saved
 to that file.
 .El
 .Pp
-Fwcfg types:
+fw_cfg types:
 .Bl -tag -width 10n
 .It Ar fwcfg
-The fwcfg interface is used to pass information such as the CPU count or ACPI tables to the guest firmware.
+The fw_cfg interface is used to pass information such as the CPU count
+or ACPI tables to the guest firmware.
 Supported values are
 .Ql bhyve
 and
@@ -628,10 +629,13 @@ is used, bhyve's fwctl interface is used.
 It currently reports only the CPU count to the guest firmware.
 The
 .Ql qemu
-option uses QEMU's fwcfg interface.
-This interface is widely used and allows user-defined information to be passed to the guest.
-It is used for passing the CPU count, ACPI tables, a boot order and many other things to the guest.
-Some operating systems such as Fedora CoreOS can be configured by qemu's fwcfg interface as well.
+option uses QEMU's fw_cfg interface.
+This interface is widely used and allows user-defined information to
+be passed to the guest.
+It is used for passing the CPU count, ACPI tables, a boot order and
+many other things to the guest.
+Some operating systems such as Fedora CoreOS can be configured by
+QEMU's fw_cfg interface as well.
 .El
 .Pp
 Pass-through device backends:
@@ -667,10 +671,10 @@ Add
 as option ROM to the PCI device.
 The ROM will be loaded by firmware and should be capable of initializing the device.
 .It Li bootindex= Ns Ar index
-Add the device to the bootorder at
+Add the device to the boot order at
 .Ar index .
-A fwcfg file is used to specify the bootorder.
-The guest firmware may ignore or doesn't support this fwcfg file.
+A fw_cfg file is used to specify the boot order.
+The guest firmware may ignore or doesn't support this fw_cfg file.
 In that case, this feature doesn't work as expected.
 .El
 .Pp
@@ -678,7 +682,7 @@ Guest memory must be wired using the
 .Fl S
 option when a pass-through device is configured.
 .Pp
-The host device must have been reserved at boot-time using the
+The host device must have been reserved at boot time using the
 .Va pptdevs
 loader variable as described in
 .Xr vmm 4 .
@@ -793,7 +797,7 @@ standard PCI devices with BAR addressing, but may also
 implicitly decode legacy VGA I/O space
 .Pq Ad 0x3c0-3df
 and memory space
-.Pq 64KB at Ad 0xA0000 .
+.Pq 64 KiB at Ad 0xA0000 .
 The default
 .Cm io
 option should be used for guests that attempt to issue BIOS calls which result
@@ -876,7 +880,7 @@ Serial number with maximum 20 characters.
 .It Cm eui64
 IEEE Extended Unique Identifier (8 byte value).
 .It Cm dsm
-DataSet Management support.
+Dataset Management support.
 Supported values are:
 .Cm auto , enable ,
 and
@@ -899,14 +903,15 @@ Configuration options are defined as follows:
 .Bl -tag -width 10n
 .It Cm nmrr
 Nominal Media Rotation Rate, known as RPM.
-Value 1 will indicate device as Solid State Disk.
-Default value is 0, not report.
+A value of 1 indicates that the device is a solid state drive, i.e.,
+non-rotational.
+Default value is 0.
 .It Cm ser
-Serial Number with maximum 20 characters.
+Serial number with maximum 20 characters.
 .It Cm rev
-Revision Number with maximum 8 characters.
+Revision number with maximum 8 characters.
 .It Cm model
-Model Number with maximum 40 characters.
+Model number with maximum 40 characters.
 .El
 .Pp
 HD Audio device backends:
@@ -1028,7 +1033,7 @@ or a similar boot loader before
 can be run.
 Otherwise, the boot loader is not needed.
 .Pp
-To run a virtual machine with 1GB of memory, two virtual CPUs, a virtio
+To run a virtual machine with 1 GiB of memory, two virtual CPUs, a virtio
 block device backed by the
 .Pa /my/image
 filesystem image, and a serial port for the console:
@@ -1037,7 +1042,7 @@ bhyve -c 2 -s 0,hostbridge -s 1,lpc -s 2,virtio-blk,/my/image \\
   -l com1,stdio -A -H -P -m 1G vm1
 .Ed
 .Pp
-Run a 24GB single-CPU virtual machine with three network ports, one of which
+Run a 24 GiB single-CPU virtual machine with three network ports, one of which
 has a MAC address specified:
 .Bd -literal -offset indent
 bhyve -s 0,hostbridge -s 1,lpc -s 2:0,virtio-net,tap0 \\
@@ -1047,7 +1052,7 @@ bhyve -s 0,hostbridge -s 1,lpc -s 2:0,virtio-net,tap0 \\
   -A -H -P -m 24G bigvm
 .Ed
 .Pp
-Run an 8GB quad-CPU virtual machine with 8 AHCI SATA disks, an AHCI ATAPI
+Run an 8 GiB quad-CPU virtual machine with 8 AHCI SATA disks, an AHCI ATAPI
 CD-ROM, a single virtio network port, an AMD hostbridge, and the console
 port connected to an
 .Xr nmdm 4