Mdoc Janitor:

  * Fix hard sentence breaks.

  * NOTE: devstat(9) requires more mdoc(7) work.

1 files changed, 8 insertions, 4 deletions

diff --git a/share/man/man9/driver.9 b/share/man/man9/driver.9
index fa64a1a..88fdb9e 100644
--- a/share/man/man9/driver.9
+++ b/share/man/man9/driver.9
@@ -72,11 +72,14 @@ DRIVER_MODULE(foo, bogo, foo_driver, foo_devclass, 0, 0);
 .Sh DESCRIPTION
 Each driver in the kernel is described by a
 .Dv driver_t
-structure.  The structure contains the name of the device, a pointer
+structure.
+The structure contains the name of the device, a pointer
 to a list of methods, an indication of the kind of device which the
 driver implements and the size of the private data which the driver
-needs to associate with a device instance.  Each driver will implement
-one or more sets of methods (called interfaces).  The example driver
+needs to associate with a device instance.
+Each driver will implement
+one or more sets of methods (called interfaces).
+The example driver
 implements the standard "driver" interface and the fictitious "bogo"
 interface.
 .Pp
@@ -85,7 +88,8 @@ When a driver is registered with the system (by the
 macro, see
 .Xr DRIVER_MODULE 9 ) ,
 it is added to the list of drivers contained in the devclass
-of its parent bus type.  For instance all PCI drivers would be
+of its parent bus type.
+For instance all PCI drivers would be
 contained in the devclass named "pci" and all ISA drivers would be
 in the devclass named "isa".
 The reason the drivers are not held in the device object of the parent