a even length -> an even length;

killed whitespace at EOL;

1 files changed, 10 insertions, 10 deletions

diff --git a/share/man/man4/man4.hp300/st.4 b/share/man/man4/man4.hp300/st.4
index d6cd571a5cb..6e4c9c08711 100644
--- a/share/man/man4/man4.hp300/st.4
+++ b/share/man/man4/man4.hp300/st.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: st.4,v 1.12 2003/03/16 20:12:51 miod Exp $
+.\"	$OpenBSD: st.4,v 1.13 2003/04/30 12:03:26 jmc Exp $
 .\"
 .\" Copyright (c) 1990, 1991, 1993
 .\"	The Regents of the University of California.  All rights reserved.
@@ -54,7 +54,7 @@ driver was written especially to support the Exabyte
 .Tn EXB-8200 8MM
 Cartridge
 Tape Subsystem.
-It has several extensions specific to the Exabyte, but should support other 
+It has several extensions specific to the Exabyte, but should support other
 tape drives as long as they follow the
 .Tn ANSI SCSI-I
 specification.
@@ -109,13 +109,13 @@ struct	mtget {
 .Pp
 Bit 4 in the minor device number is used
 to select long filemarks or short filemarks.
-A long filemark occupies 2.12 MBytes of space on the tape, while a short 
-filemark occupies 488 KBytes. 
+A long filemark occupies 2.12 MBytes of space on the tape, while a short
+filemark occupies 488 KBytes.
 A long filemark includes an erase gap while the short filemark does not.
 The tape can be positioned on the
 .Tn BOT
 side of a long filemark allowing
-data to be appended with a write operation. 
+data to be appended with a write operation.
 Since the short filemark does not contain an erase gap which would allow
 writing it is considered to be non-erasable.
 If either type of filemark is followed by blank tape, data may be appended
@@ -180,10 +180,10 @@ Read requests are normally even length for which a
 .Tn DMA
 transfer is used.
 If, however, the driver detects that an odd length read has happened
-(when a even length was requested) it will issue the
+(when an even length was requested) it will issue the
 .Dv EIO
 error and the last byte of the read
-data will be 0x00. 
+data will be 0x00.
 Odd length read requests must match the size of the requested data block
 on tape.
 .Pp
@@ -201,7 +201,7 @@ is ok).
 One can only start writing at  1) beginning of tape, 2) on the
 end of what was last written, 3) "front" side of a regular (long) filemark.
 For example, you have a tape with 3 tar files.
-If you want to save the first file, but overwrite the second two files with 
+If you want to save the first file, but overwrite the second two files with
 new data, on a normal
 1/4" or 1/2" drive you would do:
 .Pp
@@ -225,8 +225,8 @@ until a
 .Tn \*qBLANK CHECK\*q
 error is returned.
 Writing can be started at this point.
-(This applies to both long and short filemarks.) 
-The tape does not become positioned somewhere down the "erased" area as 
+(This applies to both long and short filemarks.)
+The tape does not become positioned somewhere down the "erased" area as
 does a conventional magtape.
 One can issue multiple reads at the
 .Tn \*qBLANK CHECK\*q