diff options
author | brueffer <brueffer@FreeBSD.org> | 2015-08-12 11:56:19 +0000 |
---|---|---|
committer | brueffer <brueffer@FreeBSD.org> | 2015-08-12 11:56:19 +0000 |
commit | a00534bfebff3ae3ad1b4bdfce62355d4347541d (patch) | |
tree | 092913eebbfeace253b20e892cfc0da2e7a65900 /share | |
parent | cd3dfbae4efb7ab58027deeeab317b5726799d59 (diff) | |
download | FreeBSD-src-a00534bfebff3ae3ad1b4bdfce62355d4347541d.zip FreeBSD-src-a00534bfebff3ae3ad1b4bdfce62355d4347541d.tar.gz |
Fix mandoc warnings/errors.
MFC after: 1 week
Diffstat (limited to 'share')
-rw-r--r-- | share/man/man4/cloudabi.4 | 3 | ||||
-rw-r--r-- | share/man/man4/ctl.4 | 1 | ||||
-rw-r--r-- | share/man/man4/em.4 | 1 | ||||
-rw-r--r-- | share/man/man4/gre.4 | 1 | ||||
-rw-r--r-- | share/man/man4/hptiop.4 | 3 | ||||
-rw-r--r-- | share/man/man4/man4.i386/wl.4 | 4 | ||||
-rw-r--r-- | share/man/man4/ng_btsocket.4 | 14 | ||||
-rw-r--r-- | share/man/man4/siftr.4 | 2 | ||||
-rw-r--r-- | share/man/man4/snp.4 | 2 | ||||
-rw-r--r-- | share/man/man4/uftdi.4 | 2 | ||||
-rw-r--r-- | share/man/man4/vt.4 | 4 | ||||
-rw-r--r-- | share/man/man7/release.7 | 1 | ||||
-rw-r--r-- | share/man/man8/nanobsd.8 | 2 | ||||
-rw-r--r-- | share/man/man8/uefi.8 | 4 | ||||
-rw-r--r-- | share/man/man8/yp.8 | 11 | ||||
-rw-r--r-- | share/man/man9/PCI_IOV_ADD_VF.9 | 2 | ||||
-rw-r--r-- | share/man/man9/PCI_IOV_INIT.9 | 2 | ||||
-rw-r--r-- | share/man/man9/altq.9 | 2 | ||||
-rw-r--r-- | share/man/man9/ifnet.9 | 8 |
19 files changed, 36 insertions, 33 deletions
diff --git a/share/man/man4/cloudabi.4 b/share/man/man4/cloudabi.4 index 050e8c0..1986735 100644 --- a/share/man/man4/cloudabi.4 +++ b/share/man/man4/cloudabi.4 @@ -99,5 +99,4 @@ cloudlibc on GitHub: CloudABI support first appeared in .Fx 11.0 . .Sh AUTHORS -Nuxi: -.Pa https://nuxi.nl/ . +.An Nuxi : Pa https://nuxi.nl/ . diff --git a/share/man/man4/ctl.4 b/share/man/man4/ctl.4 index 239bad9..5a852d0 100644 --- a/share/man/man4/ctl.4 +++ b/share/man/man4/ctl.4 @@ -119,6 +119,7 @@ In the event that there is no response within that time the session gets forcibly terminated. Set to 0 to disable sending NOP-In PDUs. Defaults to 5. +.El .Sh SEE ALSO .Xr ctladm 8 , .Xr ctld 8 , diff --git a/share/man/man4/em.4 b/share/man/man4/em.4 index 5b80ed6..a9fd11f 100644 --- a/share/man/man4/em.4 +++ b/share/man/man4/em.4 @@ -307,5 +307,4 @@ The driver was written by .An Intel Corporation Aq Mt freebsd@intel.com . .Sh BUGS -.Pp Activating EM_MULTIQUEUE support requires MSI-X features. diff --git a/share/man/man4/gre.4 b/share/man/man4/gre.4 index 1b99e4d..3e6520c 100644 --- a/share/man/man4/gre.4 +++ b/share/man/man4/gre.4 @@ -154,7 +154,6 @@ ifconfig greN create ifconfig greN inet 198.51.100.1 203.0.113.1 ifconfig greN inet tunnel 198.51.100.1 203.0.113.1 tunnelfib 1 .Ed -.Pp .Sh NOTES The MTU of .Nm diff --git a/share/man/man4/hptiop.4 b/share/man/man4/hptiop.4 index fdd6d04..6d4a4a4 100644 --- a/share/man/man4/hptiop.4 +++ b/share/man/man4/hptiop.4 @@ -135,4 +135,5 @@ device driver first appeared in .Sh AUTHORS The .Nm -driver was written by HighPoint Technologies, Inc. +driver was written by +.An HighPoint Technologies, Inc. diff --git a/share/man/man4/man4.i386/wl.4 b/share/man/man4/man4.i386/wl.4 index a1eacda..e697d23 100644 --- a/share/man/man4/man4.i386/wl.4 +++ b/share/man/man4/man4.i386/wl.4 @@ -165,7 +165,9 @@ ported the Mach drivers to BSDI. ported them to .Fx 2.1 . .An Michael Smith -ported the wl driver only to 2.2.2. +ported the +.Nm +driver only to 2.2.2. Jim and Michael have been maintaining them. The current state of the driver is NOT ANYONE'S diff --git a/share/man/man4/ng_btsocket.4 b/share/man/man4/ng_btsocket.4 index 103497a..27c77ad 100644 --- a/share/man/man4/ng_btsocket.4 +++ b/share/man/man4/ng_btsocket.4 @@ -45,8 +45,8 @@ module implements three Netgraph node types. Each type in its turn implements one protocol within .Dv PF_BLUETOOTH domain. -.Sh Dv BLUETOOTH_PROTO_HCI Sh protocol -.Ss Dv SOCK_RAW Ss HCI sockets +.Sh Dv BLUETOOTH_PROTO_HCI protocol +.Ss Dv SOCK_RAW HCI sockets Implemented by .Nm btsock_hci_raw Netgraph type. @@ -147,7 +147,7 @@ level can be used to obtain via or change via .Xr setsockopt 2 raw HCI socket's filter. -.Sh Dv BLUETOOTH_PROTO_L2CAP Sh protocol +.Sh Dv BLUETOOTH_PROTO_L2CAP protocol The Bluetooth L2CAP socket address is defined as follows: .Bd -literal -offset indent /* Bluetooth version of struct sockaddr for L2CAP sockets */ @@ -158,7 +158,7 @@ struct sockaddr_l2cap { bdaddr_t l2cap_bdaddr; /* address */ }; .Ed -.Ss Dv SOCK_RAW Ss L2CAP sockets +.Ss Dv SOCK_RAW L2CAP sockets Implemented by .Nm btsock_l2c_raw Netgraph type. @@ -204,7 +204,7 @@ The variable, that can be examined and set via .Xr sysctl 8 , controls the control request timeout (in seconds) for raw L2CAP sockets. -.Ss Dv SOCK_SEQPACKET Ss L2CAP sockets +.Ss Dv SOCK_SEQPACKET L2CAP sockets Implemented by .Nm btsock_l2c Netgraph type. @@ -264,7 +264,7 @@ Get (set) value of the flush timeout. Not implemented. .Ef .El -.Sh Dv BLUETOOTH_PROTO_RFCOMM Sh protocol +.Sh Dv BLUETOOTH_PROTO_RFCOMM protocol The Bluetooth RFCOMM socket address is defined as follows: .Bd -literal -offset indent /* Bluetooth version of struct sockaddr for RFCOMM sockets */ @@ -275,7 +275,7 @@ struct sockaddr_rfcomm { uint8_t rfcomm_channel; /* channel */ }; .Ed -.Ss Dv SOCK_STREAM Ss RFCOMM sockets +.Ss Dv SOCK_STREAM RFCOMM sockets Note that RFCOMM sockets do not have associated Netgraph node type. RFCOMM sockets are implemented as additional layer on top of L2CAP sockets. RFCOMM sockets are either diff --git a/share/man/man4/siftr.4 b/share/man/man4/siftr.4 index 7fe3c85..7afa279 100644 --- a/share/man/man4/siftr.4 +++ b/share/man/man4/siftr.4 @@ -345,7 +345,7 @@ network interface card and drivers being used. .Bl -tag -offset indent -width Va .It Va 28 Flow type for the connection. -Flowtype defines which protocol fields are hashed to produce the flowid. +Flowtype defines which protocol fields are hashed to produce the flowid. A complete listing is available in .Pa sys/mbuf.h under diff --git a/share/man/man4/snp.4 b/share/man/man4/snp.4 index 48e10a9..36816bd 100644 --- a/share/man/man4/snp.4 +++ b/share/man/man4/snp.4 @@ -85,7 +85,7 @@ driver was rewritten to work with the replaced TTY subsystem. .Sh AUTHORS .An -nosplit The author of the current implementation is -.An Ed Schouten Aq Mt ed@FreeBSD.org . +.An \&Ed Schouten Aq Mt ed@FreeBSD.org . Previous versions of .Nm were based on code written by diff --git a/share/man/man4/uftdi.4 b/share/man/man4/uftdi.4 index 687d443..dc45373 100644 --- a/share/man/man4/uftdi.4 +++ b/share/man/man4/uftdi.4 @@ -193,7 +193,7 @@ struct uftdi_eeio .Pp The FT232R chip has an internal eeprom. An external serial eeprom is optional on other FTDI chips. -The eeprom may contain 64, 128, or 256 words, +The eeprom may contain 64, 128, or 256 words, depending on the part used. Multiple calls may be needed to read or write the larger parts. When no eeprom is present, all words in the returned data are 0xffff. diff --git a/share/man/man4/vt.4 b/share/man/man4/vt.4 index f330218..e890904 100644 --- a/share/man/man4/vt.4 +++ b/share/man/man4/vt.4 @@ -327,8 +327,8 @@ driver first appeared in The .Nm device driver was developed by -.An Ed Schouten Aq Mt ed@FreeBSD.org , -.An Ed Maste Aq Mt emaste@FreeBSD.org , +.An \&Ed Schouten Aq Mt ed@FreeBSD.org , +.An \&Ed Maste Aq Mt emaste@FreeBSD.org , and .An Aleksandr Rybalko Aq Mt ray@FreeBSD.org , with sponsorship provided by the diff --git a/share/man/man7/release.7 b/share/man/man7/release.7 index a213813..3848768 100644 --- a/share/man/man7/release.7 +++ b/share/man/man7/release.7 @@ -435,7 +435,6 @@ include support for each hosting provider by default. The following .Xr make 1 environment variables are supported: -.Pp .Bl -tag -width Ev .It Va CLOUDWARE Set to a list of one or more cloud hosting providers, enclosed in quotes. diff --git a/share/man/man8/nanobsd.8 b/share/man/man8/nanobsd.8 index 3668112..aae6fff 100644 --- a/share/man/man8/nanobsd.8 +++ b/share/man/man8/nanobsd.8 @@ -104,7 +104,7 @@ Making use of just one shell script and one configuration file it is possible to build reduced and customized images satisfying any arbitrary set of requirements. .El -.Ss Nm NanoBSD Ss Media Layout +.Ss NanoBSD Media Layout The mass storage medium is divided into three parts by default (which are normally mounted read-only): .Pp diff --git a/share/man/man8/uefi.8 b/share/man/man8/uefi.8 index 94000dd..c4ee882 100644 --- a/share/man/man8/uefi.8 +++ b/share/man/man8/uefi.8 @@ -114,7 +114,7 @@ typical non-default kernel (optional) .Xr vt 4 , .Xr msdosfs 5 , .Xr boot 8 , -.Xr gpart 8 , +.Xr gpart 8 , .Xr uefisign 8 .Sh HISTORY .Nm @@ -125,7 +125,7 @@ boot support first appeared in .Nm boot support was developed by .An Benno Rice Aq Mt benno@FreeBSD.org , -.An Ed Maste Aq Mt emaste@FreeBSD.org , +.An \&Ed Maste Aq Mt emaste@FreeBSD.org , and .An Nathan Whitehorn Aq Mt nwhitehorn@FreeBSD.org . The diff --git a/share/man/man8/yp.8 b/share/man/man8/yp.8 index db5610b..8ca91be 100644 --- a/share/man/man8/yp.8 +++ b/share/man/man8/yp.8 @@ -464,9 +464,11 @@ Some systems, such as .Tn NIS to be running in order for their hostname resolution functions -.Fn ( gethostbyname , +.Po Fn gethostbyname , .Fn gethostbyaddr , -etc.) to work properly. +etc. +.Pc +to work properly. On these systems, .Xr ypserv 8 performs @@ -499,13 +501,14 @@ It can also be made to register itself as an v1 server in order to placate certain systems that insist on the presence of a v1 server -.No ( Fx +.Po Fx uses only .Tn NIS v2, but many other systems, including .Tn SunOS -4.x, search for both a v1 and v2 server when binding). +4.x, search for both a v1 and v2 server when binding +.Pc . .Fx Ns 's .Xr ypserv 8 does not actually handle diff --git a/share/man/man9/PCI_IOV_ADD_VF.9 b/share/man/man9/PCI_IOV_ADD_VF.9 index d99a106..1294cd0 100644 --- a/share/man/man9/PCI_IOV_ADD_VF.9 +++ b/share/man/man9/PCI_IOV_ADD_VF.9 @@ -104,8 +104,8 @@ the PF. .Sh SEE ALSO .Xr nv 9 , .Xr pci 9 , -.Xr pci_iov_schema 9 , .Xr PCI_IOV_INIT 9 , +.Xr pci_iov_schema 9 , .Xr PCI_IOV_UNINIT 9 .Sh AUTHORS This manual page was written by diff --git a/share/man/man9/PCI_IOV_INIT.9 b/share/man/man9/PCI_IOV_INIT.9 index f9daa24..d27538d 100644 --- a/share/man/man9/PCI_IOV_INIT.9 +++ b/share/man/man9/PCI_IOV_INIT.9 @@ -77,8 +77,8 @@ and no VFs will be created. .Sh SEE ALSO .Xr nv 9 , .Xr pci 9 , -.Xr pci_iov_schema 9 , .Xr PCI_IOV_ADD_VF 9 , +.Xr pci_iov_schema 9 , .Xr PCI_IOV_UNINIT 9 .Sh AUTHORS This manual page was written by diff --git a/share/man/man9/altq.9 b/share/man/man9/altq.9 index e718027..23d2510 100644 --- a/share/man/man9/altq.9 +++ b/share/man/man9/altq.9 @@ -237,7 +237,7 @@ sets a flag to indicate that a driver was converted to use the new macros. .Nm can be enabled only on interfaces with this flag. .Sh COMPATIBILITY -.Ss Vt ifaltq Ss structure +.Ss Vt ifaltq structure In order to keep compatibility with the existing code, the new output queue structure .Vt ifaltq diff --git a/share/man/man9/ifnet.9 b/share/man/man9/ifnet.9 index b165e2b..ef6e277 100644 --- a/share/man/man9/ifnet.9 +++ b/share/man/man9/ifnet.9 @@ -215,7 +215,7 @@ Interfaces are also associated with an output queue, defined as a this structure is used to hold packets while the interface is in the process of sending another. .Pp -.Ss The Vt ifnet Ss structure +.Ss The ifnet Structure The fields of .Vt "struct ifnet" are as follows: @@ -840,7 +840,7 @@ routine. The .Xr polling handler returns the number of packets processed. -.Ss The Vt if_data Ss Structure +.Ss The if_data Structure The .Vt if_data structure contains statistics and identifying information used @@ -1021,7 +1021,7 @@ The link is down. .It Dv LINK_STATE_UP The link is up. .El -.Ss The Vt ifaddr Ss Structure +.Ss The ifaddr Structure Every interface is associated with a list (or, rather, a .Li TAILQ ) @@ -1119,7 +1119,7 @@ In addition to these functions, there may also be link-layer support routines which are used by a number of drivers implementing a specific link layer over different hardware; see the documentation for that link layer for more details. -.Ss The Vt ifmultiaddr Ss Structure +.Ss The ifmultiaddr Structure Every multicast-capable interface is associated with a list of multicast group memberships, which indicate at a low level which link-layer multicast addresses (if any) should be accepted, and at a |