Removed trailing whitespace.

11 files changed, 56 insertions, 56 deletions

diff --git a/share/man/man4/cd.4 b/share/man/man4/cd.4
index 87f78ab..4bb9b0d 100644
--- a/share/man/man4/cd.4
+++ b/share/man/man4/cd.4
@@ -388,7 +388,7 @@ After that, the
 .Nm
 driver defaults to using 6 byte commands (assuming the protocol the drive
 speaks claims to support 6 byte commands), until one fails with a
-.Tn SCSI 
+.Tn SCSI
 ILLEGAL REQUEST error.  Then it tries the 10 byte version of the command to
 see if that works instead.  Users can change the default via per-drive
 sysctl variables and loader tunables.  The variable names are the same in
@@ -396,7 +396,7 @@ both instances:
 .Pp
 .Va kern.cam.cd.%d.minimum_cmd_size
 .Pp
-Where 
+Where
 .Dq %d
 is the unit number of the drive in question.  Valid minimum command sizes
 are 6 and 10.  Any value above 6 will be rounded to 10, and any value below
diff --git a/share/man/man4/da.4 b/share/man/man4/da.4
index b768589..0900852 100644
--- a/share/man/man4/da.4
+++ b/share/man/man4/da.4
@@ -119,7 +119,7 @@ Power Supply (UPS).
 The
 .Nm
 device driver ensures that the cache and media are synchronized upon
-final close of the device or an unexpected shutdown (panic) event. 
+final close of the device or an unexpected shutdown (panic) event.
 This ensures that it is safe to disconnect power once the operating system
 has reported that it has halted.
 The write cache can be enabled by setting the
diff --git a/share/man/man4/man4.i386/acpi_asus.4 b/share/man/man4/man4.i386/acpi_asus.4
index 7a96948..2d5314d 100644
--- a/share/man/man4/man4.i386/acpi_asus.4
+++ b/share/man/man4/man4.i386/acpi_asus.4
@@ -108,7 +108,7 @@ The
 driver and this manual page were written by
 .An Philip Paeps Aq philip@FreeBSD.org .
 .Pp
-Inspiration came from the 
-.Em acpi4asus project 
+Inspiration came from the
+.Em acpi4asus project
 started by Julien Lerouge which maintains a driver implementing this
 functionality in the Linux kernel.
diff --git a/share/man/man4/man4.i386/ct.4 b/share/man/man4/man4.i386/ct.4
index 3fdd1b1..85ee11b 100644
--- a/share/man/man4/man4.i386/ct.4
+++ b/share/man/man4/man4.i386/ct.4
@@ -41,7 +41,7 @@ For most PC-9801-55, -92 and compatibles:
 .Cd hint.ct.0.at="isa"
 .Pp
 For ELECOM bus-master
-.Tn SCSI 
+.Tn SCSI
 adapters:
 .Cd hint.ct.0.at="isa"
 .Cd hint.ct.0.flags="0x30000"
@@ -67,50 +67,50 @@ For adapters with SMIT transfer mode to enable SMIT transfer:
 meaning:
 .Bl -tag -offset indent -compact -width 0x000000
 .It 0x00000
-DMA transfer mode for an NEC PC-9801-55, -92 (or 
-compatibles), ICM IF-2660, Midori-Denshi MDC-554NA, or 
+DMA transfer mode for an NEC PC-9801-55, -92 (or
+compatibles), ICM IF-2660, Midori-Denshi MDC-554NA, or
 Logitec LHA-N151
 .It 0x10000
 DMA transfer mode for an I-O DATA SC-98II
 .It 0x20000
-bus-master transfer mode for a TEXA HA-55BS2, its 
+bus-master transfer mode for a TEXA HA-55BS2, its
 successors, or Midori-Denshi MDC-926R
 .It 0x30000
-bus-master transfer mode for an ELECOM bus-master SCSI 
+bus-master transfer mode for an ELECOM bus-master SCSI
 adapter
 .It 0x40000
 SMIT transfer mode (for supported adapters only)
 .It 0x50000
-bus-master transfer mode for a Logitec LHA-20x series, 
+bus-master transfer mode for a Logitec LHA-20x series,
 ICM IF-2766, IF-2766ET, IF-2767 or IF-2769
 .Sh DESCRIPTION
 The
 .Nm
-driver provides access to the 
-.Tn SCSI 
+driver provides access to the
+.Tn SCSI
 bus connected to a WD33C93[ABC] based host adapter.
 The following adapters are supported:
 .Pp
 .Bl -bullet -compact
 .It
-NEC PC-9801-55, 92 and compatibles, 
+NEC PC-9801-55, 92 and compatibles,
 .It
-ELECOM bus-master 
-.Tn SCSI 
-adapters, 
+ELECOM bus-master
+.Tn SCSI
+adapters,
 .It
-I-O DATA SC-98II, 
+I-O DATA SC-98II,
 .It
-ICM IF-2660, IF-2766, IF-2766ET, IF-2767 and IF-2769, 
+ICM IF-2660, IF-2766, IF-2766ET, IF-2767 and IF-2769,
 .It
-Logitec LHA-N151 and LHA-20x series, 
+Logitec LHA-N151 and LHA-20x series,
 .It
-Midori-Denshi MDC-554NA and MDC-926R, 
+Midori-Denshi MDC-554NA and MDC-926R,
 .It
-TEXA HA-55BS2 and its later models, and 
+TEXA HA-55BS2 and its later models, and
 .It
-SMIT transfer type 
-.Tn SCSI 
+SMIT transfer type
+.Tn SCSI
 host adapters.
 .El
 .Sh SEE ALSO
@@ -143,6 +143,6 @@ driver was written by
 .Pp
 This manual page was written by
 .An -nosplit
-.An Noriaki MITSUNAGA Aq non@FreeBSD.org 
+.An Noriaki MITSUNAGA Aq non@FreeBSD.org
 and
 .An Hideyuki KURASHINA Aq rushani@FreeBSD.org .
diff --git a/share/man/man4/man4.i386/ndis.4 b/share/man/man4/man4.i386/ndis.4
index 5a397bc..76b9c21 100644
--- a/share/man/man4/man4.i386/ndis.4
+++ b/share/man/man4/man4.i386/ndis.4
@@ -70,7 +70,7 @@ the user must extract two files: the .SYS file containing the driver
 binary code, and its companion .INF file, which contains the
 definitions for driver-specific registry keys and other installation
 data such as device identifiers. These two files can be converted
-into a 
+into a
 .Pa ndis_driver_data.h
 file using the
 .Xr ndiscvt 8
diff --git a/share/man/man4/matcd.4 b/share/man/man4/matcd.4
index 5235759..1cbab48 100644
--- a/share/man/man4/matcd.4
+++ b/share/man/man4/matcd.4
@@ -69,13 +69,13 @@ driver controls the CR-562 and CR-563 Compact Disc drives made by
 Matsushita-Kotobuki Electronics Industries, or Matsushita for short.
 These drives were sold under the Panasonic (which is a trade
 name for Matsushita), Creative Labs (omniCD) and Reveal names, and were
-also included in computers that were made by Tandy, GRiD, Victor, AST, 
+also included in computers that were made by Tandy, GRiD, Victor, AST,
 Packard Bell and many other brands.
 .Pp
 The drives are compatible with the major the Compact Disc standards,
 including CD-DA (Red Book - Digital Audio on pressed media), CD-WO (Orange
 Book Part II - Write-Once media), CD-ROM (Yellow Book - Data Storage), and
-the Kodak Photo-CD system.  The drives have some support related to 
+the Kodak Photo-CD system.  The drives have some support related to
 CD-ROM XA and CD-I (Green Book) audio and data requirements.
 .Pp
 These drives connect to the PC ISA bus through a simple (but proprietary) host
@@ -99,8 +99,8 @@ The
 .Nm
 driver can be directly linked into the
 .Fx
-kernel, or exist 
-as a loadable 
+kernel, or exist
+as a loadable
 .Fx
 kernel module.  The kernel module can be loaded or unloaded at any time
 using the \fBkldload\fR(8)/\fBkldunload\fR(8) commands.
@@ -116,7 +116,7 @@ the driver already in the kernel can simplify the installation process.
 if you determine that you need to have the
 .Nm
 driver linked into the kernel, it is necessary to add an entry to the kernel
-configuration file and generate a new kernel.  The 
+configuration file and generate a new kernel.  The
 .Fx
 kernel source tree comes
 with the file \fI/usr/src/sys/i386/conf/GENERIC\fR.
@@ -140,9 +140,9 @@ all of the instructions that are displayed.  If the kernel completely
 builds, use the "make install" command and then reboot the system for that
 new kernel to become operational.
 .Sh DRIVER CONFIGURATION
-Regardless of whether the 
+Regardless of whether the
 .Nm
-driver is linked into the kernel or is used as a loadable kernel module, 
+driver is linked into the kernel or is used as a loadable kernel module,
 the number of host interfaces that the driver will expect (or search for)
 is dictated by the number of entries present in the file
 \fI/boot/device\.hints\fR.  For example, in order to support two host
@@ -156,7 +156,7 @@ hint.matcd.1.port="0x260"
 
 .Ed
 Each set of entries designates a different
-.Nm 
+.Nm
 host interface, and where the I/O ports on that host interface adapter
 are located.
 .Pp
@@ -170,13 +170,13 @@ interface.
 .Pp
 If the \fIaddress\fR parameter of a
 \fBhint.matcd.\fIn\fR.port="\fIaddress\fP"\fR entry
-in \fI/boot/device\.hints\fR file is set to "\fB-1\fR", the 
+in \fI/boot/device\.hints\fR file is set to "\fB-1\fR", the
 .Nm
 driver searches for the host interface adapters by using a table
 of known I/O ports on Creative host adapters contained in the driver itself
-(see \fI/usr/src/sys/dev/matcd/options.h\fR).  
+(see \fI/usr/src/sys/dev/matcd/options.h\fR).
 .Pp
-Although the multiple port scan allows the 
+Although the multiple port scan allows the
 .Nm
 driver to work with many different types of host adapters without adjustments,
 using this mechanism has the potential to cause problems when your system has
@@ -202,7 +202,7 @@ above where the first I/O port for the audio section of the card (0x220).
 If you have determined exactly where the Matsushita I/O ports start on your
 system, specify the port by setting the
 \fBhint.matcd.\fIn\fR.port="\fIaddress\fP"\fR entry at the kernel boot
-prompt, or by editing the entry in the \fI/boot/device\.hints\fR file.  
+prompt, or by editing the entry in the \fI/boot/device\.hints\fR file.
 .Pp
 If you make a change to the \fI/boot/device\.hints\fR configuration file
 while the system is running, it is currently necessary to reboot the system
@@ -236,7 +236,7 @@ Later versions of Matsushita and "Creative" Compact Disc drives use a
 basic IDE interface, so these other drives must use an IDE driver, such
 as \fBata\fR(4).
 .Pp
-The TEAC CD-55 4X Compact Disc drive also uses the same Creative/Panasonic 
+The TEAC CD-55 4X Compact Disc drive also uses the same Creative/Panasonic
 electrical interface, but the TEAC drive is not command set compatible with
 the Matsushita CR-56x drives.  The TEAC drive cannot be used with
 .Nm .
@@ -394,8 +394,8 @@ Used to access 2352-byte frames on a Compact Disc
 recorded in any format and disables the disc eject controls.
 .It Pa /boot/devices.hints
 Specify the number of host interfaces and host adapter I/O port locations
-that 
-.Nm 
+that
+.Nm
 should examine.
 .It Pa /usr/src/sys/dev/matcd/*
 Source code for
@@ -429,7 +429,7 @@ Drives on a second host interface are considered logical
 drive numbers 4 through 7, drives 8 through 11 are on the third interface
 and 12 through 15 are on the fourth.  The first drive on the second host
 interface is always logical drive 4 regardless of how many drives are
-present on the first host interface.  
+present on the first host interface.
 .Pp
 Host interfaces are numbered as specified in the \fI/boot/devices.hints\fR
 file.
@@ -447,7 +447,7 @@ All rights reserved.
 The
 .Nm
 driver originally appeared in
-.Fx 2.0.5 .  The 
+.Fx 2.0.5 .  The
 .Fx
 5.1.x compatible implementation described here appeared in
 .Fx
diff --git a/share/man/man4/multicast.4 b/share/man/man4/multicast.4
index e71c16d..914013a 100644
--- a/share/man/man4/multicast.4
+++ b/share/man/man4/multicast.4
@@ -182,7 +182,7 @@ The
 contains the maximum rate (in bits/s) of the multicast data packets forwarded
 on that vif.
 Value of 0 means no limit.
-The 
+The
 .Dq vif_local_address
 contains the local IP address of the corresponding local interface.
 The
@@ -393,7 +393,7 @@ to preserve backward compatibility (binary and API),
 and at the same time to allow user-level processes to take advantage of
 the new features (if the kernel supports them).
 .Pp
-One of the mechanisms that allows us to preserve the backward 
+One of the mechanisms that allows us to preserve the backward
 compatibility is a sort of negotiation
 between the user-level process and the kernel:
 .Bl -enum
@@ -707,7 +707,7 @@ the following:
  *
  * Measurement works as follows:
  *
- * For >= measurements: 
+ * For >= measurements:
  * The first packet marks the start of a measurement interval.
  * During an interval we count packets and bytes, and when we
  * pass the threshold we deliver an upcall and we are done.
@@ -860,7 +860,7 @@ indicate the particular measured values.
 However, because of the way
 the particular intervals are measured, the user should be careful how
 bu_measured.b_time is used.
-For example, if the 
+For example, if the
 filter is installed to trigger an upcall if the number of packets
 is >= 1, then
 .Dq bu_measured
diff --git a/share/man/man4/ng_atmpif.4 b/share/man/man4/ng_atmpif.4
index 189ccae..f76aea3 100644
--- a/share/man/man4/ng_atmpif.4
+++ b/share/man/man4/ng_atmpif.4
@@ -46,7 +46,7 @@ The
 .Nm
 netgraph node type allows the emulation of
 .Xr atm 8
-(netatm/HARP) Physical devices (PIF) to be connected to the 
+(netatm/HARP) Physical devices (PIF) to be connected to the
 .Xr netgraph 4
 networking subsystem.
 Moreover it includes protection of the PDU against duplication and
diff --git a/share/man/man4/ng_sppp.4 b/share/man/man4/ng_sppp.4
index 2866b38..39b3336 100644
--- a/share/man/man4/ng_sppp.4
+++ b/share/man/man4/ng_sppp.4
@@ -146,6 +146,6 @@ The
 node type was implemented for
 .Fx 5.0 .
 It was included to the system since
-.Fx 5.3 . 
+.Fx 5.3 .
 .Sh AUTHOR
 .An Copyright (C) 2003-2004 Roman Kurakin Aq rik@cronyx.ru
diff --git a/share/man/man4/ng_sscop.4 b/share/man/man4/ng_sscop.4
index 6c6ed40..aa3d6ae 100644
--- a/share/man/man4/ng_sscop.4
+++ b/share/man/man4/ng_sscop.4
@@ -153,7 +153,7 @@ state and the lower hook is still connected, an
 .Dv SSCOP_RELEASE_request
 is executed to release the SSCOP connection.
 .It Dv manage
-This is the management interface defined in the standard. 
+This is the management interface defined in the standard.
 The data structure used here is:
 .Bd -literal
 struct sscop_marg {
@@ -190,7 +190,7 @@ The
 .Nm
 node understands the generic messages plus the following:
 .Bl -tag -width xxx
-.It Dv NGM_SSCOP_SETPARAM 
+.It Dv NGM_SSCOP_SETPARAM
 Set operational parameters of the SSCOP instance and takes the
 following structure:
 .Bd -literal
@@ -268,16 +268,16 @@ but that could not be set and
 is an
 .Xr errno 3
 code describing why the parameter could not be set.
-.It Dv NGM_SSCOP_GETPARAM 
+.It Dv NGM_SSCOP_GETPARAM
 This message returns the current operational parameters of the SSCOP
 instance in a
 .Fa sscop_param
 structure.
-.It Dv NGM_SSCOP_ENABLE 
+.It Dv NGM_SSCOP_ENABLE
 This message creates the actual SSCOP instance and initializes it.
 Until this is done, parameters may neither be retrieved not set and all
 message received on any hook are discarded.
-.It Dv NGM_SSCOP_DISABLE 
+.It Dv NGM_SSCOP_DISABLE
 Destroy the SSCOP instance. After this all messages on any hooks are
 discarded.
 .It Dv NGM_SSCOP_SETDEBUG
@@ -323,7 +323,7 @@ The space is computed as the difference of the
 .Fa max_queuelen_packets
 and
 .Fa current
-members of the 
+members of the
 .Fa ngm_queue_state
 structure.
 .It Dv NGM_SYNC_QUEUE_STATE
diff --git a/share/man/man4/stg.4 b/share/man/man4/stg.4
index 68956c5..4c170ed 100644
--- a/share/man/man4/stg.4
+++ b/share/man/man4/stg.4
@@ -59,7 +59,7 @@ MELCO IFC-SC
 RATOC REX-5536, REX-5536AM, REX-5536M, REX-9836A
 .El
 .Pp
-Note that the Adaptec 2920C is supported by the 
+Note that the Adaptec 2920C is supported by the
 .Sy ahc
 driver.
 .Sh SEE ALSO