Various textual improvements.

1 files changed, 15 insertions, 16 deletions

diff --git a/share/man/man4/netgraph.4 b/share/man/man4/netgraph.4
index 030b20c..1f54d24 100644
--- a/share/man/man4/netgraph.4
+++ b/share/man/man4/netgraph.4
@@ -110,10 +110,9 @@ characters (including the terminating
 .Dv NUL
 character).
 .Pp
-Each node instance has a unique
-.Em ID number
-which is expressed as a 32-bit hexadecimal value.
-This value may be used to refer to a node when there is no
+Each node instance has a unique 32-bit
+.Em ID number .
+This number may be used to refer to a node when there is no
 .Tn ASCII
 name assigned to it.
 .Ss Hooks
@@ -153,7 +152,7 @@ by the input queueing system, rather than being delivered directly.
 This can be used when the data is sent from an interrupt handler,
 and processing must be quick so as not to block other interrupts.
 .It
-A hook may supply overriding receive data and receive message functions
+A hook may supply overriding receive data and receive message functions,
 which should be used for data and messages received through that hook
 in preference to the general node-wide methods.
 .El
@@ -175,15 +174,15 @@ The first
 in a chain must have the
 .Dv M_PKTHDR
 flag set.
-Each node decides how to handle data coming in on its hooks.
+Each node decides how to handle data received through one of its hooks.
 .Pp
 Along with data, nodes can also receive control messages.
 There are generic and type-specific control messages.
 Control messages have a common
-header format, followed by a type-specific data, and are binary structures
+header format, followed by type-specific data, and are binary structures
 for efficiency.
 However, node types may also support conversion of the
-type specific data between binary and
+type-specific data between binary and
 .Tn ASCII
 formats,
 for debugging and human interface purposes (see the
@@ -205,10 +204,10 @@ addressing).
 If the destination is adjacent to the source, then the source
 node may simply specify (as a pointer in the code) the hook across which the
 message should be sent.
-Otherwise, the recipient node global
+Otherwise, the recipient node's global
 .Tn ASCII
 name
-(or equivalent ID based name) is used as the destination address
+(or equivalent node ID) is used as the destination address
 for the message (absolute addressing).
 The two types of
 .Tn ASCII
@@ -217,19 +216,19 @@ may be combined, by specifying an absolute start node and a sequence
 of hooks.
 Only the
 .Tn ASCII
-addressing modes are available to control programs outside the kernel,
-as use of direct pointers is limited of course to kernel modules.
+addressing modes are available to control programs outside the kernel;
+use of direct pointers is limited to kernel modules.
 .Pp
-Messages often represent commands that are followed by a reply message
+Messages often represent commands which are followed by a reply message
 in the reverse direction.
 To facilitate this, the recipient of a
 control message is supplied with a
 .Dq return address
 that is suitable for addressing a reply.
 .Pp
-Each control message contains a 32 bit value called a
-.Em typecookie
-indicating the type of the message, i.e., how to interpret it.
+Each control message contains a 32-bit value, called a
+.Dq typecookie ,
+indicating the type of the message, i.e. how to interpret it.
 Typically each type defines a unique typecookie for the messages
 that it understands.
 However, a node may choose to recognize and