Hiten's patchset for section four manpages, slightly edited by me.

1 files changed, 12 insertions, 8 deletions

diff --git a/share/man/man4/natm.4 b/share/man/man4/natm.4
index 622ccce..75a2c57 100644
--- a/share/man/man4/natm.4
+++ b/share/man/man4/natm.4
@@ -19,7 +19,7 @@ to do
 .Dq make clean ) .
 .Sh NATM API
 The NATM layer uses a
-.Dv struct sockaddr_natm
+.Vt struct sockaddr_natm
 to specify a virtual circuit:
 .Bd -literal -offset indent
 struct sockaddr_natm {
@@ -52,11 +52,13 @@ one would use the following:
 .Pp
 The
 .Fn socket
-call simply creates an unconnected NATM socket.  The
+call simply creates an unconnected NATM socket.
+The
 .Fn connect
 call associates an unconnected NATM socket with a
 virtual circuit and tells the driver to enable that virtual circuit
-for receiving data.  After the
+for receiving data.
+After the
 .Fn connect
 call one can
 .Fn read
@@ -75,19 +77,21 @@ protocol layer passes the address of the protocol control block down
 to the driver as a receive
 .Dq handle .
 When inbound data arrives, the driver passes the data back with the
-appropriate receive handle.   The NATM layer uses this to avoid the
-overhead of a protocol control block lookup.   This allows us to take
+appropriate receive handle.
+The NATM layer uses this to avoid the
+overhead of a protocol control block lookup.
+This allows us to take
 advantage of the fact that ATM has already demultiplexed the data for
 us.
 .Sh CAVEAT
 The NATM protocol support is subject to change as
-the ATM protocols develop.  Users should not depend
-on details of the current implementation, but rather
+the ATM protocols develop.
+Users should not depend on details of the current implementation, but rather
 the services exported.
 .Sh SEE ALSO
 .Xr en 4 ,
-.Xr hatm 4 ,
 .Xr fatm 4 ,
+.Xr hatm 4 ,
 .Xr natmip 4
 .Sh AUTHORS
 .An Chuck Cranor