mdoc(7) police:

- Added SYNOPSIS
- Removed HISTORY information from DESCRIPTION
- Removed whitespace at EOL
- Minor markup nits

share/man/man4/bridge.4

@@ -7,17 +7,15 @@
 .Sh NAME
 .Nm bridge
 .Nd bridging support
+.Sh SYNOPSIS
+.Cd "options BRIDGE"
 .Sh DESCRIPTION
-Starting from version 2.2.8,
 .Fx
-supports bridging on Ethernet-type
-interfaces.
-This is enabled by including the following line in the kernel configuration
-file:
+supports bridging on Ethernet-type interfaces.
 .Pp
-.Dl "options BRIDGE"
-.Pp
-Runtime operation of the bridge is controlled by several
+Runtime operation of the
+.Nm
+is controlled by several
 .Xr sysctl 8
 variables.
 The
@@ -30,7 +28,6 @@ to disable it.
 .Pp
 The
 .Va net.link.ether.bridge_ipfw
-.Xr sysctl 8
 variable can be set to
 .Li 1
 to enable
@@ -43,15 +40,16 @@ to IP packets.
 Non-IP packets are subject to the default
 .Xr ipfw 8
 rule
-.Pq number 65535
+(number 65535)
 which must be an
-.Ar allow
+.Cm allow
 rule if ARP and other non-IP packets need to flow through the
-bridge.
+.Nm .
 .Pp
-The bridge configuration is controlled by the
+The
+.Nm
+configuration is controlled by the
 .Va net.link.ether.bridge_cfg
-.Xr sysctl 8
 variable.
 It consists of a comma-separated list of
 .Ar interface : Ns Ar cluster
@@ -61,14 +59,17 @@ number will
 be bridged together.
 .Pp
 Another
-.Xr sysctl 8
-variable reinitializes the bridge; this is required if bridged
+variable reinitializes the
+.Nm ;
+this is required if bridged
 configurations include loadable interfaces.
 After loading new interface drivers, setting the
 .Va net.link.ether.bridge_refresh
 variable to
 .Li 1
-will cause the bridge to reinitialize itself.
+will cause the
+.Nm
+to reinitialize itself.
 .Sh EXAMPLES
 The following command will cause the
 .Li ep0
@@ -82,7 +83,9 @@ interfaces to be bridged together:
 .Pp
 .Dl "sysctl -w net.link.ether.bridge_cfg ep0:0,fxp0:0,fxp1:1,de0:1"
 .Sh BUGS
-Care must be taken not to construct loops in the bridge topology.
+Care must be taken not to construct loops in the
+.Nm
+topology.
 The kernel supports only a primitive form of loop detection, by disabling
 some interfaces when a loop is detected.
 No support for a daemon running the