mdoc(7) police: Scheduled sweep.

1 files changed, 11 insertions, 8 deletions

diff --git a/share/man/man4/fwohci.4 b/share/man/man4/fwohci.4
index a85a43c..bfbf6b8 100644
--- a/share/man/man4/fwohci.4
+++ b/share/man/man4/fwohci.4
@@ -65,27 +65,30 @@ Ricoh R5C552
 .El
 .Sh SEE ALSO
 .Xr firewire 4 ,
-.Xr fwcontrol 8 ,
 .Xr fwe 4 ,
-.Xr kldload 8 ,
-.Xr sbp 4
+.Xr sbp 4 ,
+.Xr fwcontrol 8 ,
+.Xr kldload 8
 .Sh HISTORY
 The
 .Nm
 device driver first appeared in
 .Fx 5.0 .
 .Sh AUTHORS
+.An -nosplit
 The
 .Nm
 device driver was written by
 .An Katsushi Kobayashi
 and
 .An Hidetoshi Shimokawa .
-.Pp
 .Sh BUGS
 The driver allows physical access from any nodes on the bus by default.
 This means that any devices on the bus can read and modify any memory space
-which can be accessed by IEEE 1394 OHCI chip.  It is allowed mostly
-for sbp(4) devices. This should be changed to allow it only for specific
-devices.  Anyway FireWire is a bus and not expected to be connected with
-un-trustable devices because a node can monitor all the traffic. 
+which can be accessed by IEEE 1394 OHCI chip.
+It is allowed mostly for
+.Xr sbp 4
+devices.
+This should be changed to allow it only for specific devices.
+Anyway, FireWire is a bus and not expected to be connected with
+un-trustable devices because a node can monitor all the traffic.