Correct inconsistent spelling of terms and duplication.
Details
- Reviewers
ziaee - Group Reviewers
bhyve - Commits
- rG5819f8b285fc: bhyve.8: Fix consistency and terms in manpage
Diff Detail
- Repository
- rG FreeBSD src repository
- Lint
Lint Skipped - Unit
Tests Skipped - Build Status
Buildable 69426 Build 66309: arc lint + arc unit
Event Timeline
| usr.sbin/bhyve/bhyve.8 | ||
|---|---|---|
| 171 | For true consistency we actually need to standardize it the other way, the interface has been externally called fw_cfg since even before we got it, right? | |
Thanks michaelo!
| usr.sbin/bhyve/bhyve.8 | ||
|---|---|---|
| 715 | In the roff language, new sentences start on newlines. You can check the linter with mandoc -Tlint /here/is/the/manual. | |
| usr.sbin/bhyve/bhyve.8 | ||
|---|---|---|
| 681 | ||
| 714 | That said, I would suggest a more active voice here, for this sentence, something like: Only one active connection is allowed at any time. The TCP server will immediately close new connections while an existing connection is active. | |
| 1024 | This is the formatting consistently used in the NVMe 1.4b specification. | |
| 1179 | Using this syntax is fine, but I don't think it is ambiguous to use plain GB here and elsewhere. Memory sizing is always power-of-2, so memory/RAM sizes and address space sizes (e.g. the 64K window for VGA) are always power-of-2. (This is different from some other places like disk sizes where it is indeed ambiguous.) In particular, the syntax accepted for the command line doesn't accept the i, only GB or G (see expand_number(3)). | |
Addressed issues.
| usr.sbin/bhyve/bhyve.8 | ||
|---|---|---|
| 1179 | I didn't change any or the options, put only free form prose. | |