delete doubled words, e.g.: "the the" -> "the"

37 files changed, 86 insertions, 56 deletions

diff --git a/share/doc/handbook/development.sgml b/share/doc/handbook/development.sgml
index 5b498fc..3e53880 100644
--- a/share/doc/handbook/development.sgml
+++ b/share/doc/handbook/development.sgml
@@ -103,7 +103,7 @@ In summary, our development model is organized as a loose set of
 concentric circles.  The centralized model is designed for the
 convenience of the <em>users</em> of FreeBSD, who are thereby provided
 with an easy way of tracking one central code base, not to keep
-potential contributors out!  Our desire is to to present a stable
+potential contributors out!  Our desire is to present a stable
 operating system with a large set of coherent <ref id="ports"
 name="application programs"> that the users can easily install and
 use, and this model works very well in accomplishing that.
diff --git a/share/doc/handbook/eresources.sgml b/share/doc/handbook/eresources.sgml
index 7da47f6..7fa0df5 100644
--- a/share/doc/handbook/eresources.sgml
+++ b/share/doc/handbook/eresources.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: eresources.sgml,v 1.26 1996/07/29 07:15:55 jkh Exp $ -->
+<!-- $Id: eresources.sgml,v 1.27 1996/08/28 00:43:56 asami Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <chapt>
@@ -35,7 +35,7 @@ strive to keep the signal to noise ratio of the lists high, especially
 in the technical ones.
 
 Archives are kept for all of the mailing lists and can be searched
-using the the <url url="http://www.FreeBSD.ORG/search.html"
+using the <url url="http://www.FreeBSD.ORG/search.html"
 name="FreeBSD World Wide Web server">.  The keyword searchable archive
 offers an excellent way of finding answers to frequently asked
 questions and should be consulted before posting a question.
diff --git a/share/doc/handbook/esdi.sgml b/share/doc/handbook/esdi.sgml
index 858020b..698af3e 100644
--- a/share/doc/handbook/esdi.sgml
+++ b/share/doc/handbook/esdi.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: esdi.sgml,v 1.6 1996/01/31 19:02:56 mpp Exp $ -->
+<!-- $Id: esdi.sgml,v 1.7 1996/05/16 23:17:56 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!--
@@ -57,7 +57,7 @@
 	between all the drives. So, it forms a bus onto which all
 	drives are connected.
 
-	The second cable is a a 20 pin flat cable edge connector that
+	The second cable is a 20 pin flat cable edge connector that
 	carries the data to and from the drive. This cable is radially
 	connected, so each drive has its own direct connection to the
 	controller.
diff --git a/share/doc/handbook/install.sgml b/share/doc/handbook/install.sgml
index 43820f3..bd52ff9 100644
--- a/share/doc/handbook/install.sgml
+++ b/share/doc/handbook/install.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: install.sgml,v 1.36 1996/09/21 17:51:46 jkh Exp $ -->
+<!-- $Id: install.sgml,v 1.37 1996/10/04 22:54:05 wosch Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <!--
@@ -713,7 +713,7 @@ ftp://foo.bar.com:1234/pub/FreeBSD
 
 	<enum>
 	  <item>Boot the boot floppy.  After a boot sequence
-	    which can take anywhere from from 30 seconds to 3
+	    which can take anywhere from 30 seconds to 3
 	    minutes, depending on your hardware, you should be
 	    presented with a menu of initial choices.  If the
 	    floppy does not boot at all, or the boot hangs at some
diff --git a/share/doc/handbook/kernelconfig.sgml b/share/doc/handbook/kernelconfig.sgml
index b8a0ca5..646ab589 100644
--- a/share/doc/handbook/kernelconfig.sgml
+++ b/share/doc/handbook/kernelconfig.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: kernelconfig.sgml,v 1.19 1996/09/11 16:11:51 jfieber Exp $ -->
+<!-- $Id: kernelconfig.sgml,v 1.20 1996/09/16 14:27:07 jfieber Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 <!-- <!DOCTYPE linuxdoc PUBLIC '-//FreeBSD//DTD linuxdoc//EN'> -->
   <chapt><heading>Configuring the FreeBSD Kernel<label id="kernelconfig"></heading>
@@ -353,7 +353,7 @@
 	      the kernel.
 
 	      <quote><em/Note:/ The <tt>ipcs(1)</tt> command will
-		tell will list any processes using using each of
+		tell will list any processes using each of
 		these System V facilities.</quote>
 
 	  </descrip>
diff --git a/share/doc/handbook/linuxemu.sgml b/share/doc/handbook/linuxemu.sgml
index 560ec27..3ce539b 100644
--- a/share/doc/handbook/linuxemu.sgml
+++ b/share/doc/handbook/linuxemu.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: linuxemu.sgml,v 1.11 1996/08/28 00:43:59 asami Exp $ -->
+<!-- $Id: linuxemu.sgml,v 1.12 1996/10/04 22:54:07 wosch Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <chapt><heading>Linux Emulation<label id="linuxemu"></heading>
@@ -38,7 +38,7 @@ Linux-emulation up will vary slightly:
 <sect1><heading>Installing Linux Emulation in 2.1-STABLE</heading>
 
 <p>The GENERIC kernel in 2.1-stable is not configured for linux
-compatibility so you you must reconfigure your kernel for it.  There
+compatibility so you must reconfigure your kernel for it.  There
 are two ways to do this: 1. linking the emulator statically in the
 kernel itself and 2. configuring your kernel to dynamically load the
 linux loadable kernel module (LKM).
diff --git a/share/doc/handbook/policies.sgml b/share/doc/handbook/policies.sgml
index 41f0cbb..3f22756 100644
--- a/share/doc/handbook/policies.sgml
+++ b/share/doc/handbook/policies.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: policies.sgml,v 1.2 1996/07/03 04:23:26 mpp Exp $ -->
+<!-- $Id: policies.sgml,v 1.3 1996/07/22 00:00:36 jraynard Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <chapt><heading>Source Tree Guidelines and Policies
@@ -107,7 +107,7 @@ out major mistakes.
 branches, it is required that "official" patches from the vendor
 be applied to the original distributed sources and the result
 re-imported onto the vendor branch again.  Official patches should
-never be patched into the the FreeBSD checked out version and
+never be patched into the FreeBSD checked out version and
 "committed", as this destroys the vendor branch coherency and makes
 importing future versions rather difficult as there will be conflicts.
 
diff --git a/share/doc/handbook/porting.sgml b/share/doc/handbook/porting.sgml
index 56bf0b7..441ea06 100644
--- a/share/doc/handbook/porting.sgml
+++ b/share/doc/handbook/porting.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: porting.sgml,v 1.29 1996/09/12 05:00:53 asami Exp $ -->
+<!-- $Id: porting.sgml,v 1.30 1996/10/04 22:54:09 wosch Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect1><heading>Porting an existing piece of free software<label id="porting"></heading>
@@ -13,7 +13,7 @@ otherwise know where to turn for it.  All ported software is organized
 into a carefully organized hierarchy know as ``the ports collection''.
 The collection enables a new user to get a quick and complete overview
 of what is available for FreeBSD in an easy-to-compile form.  It also
-saves considerable space by not actually containing the the majority
+saves considerable space by not actually containing the majority
 of the sources being ported, but merely those differences required for
 running under FreeBSD. 
 
@@ -157,7 +157,7 @@ The pattern is the year followed by the month.
  # Date created:	5 December 1994
  # Whom:		asami
  #
- # $Id: porting.sgml,v 1.29 1996/09/12 05:00:53 asami Exp $
+ # $Id: porting.sgml,v 1.30 1996/10/04 22:54:09 wosch Exp $
  #
  
  DISTNAME=	oneko-1.1b
@@ -410,7 +410,7 @@ ftp://freefall.FreeBSD.ORG/pub/FreeBSD/LOCAL_PORTS/
 	<p>If your port requires some additional `patches' that are
 	  available on the Internet, fetch them too and put them in
 	  <tt>&dollar;{DISTDIR}</tt>.  Do not worry if they come from
-	  site other than where you got the the main source tarball,
+	  site other than where you got the main source tarball,
 	  we have a way to handle these situations (see the
 	  description of <ref id="porting:patchfiles"
 	  name="<tt>&dollar;{PATCHFILES}</tt>"> below).
@@ -560,7 +560,7 @@ work/foozolix-1.0/
 	<heading>MASTER_SITES</heading>
 
 	<p>Record the directory part of the ftp/http-URL pointing at
-	  the the original tarball in <tt>&dollar;{MASTER_SITES}</tt>.
+	  the original tarball in <tt>&dollar;{MASTER_SITES}</tt>.
 	  Do not forget the trailing slash (<tt>/</tt>)!
 
  	<p>The make macros will try to use this specification for
@@ -1098,7 +1098,7 @@ lib/libtcl.so.7.3
   person who wrote this Makefile]
  # Whom:			Satoshi Asami <asami@FreeBSD.ORG>
  #
- # $Id: porting.sgml,v 1.29 1996/09/12 05:00:53 asami Exp $
+ # $Id: porting.sgml,v 1.30 1996/10/04 22:54:09 wosch Exp $
  [ ^^^^ do not worry about this, I know it says "porting.sgml"...it
   will be automatically filled in by CVS when it is committed to our
   repository]
diff --git a/share/doc/handbook/printing.sgml b/share/doc/handbook/printing.sgml
index 941d8eb..e7ecb4f 100644
--- a/share/doc/handbook/printing.sgml
+++ b/share/doc/handbook/printing.sgml
@@ -1,7 +1,7 @@
 <!-- This is an SGML document in the linuxdoc DTD describing
      Printing with FreeBSD.  By Sean Kelly, 1995.
 
-     $Id: printing.sgml,v 1.9 1996/09/22 15:40:27 wosch Exp $
+     $Id: printing.sgml,v 1.10 1996/10/04 22:54:11 wosch Exp $
 
      The FreeBSD Documentation Project
 
@@ -2301,7 +2301,7 @@ plain text         if     none, -p, or -l
 	      outside of the base FreeBSD installation, they should
 	      probably go under <tt>/usr/local</tt>.  The directory
 	      <tt>/usr/local/libexec</tt> is a popular location, since
-	      they they are specialized programs that only LPD will
+	      they are specialized programs that only LPD will
 	      run; regular users should not ever need to run them.
 
 	      To enable a conversion filter, specify its pathname
diff --git a/share/doc/handbook/userppp.sgml b/share/doc/handbook/userppp.sgml
index 396665c..dae9838 100644
--- a/share/doc/handbook/userppp.sgml
+++ b/share/doc/handbook/userppp.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: userppp.sgml,v 1.7 1996/05/16 23:18:28 mpp Exp $ -->
+<!-- $Id: userppp.sgml,v 1.8 1996/05/31 02:51:24 mpp Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
 <sect>Setting up user PPP<label id="userppp">
@@ -35,7 +35,7 @@
   In essence, this means that rather than running a PPP daemon, the ppp
   program can be run as and when desired. No PPP interface needs to be
   compiled into the kernel, as the program can use the generic tunnel
-  device to to get data into and out of the kernel.
+  device to get data into and out of the kernel.
 
   From here on out, user ppp will be referred to as simply as ppp unless a
   distinction need to be made be it and any other PPP client/server software.
diff --git a/share/doc/iso/ucb/addr.nr b/share/doc/iso/ucb/addr.nr
index 57eff30..92ea9fa 100644
--- a/share/doc/iso/ucb/addr.nr
+++ b/share/doc/iso/ucb/addr.nr
@@ -1,3 +1,5 @@
+.\"	$Id$
+.\"
 .NC "NSAP Addresses & Routing"
 .sh 1 "OSI Address Formats"
 .pp
@@ -149,7 +151,7 @@ A table, \fIsnpa_cache\fR is kept in the kernel which contains the
 translation between NSAP-addresses and SNPA-addresses. 
 This table is used by \fIiso_snparesolve()\fR whenever a 
 datagram must be dispatched.
-The table is maintained by the the ISO ES-IS protocol entity.
+The table is maintained by the ISO ES-IS protocol entity.
 Entries can be added and deleted
 by the user program \fIclnlutil(8)\fR and
 by the CONS entity.
diff --git a/share/doc/iso/wisc/addr.nr b/share/doc/iso/wisc/addr.nr
index 1133422..e1b5fbb 100644
--- a/share/doc/iso/wisc/addr.nr
+++ b/share/doc/iso/wisc/addr.nr
@@ -1,3 +1,5 @@
+.\"	$Id$
+.\"
 .NC "NSAP Addresses & Routing"
 .sh 1 "OSI Address Formats"
 .pp
@@ -149,7 +151,7 @@ A table, \fIsnpa_cache\fR is kept in the kernel which contains the
 translation between NSAP-addresses and SNPA-addresses. 
 This table is used by \fIiso_snparesolve()\fR whenever a 
 datagram must be dispatched.
-The table is maintained by the the ISO ES-IS protocol entity.
+The table is maintained by the ISO ES-IS protocol entity.
 Entries can be added and deleted
 by the user program \fIclnlutil(8)\fR and
 by the CONS entity.
diff --git a/share/doc/iso/wisc/eicon.nr b/share/doc/iso/wisc/eicon.nr
index 64db4aa..a99c4c5 100644
--- a/share/doc/iso/wisc/eicon.nr
+++ b/share/doc/iso/wisc/eicon.nr
@@ -1,3 +1,5 @@
+.\"	$Id$
+.\"
 .sh 2 "X.25 Public Data Network Support"
 .pp
 This ARGO release includes support for an X.25 Public Data Network (PDN)
@@ -146,7 +148,7 @@ the remote DTE.
 This reply notifies CONS that the virtual circuit has been reset either
 by the DCE or by the remote DTE.
 .ip "\fIECN_ACK - 0x05\fR"
-This reply tells CONS that the associated ECN_SEND request has been been
+This reply tells CONS that the associated ECN_SEND request has been
 completed by the adapter.
 .sh 3 "NCB Commands"
 .lp
diff --git a/share/doc/iso/wisc/trans_design.nr b/share/doc/iso/wisc/trans_design.nr
index 6aeb54a..f0f8095 100644
--- a/share/doc/iso/wisc/trans_design.nr
+++ b/share/doc/iso/wisc/trans_design.nr
@@ -1,3 +1,5 @@
+.\"	$Id$
+.\"
 .NC "The Design of the ARGO Transport Entity"
 .sh 1 "Protocol Hooks"
 .pp
@@ -1457,7 +1459,7 @@ and lacking
 a method to measure
 the round trip time in the other direction,
 ARGO TP uses the measured average round trip time
-to adjust the the sendack timer.
+to adjust the sendack timer.
 .pp
 The choice of strategies is made with the
 \fIsetsockopt()\fR system call.
diff --git a/share/doc/iso/wiscman/cons.4p b/share/doc/iso/wiscman/cons.4p
index c8b152b..a233eac 100644
--- a/share/doc/iso/wiscman/cons.4p
+++ b/share/doc/iso/wiscman/cons.4p
@@ -1,3 +1,5 @@
+.\"	$Id$
+.\"
 .TH CONS 4P "9 December 1988"
 .ds ]W Wisconsin ARGO 1.0
 .UC 4
@@ -112,7 +114,7 @@ The actual error value returned in
 \fIerrno\fR
 is the X.25 diagnostic code in the lower 10 bits
 logically "or"ed with the hexadecimal value 0x8400 (bits
-10 and 15 set, counting from zero at the the least significant bit).
+10 and 15 set, counting from zero at the least significant bit).
 The error values can be found in 
 the file
 .nf
diff --git a/share/doc/iso/wiscman/tp.4p b/share/doc/iso/wiscman/tp.4p
index 64dbf2f..e82cfef 100644
--- a/share/doc/iso/wiscman/tp.4p
+++ b/share/doc/iso/wiscman/tp.4p
@@ -1,3 +1,5 @@
+.\"	$Id$
+.\"
 .TH TP 4P "9 December 1988"
 .ds ]W Wisconsin ARGO 1.0
 .UC 4
@@ -368,7 +370,7 @@ p_use_checksum
 Boolean.
 [ true ]
 .IP
-Boolean indicating the the use of checksums will be negotiated.
+Boolean indicating the use of checksums will be negotiated.
 This parameter applies only to class 4.
 .\" ******************8
 .TP 25
diff --git a/share/doc/papers/diskperf/conclusions.ms b/share/doc/papers/diskperf/conclusions.ms
index 5381106..b8e9ff3 100644
--- a/share/doc/papers/diskperf/conclusions.ms
+++ b/share/doc/papers/diskperf/conclusions.ms
@@ -30,6 +30,7 @@
 .\" SUCH DAMAGE.
 .\"
 .\"	@(#)conclusions.ms	6.2 (Berkeley) 4/16/91
+.\"	$Id$
 .\"
 .ds RH Conclusions
 .NH
@@ -58,7 +59,7 @@ against the future value and expandability of newer technologies.
 Two important conclusions about storage systems in general
 can be drawn from these tests.
 The first is that buffering can be effective in smoothing
-the the effects of lower bus speeds and bus contention.
+the effects of lower bus speeds and bus contention.
 Even though the UDA50 is located on the relatively slow
 UNIBUS, its performance is similar to controllers located on
 the faster processor busses.
diff --git a/share/doc/papers/diskperf/tests.ms b/share/doc/papers/diskperf/tests.ms
index 1809afe..e507408 100644
--- a/share/doc/papers/diskperf/tests.ms
+++ b/share/doc/papers/diskperf/tests.ms
@@ -30,6 +30,7 @@
 .\" SUCH DAMAGE.
 .\"
 .\"	@(#)tests.ms	6.2 (Berkeley) 4/16/91
+.\"	$Id$
 .\"
 .ds RH Tests
 .NH
@@ -39,7 +40,7 @@ Our battery of tests consists of four programs,
 read_8192, write_8192, write_4096
 and rewrite_8192 originally written by [McKusick83]
 to evaluate the performance of the new file system in 4.2BSD.
-These programs all follow the the same model and are typified by
+These programs all follow the same model and are typified by
 read_8192 shown here.
 .DS
 #define	BUFSIZ 8192
diff --git a/share/doc/papers/fsinterface/fsinterface.ms b/share/doc/papers/fsinterface/fsinterface.ms
index c5722e6..b1cc43e 100644
--- a/share/doc/papers/fsinterface/fsinterface.ms
+++ b/share/doc/papers/fsinterface/fsinterface.ms
@@ -30,6 +30,7 @@
 .\" SUCH DAMAGE.
 .\"
 .\"	@(#)fsinterface.ms	1.4 (Berkeley) 4/16/91
+.\"	$Id$
 .\"
 .if \nv .rm CM
 .de UX
@@ -250,7 +251,7 @@ otherwise, the inode describes the next directory to be searched.
 The inode returned may be used in various ways by the caller;
 it may be examined, the file may be read or written,
 types and access may be checked, and fields may be modified.
-Modified inodes are automatically written back the the filesystem
+Modified inodes are automatically written back the filesystem
 on disk when the last reference is released with \fIiput\fP.
 Although the details are considerably different,
 the same general scheme is used in the faster filesystem in 4.2BSD
@@ -578,7 +579,7 @@ and they may be accessed using short offsets from a base pointer
 .PP
 The proposed filesystem interface is described very tersely here.
 For the most part, data structures and procedures are analogous
-to those used by VFS, and only the changes will be be treated here.
+to those used by VFS, and only the changes will be treated here.
 See [Kleiman86] for complete descriptions of the vfs and vnode operations
 in Sun's interface.
 .PP
diff --git a/share/doc/papers/kernmalloc/kernmalloc.t b/share/doc/papers/kernmalloc/kernmalloc.t
index 62df1b4..0b8bb08 100644
--- a/share/doc/papers/kernmalloc/kernmalloc.t
+++ b/share/doc/papers/kernmalloc/kernmalloc.t
@@ -30,6 +30,7 @@
 .\" SUCH DAMAGE.
 .\"
 .\"	@(#)kernmalloc.t	5.1 (Berkeley) 4/16/91
+.\"	$Id$
 .\"
 .\" reference a system routine name
 .de RN
@@ -600,7 +601,7 @@ Two of the traditional UNIX
 memory allocators remain in the current system.
 The terminal subsystem uses \fIclist\fP\^s (character lists).
 That part of the system is expected to undergo major revision within
-the the next year or so, and it will probably be changed to use
+the next year or so, and it will probably be changed to use
 \fImbuf\fP\^s as it is merged into the network system.
 The other major allocator that remains is
 .RN getblk ,
diff --git a/share/doc/papers/kerntune/1.t b/share/doc/papers/kerntune/1.t
index d78c568..88adf40 100644
--- a/share/doc/papers/kerntune/1.t
+++ b/share/doc/papers/kerntune/1.t
@@ -31,13 +31,14 @@
 .\" SUCH DAMAGE.
 .\"
 .\"	@(#)1.t	1.2 (Berkeley) 11/8/90
+.\"	$Id$
 .\"
 .ds RH Introduction
 .NH 1
 Introduction
 .PP
 The purpose of this paper is to describe the tools and techniques 
-that are available for improving the performance of the the kernel.
+that are available for improving the performance of the kernel.
 The primary tool used to measure the kernel is the hierarchical
 profiler \fIgprof\fP.
 The profiler enables the user to measure the cost of
diff --git a/share/doc/papers/malloc/kernel.ms b/share/doc/papers/malloc/kernel.ms
index 1a4e967..21dff8d 100644
--- a/share/doc/papers/malloc/kernel.ms
+++ b/share/doc/papers/malloc/kernel.ms
@@ -6,7 +6,7 @@
 .\" this stuff is worth it, you can buy me a beer in return.   Poul-Henning Kamp
 .\" ----------------------------------------------------------------------------
 .\"
-.\" $Id$
+.\" $Id: kernel.ms,v 1.1 1996/04/13 08:30:16 phk Exp $
 .\"
 .ds RH The kernel and memory
 .NH
@@ -30,7 +30,7 @@ for the data and bss section combined and one for the stack.
 On some systems the text shared a segment with the data and bss, and was
 consequently just as writable as them.
 .PP
-In this setup all the the brk(2) system call have to do is to find the
+In this setup all the brk(2) system call have to do is to find the
 right amount of free storage, possibly moving things around in physical
 memory, maybe even swapping out a segment or two to make space,
 and change the upper limit on the data segment according to the address given.
diff --git a/share/doc/papers/newvm/1.t b/share/doc/papers/newvm/1.t
index 657fc2d..c934b97 100644
--- a/share/doc/papers/newvm/1.t
+++ b/share/doc/papers/newvm/1.t
@@ -30,6 +30,7 @@
 .\" SUCH DAMAGE.
 .\"
 .\"	@(#)1.t	5.1 (Berkeley) 4/16/91
+.\"	$Id$
 .\"
 .NH
 Motivations for a New Virtual Memory System
@@ -156,7 +157,7 @@ be governed by the amount of physical memory.
 .PP
 Another effect of the current technology is that the latency and overhead
 associated with accessing the file system is considerably higher
-since the access must be be over the network
+since the access must be over the network
 rather than to a locally-attached disk.
 One use of the surplus memory would be to
 maintain a cache of recently used files;
diff --git a/share/doc/papers/newvm/a.t b/share/doc/papers/newvm/a.t
index 3b6213a..3472470 100644
--- a/share/doc/papers/newvm/a.t
+++ b/share/doc/papers/newvm/a.t
@@ -30,6 +30,7 @@
 .\" SUCH DAMAGE.
 .\"
 .\"	@(#)a.t	5.1 (Berkeley) 4/16/91
+.\"	$Id$
 .\"
 .sp 2
 .ne 2i
@@ -200,7 +201,7 @@ value = mset(sem, wait)
 result int value; semaphore *sem; int wait;
 .DE
 \fIMset\fP indivisibly tests and sets the semaphore \fIsem\fP.
-If the the previous value is zero, the process has acquired the lock
+If the previous value is zero, the process has acquired the lock
 and \fImset\fP returns true immediately.
 Otherwise, if the \fIwait\fP flag is zero,
 failure is returned.
diff --git a/share/doc/psd/05.sysman/1.2.t b/share/doc/psd/05.sysman/1.2.t
index c0a3b17..1a77f77 100644
--- a/share/doc/psd/05.sysman/1.2.t
+++ b/share/doc/psd/05.sysman/1.2.t
@@ -30,6 +30,7 @@
 .\" SUCH DAMAGE.
 .\"
 .\"	@(#)1.2.t	8.1 (Berkeley) 6/8/93
+.\"	$Id$
 .\"
 .sh "Memory management\(dg
 .NH 3
@@ -233,7 +234,7 @@ value = mset(sem, wait)
 result int value; semaphore *sem; int wait;
 .DE
 \fIMset\fP indivisibly tests and sets the semaphore \fIsem\fP.
-If the the previous value is zero, the process has acquired the lock
+If the previous value is zero, the process has acquired the lock
 and \fImset\fP returns true immediately.
 Otherwise, if the \fIwait\fP flag is zero,
 failure is returned.
diff --git a/share/doc/psd/05.sysman/2.3.t b/share/doc/psd/05.sysman/2.3.t
index 509c7f3..8cb60a0 100644
--- a/share/doc/psd/05.sysman/2.3.t
+++ b/share/doc/psd/05.sysman/2.3.t
@@ -30,6 +30,7 @@
 .\" SUCH DAMAGE.
 .\"
 .\"	@(#)2.3.t	8.1 (Berkeley) 6/8/93
+.\"	$Id$
 .\"
 .sh "Interprocess communications
 .NH 3
@@ -392,7 +393,7 @@ provide IP source routing or security options.
 The 32-bit address is composed of network and host parts;
 the network part is variable in size and is frequency encoded.
 The host part may optionally be interpreted as a subnet field
-plus the host on subnet; this is is enabled by setting a network address
+plus the host on subnet; this is enabled by setting a network address
 mask at boot time.
 .NH 4
 Access rights transmission
diff --git a/share/doc/psd/21.ipc/5.t b/share/doc/psd/21.ipc/5.t
index fe6977e..25fd4e5b 100644
--- a/share/doc/psd/21.ipc/5.t
+++ b/share/doc/psd/21.ipc/5.t
@@ -30,6 +30,7 @@
 .\" SUCH DAMAGE.
 .\"
 .\"	@(#)5.t	8.1 (Berkeley) 8/14/93
+.\"	$Id$
 .\"
 .\".ds RH "Advanced Topics
 .bp
@@ -1538,7 +1539,7 @@ on file descriptors 0 and 1, and may immediately perform
 any operations such as \fIread\fP, \fIwrite\fP, \fIsend\fP,
 or \fIrecv\fP.  Indeed, servers may use
 buffered I/O as provided by the ``stdio'' conventions, as
-long as as they remember to use \fIfflush\fP when appropriate.
+long as they remember to use \fIfflush\fP when appropriate.
 .PP
 One call which may be of interest to individuals writing
 servers under \fIinetd\fP is the \fIgetpeername\fP call,
diff --git a/share/doc/smm/01.setup/2.t b/share/doc/smm/01.setup/2.t
index 396f956..f5b1120 100644
--- a/share/doc/smm/01.setup/2.t
+++ b/share/doc/smm/01.setup/2.t
@@ -30,6 +30,7 @@
 .\" SUCH DAMAGE.
 .\"
 .\"	@(#)2.t	8.1 (Berkeley) 7/27/93
+.\"	$Id$
 .\"
 .ds lq ``
 .ds rq ''
@@ -1652,7 +1653,7 @@ If
 .Xr tar
 images were written instead of doing a dump, you should
 be sure to use its `\-p' option when reading the files back.  No matter
-how you restore a filesystem, be sure to unmount it and and check its
+how you restore a filesystem, be sure to unmount it and check its
 integrity with
 .Xr fsck (8)
 when the job is complete.
diff --git a/share/doc/usd/19.memacros/intro.me b/share/doc/usd/19.memacros/intro.me
index 2d8046a..b6b6796 100644
--- a/share/doc/usd/19.memacros/intro.me
+++ b/share/doc/usd/19.memacros/intro.me
@@ -30,6 +30,7 @@
 .\" SUCH DAMAGE.
 .\"
 .\"	@(#)intro.me	8.1 (Berkeley) 6/8/93
+.\"	$Id$
 .\"
 .UC 7
 .ll 6.5i
@@ -1426,7 +1427,7 @@ the input:
 produces\**:
 .(f
 \**By the way,
-if you put the first three ingredients in a a heavy, deep pan
+if you put the first three ingredients in a heavy, deep pan
 and whisk the ingredients madly over a medium flame
 (never taking your hand off the handle of the pot)
 until the mixture reaches the consistency of custard
diff --git a/share/man/man0/title.urm b/share/man/man0/title.urm
index 0e307f1..515a639 100644
--- a/share/man/man0/title.urm
+++ b/share/man/man0/title.urm
@@ -30,6 +30,7 @@
 .\" SUCH DAMAGE.
 .\"
 .\"	@(#)title.urm	8.7 (Berkeley) 4/20/94
+.\"	$Id$
 .\"
 .af % i
 .EH ''''
@@ -991,7 +992,7 @@ We gratefully acknowledge
 the support of this contract.
 .LP
 We wish to acknowledge the contribution of a number of individuals to
-the the system.
+the system.
 .LP
 We would especially like to thank
 Jim Kulp of IIASA,
diff --git a/share/man/man4/bpf.4 b/share/man/man4/bpf.4
index d63b399..e43d8d4 100644
--- a/share/man/man4/bpf.4
+++ b/share/man/man4/bpf.4
@@ -20,6 +20,8 @@
 .\" This document is derived in part from the enet man page (enet.4)
 .\" distributed with 4.3BSD Unix.
 .\"
+.\"	$Id$
+.\"
 .Dd January 16, 1996
 .Dt BPF 4
 .Os BSD 4.4
@@ -309,7 +311,7 @@ field exists to account for
 padding between the header and the link level protocol.
 The purpose here is to guarantee proper alignment of the packet
 data structures, which is required on alignment sensitive 
-architectures and and improves performance on many other architectures.
+architectures and improves performance on many other architectures.
 The packet filter insures that the 
 .Li bpf_hdr
 and the network layer
diff --git a/share/man/man4/snp.4 b/share/man/man4/snp.4
index 2f77db1..2f5b50f 100644
--- a/share/man/man4/snp.4
+++ b/share/man/man4/snp.4
@@ -1,5 +1,5 @@
 .\"
-.\"  $Id: snp.4,v 1.6 1995/02/28 00:24:47 pst Exp $
+.\"  $Id: snp.4,v 1.7 1996/01/30 13:51:11 mpp Exp $
 .\"  $Source: /home/ncvs/src/share/man/man4/snp.4,v $
 .\"
 .Dd February 24, 1995
@@ -28,7 +28,7 @@ device with a tty to be observed,  open the
 device and then use the SNPSTTY ioctl.
 The argument passed to the IOCTL is the address of a variable of type
 dev_t.
-By setting the value of the variable pointed to to -1, the user may detach
+By setting the value of the variable pointed to -1, the user may detach
 the snp device from a tty.
 .Pp
 The SNPGTTY ioctl returns information about the current tty attached to
diff --git a/share/man/man4/tp.4 b/share/man/man4/tp.4
index fdc845d..f68c4ac 100644
--- a/share/man/man4/tp.4
+++ b/share/man/man4/tp.4
@@ -30,6 +30,7 @@
 .\" SUCH DAMAGE.
 .\"
 .\"     @(#)tp.4	8.4 (Berkeley) 4/19/94
+.\"	$Id$
 .\"
 .Dd April 19, 1994
 .Dt TP 4
@@ -482,7 +483,7 @@ This parameter applies only to class 4.
 Boolean.
 [true]
 .br
-Boolean indicating the the use of checksums will be negotiated.
+Boolean indicating the use of checksums will be negotiated.
 This parameter applies only to class 4.
 .It Ar p_use_nxpd
 Reserved for future use.
diff --git a/share/man/man5/hosts.equiv.5 b/share/man/man5/hosts.equiv.5
index 44efb68..d4ae350 100644
--- a/share/man/man5/hosts.equiv.5
+++ b/share/man/man5/hosts.equiv.5
@@ -29,6 +29,8 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
+.\"	$Id$
+.\"
 .Dd Feb 1996
 .Dt HOSTS.EQUIV 5
 .Os FreeBSD
@@ -80,7 +82,7 @@ For security reasons, a users
 .Nm .rhosts
 file will be ignored if it is not a regular file, or if it 
 is not owned by the user, or
-if is is writable by anyone other than the user.
+if it is writable by anyone other than the user.
 .Sh EXAMPLES
 .Pp
 .Dl bar.com foo
diff --git a/share/man/man5/link.5 b/share/man/man5/link.5
index a0c726e..b42e0d2 100644
--- a/share/man/man5/link.5
+++ b/share/man/man5/link.5
@@ -26,7 +26,7 @@
 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.\"	$Id: link.5,v 1.5 1996/04/08 04:18:14 mpp Exp $
+.\"	$Id: link.5,v 1.6 1996/05/01 01:45:22 bde Exp $
 .\"
 .Dd October 23, 1993
 .Dt LINK 5
@@ -422,7 +422,7 @@ run under control of a debugger.
 .It Fa dd_sym_loaded
 Set by the run-time linker whenever it adds symbols by loading shared objects.
 .It Fa dd_bpt_addr
-The address were a breakpoint will be set by the the run-time linker to
+The address were a breakpoint will be set by the run-time linker to
 divert control to the debugger. This address is determined by the start-up
 module,
 .Em crt0.o,
diff --git a/share/man/man5/sysconfig.5 b/share/man/man5/sysconfig.5
index a8257f0..09b6a19 100644
--- a/share/man/man5/sysconfig.5
+++ b/share/man/man5/sysconfig.5
@@ -22,7 +22,7 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.\"     $Id: sysconfig.5,v 1.3 1996/08/15 23:36:21 mpp Exp $
+.\"     $Id: sysconfig.5,v 1.4 1996/08/21 22:01:46 mpp Exp $
 .\"
 .Dd December 18, 1995
 .Dt SYSCONFIG 5
@@ -64,7 +64,7 @@ file:
 .It Ar keymap
 (str) If set to
 .Ar NO
-then no keymap is installed, otherwise the value is used to to install
+then no keymap is installed, otherwise the value is used to install
 the keymap file in 
 .Pa /usr/share/syscons/keymaps/value.kbd
 .It Ar keyrate
diff --git a/share/termcap/termcap.src b/share/termcap/termcap.src
index dee9203..6f3eef9 100644
--- a/share/termcap/termcap.src
+++ b/share/termcap/termcap.src
@@ -30,7 +30,7 @@
 # SUCH DAMAGE.
 #
 #	@(#)termcap.src	8.2 (Berkeley) 11/17/93
-#
+#	$Id$
 
 #	Termcap source file
 #	John Kunze, Berkeley
@@ -2517,7 +2517,7 @@ kterm|kterm kanji terminal emulator (X window system):\
 # Due to severe 2621 braindamage, the only way to get the arrow keys to
 # transmit anything at all is to turn on the function key labels
 # (f1-f8) with ks, and even then the poor user has to hold down shift!
-# The default 2621 turns off the labels except when it has to to enable
+# The default 2621 turns off the labels except when it has to enable
 # the function keys.  If your installation prefers labels on all the time,
 # or off all the time (at the "expense" of the function keys) move the
 # 2621-nl or 2621-wl labels to the front using reorder.