diff -ruN bleadperl_old/pod/perl56delta.pod bleadperl/pod/perl56delta.pod
--- bleadperl_old/pod/perl56delta.pod    Mon Apr 03 15:08:22 2000
+++ bleadperl/pod/perl56delta.pod  Mon Apr 03 15:11:52 2000
@@ -1547,7 +1547,7 @@

 =item *

-EPOC is is now supported (on Psion 5).
+EPOC is now supported (on Psion 5).

 =item *

diff -ruN bleadperl_old/pod/perldebguts.pod bleadperl/pod/perldebguts.pod
--- bleadperl_old/pod/perldebguts.pod    Mon Apr 03 15:08:22 2000
+++ bleadperl/pod/perldebguts.pod  Mon Apr 03 15:12:17 2000
@@ -19,7 +19,7 @@

 For example, whenever you call Perl's built-in C<caller> function
 from the package DB, the arguments that the corresponding stack
-frame was called with are copied to the the @DB::args array.  The
+frame was called with are copied to the @DB::args array.  The
 general mechanisms is enabled by calling Perl with the B<-d> switch, the
 following additional features are enabled (cf. L<perlvar/$^P>):

@@ -154,7 +154,7 @@
 C<DB::parse_options(string)>.  The function C<DB::dump_trace(skip[,
 count])> skips the specified number of frames and returns a list
 containing information about the calling frames (all of them, if
-C<count> is missing).  Each entry is reference to a a hash with
+C<count> is missing).  Each entry is reference to a hash with
 keys C<context> (either C<.>, C<$>, or C<@>), C<sub> (subroutine
 name, or info about C<eval>), C<args> (C<undef> or a reference to
 an array), C<file>, and C<line>.
diff -ruN bleadperl_old/pod/perlfaq5.pod bleadperl/pod/perlfaq5.pod
--- bleadperl_old/pod/perlfaq5.pod Mon Apr 03 15:08:23 2000
+++ bleadperl/pod/perlfaq5.pod     Mon Apr 03 15:12:25 2000
@@ -841,7 +841,7 @@

 You should think long and hard about why you need everything loaded
 at once.  It's just not a scalable solution.  You might also find it
-more fun to use the the standard DB_File module's $DB_RECNO bindings,
+more fun to use the standard DB_File module's $DB_RECNO bindings,
 which allow you to tie an array to a file so that accessing an element
 the array actually accesses the corresponding line in the file.

diff -ruN bleadperl_old/pod/perlfork.pod bleadperl/pod/perlfork.pod
--- bleadperl_old/pod/perlfork.pod Mon Apr 03 15:08:23 2000
+++ bleadperl/pod/perlfork.pod     Mon Apr 03 15:12:37 2000
@@ -11,7 +11,7 @@
 On some platforms such as Windows where the fork() system call is not
 available, Perl can be built to emulate fork() at the interpreter level.
 While the emulation is designed to be as compatible as possible with the
-real fork() at the the level of the Perl program, there are certain
+real fork() at the level of the Perl program, there are certain
 important differences that stem from the fact that all the pseudo child
 "processes" created this way live in the same real process as far as the
 operating system is concerned.
diff -ruN bleadperl_old/pod/perlfunc.pod bleadperl/pod/perlfunc.pod
--- bleadperl_old/pod/perlfunc.pod Mon Apr 03 15:08:23 2000
+++ bleadperl/pod/perlfunc.pod     Mon Apr 03 15:13:02 2000
@@ -1863,7 +1863,7 @@
 the real name of the user (as opposed to the login name) and other
 information pertaining to the user.  Beware, however, that in many
 system users are able to change this information and therefore it
-cannot be trusted and therefore the $gcos is is tainted (see
+cannot be trusted and therefore the $gcos is tainted (see
 L<perlsec>).  The $passwd and $shell, user's encrypted password and
 login shell, are also tainted, because of the same reason.

@@ -2810,7 +2810,7 @@
     open(FOO, "< $file\0");

 (this may not work on some bizzare filesystems).  One should
-conscientiously choose between the the I<magic> and 3-arguments form
+conscientiously choose between the I<magic> and 3-arguments form
 of open():

     open IN, $ARGV[0];
@@ -3927,7 +3927,7 @@
 semid_ds structure or semaphore value array.  Returns like C<ioctl>:
 the undefined value for error, "C<0 but true>" for zero, or the actual
 return value otherwise.  The ARG must consist of a vector of native
-short integers, which may may be created with C<pack("s!",(0)x$nsem)>.
+short integers, which may be created with C<pack("s!",(0)x$nsem)>.
 See also C<IPC::SysV> and C<IPC::Semaphore> documentation.

 =item semget KEY,NSEMS,FLAGS
diff -ruN bleadperl_old/pod/perlipc.pod bleadperl/pod/perlipc.pod
--- bleadperl_old/pod/perlipc.pod  Mon Apr 03 15:08:23 2000
+++ bleadperl/pod/perlipc.pod Mon Apr 03 15:13:10 2000
@@ -922,7 +922,7 @@
 IO::Socket module provides an object-oriented approach.  IO::Socket is
 included as part of the standard Perl distribution as of the 5.004
 release.  If you're running an earlier version of Perl, just fetch
-IO::Socket from CPAN, where you'll also find find modules providing easy
+IO::Socket from CPAN, where you'll also find modules providing easy
 interfaces to the following systems: DNS, FTP, Ident (RFC 931), NIS and
 NISPlus, NNTP, Ping, POP3, SMTP, SNMP, SSLeay, Telnet, and Time--just
 to name a few.
diff -ruN bleadperl_old/pod/perllexwarn.pod bleadperl/pod/perllexwarn.pod
--- bleadperl_old/pod/perllexwarn.pod    Mon Apr 03 15:08:23 2000
+++ bleadperl/pod/perllexwarn.pod  Mon Apr 03 15:13:29 2000
@@ -9,7 +9,7 @@

 The pragma works just like the existing "strict" pragma.
 This means that the scope of the warning pragma is limited to the
-enclosing block. It also means that that the pragma setting will not
+enclosing block. It also means that the pragma setting will not
 leak across files (via C<use>, C<require> or C<do>). This allows
 authors to independently define the degree of warning checks that will
 be applied to their module.
@@ -195,7 +195,7 @@

 =back

-The combined effect of 3 & 4 is that it will will allow code which uses
+The combined effect of 3 & 4 is that it will allow code which uses
 the C<warnings> pragma to control the warning behavior of $^W-type
 code (using a C<local $^W=0>) if it really wants to, but not vice-versa.

diff -ruN bleadperl_old/pod/perllocale.pod bleadperl/pod/perllocale.pod
--- bleadperl_old/pod/perllocale.pod     Mon Apr 03 15:08:23 2000
+++ bleadperl/pod/perllocale.pod   Mon Apr 03 15:13:39 2000
@@ -289,7 +289,7 @@
 other locale variables) may affect other programs as well, not just
 Perl.  In particular, external programs run from within Perl will see
 these changes.  If you make the new settings permanent (read on), all
-programs you run see the changes.  See L<ENVIRONMENT> for for
+programs you run see the changes.  See L<ENVIRONMENT> for
 the full list of relevant environment variables and L<USING LOCALES>
 for their effects in Perl.  Effects in other programs are
 easily deducible.  For example, the variable LC_COLLATE may well affect
diff -ruN bleadperl_old/pod/perlmodlib.pod bleadperl/pod/perlmodlib.pod
--- bleadperl_old/pod/perlmodlib.pod     Mon Apr 03 15:08:23 2000
+++ bleadperl/pod/perlmodlib.pod   Mon Apr 03 15:13:53 2000
@@ -823,7 +823,7 @@

 Extension modules are written in C (or a mix of Perl and C).  They
 are usually dynamically loaded into Perl if and when you need them,
-but may also be be linked in statically.  Supported extension modules
+but may also be linked in statically.  Supported extension modules
 include Socket, Fcntl, and POSIX.

 Many popular C extension modules do not come bundled (at least, not
diff -ruN bleadperl_old/pod/perlnumber.pod bleadperl/pod/perlnumber.pod
--- bleadperl_old/pod/perlnumber.pod     Mon Apr 03 15:08:23 2000
+++ bleadperl/pod/perlnumber.pod   Mon Apr 03 15:14:01 2000
@@ -59,7 +59,7 @@
 is no practical limit for the exponent or number of decimal digits for

diff -ruN bleadperl_old/pod/perlopentut.pod bleadperl/pod/perlopentut.pod
--- bleadperl_old/pod/perlopentut.pod    Mon Apr 03 15:08:23 2000
+++ bleadperl/pod/perlopentut.pod  Mon Apr 03 15:14:15 2000
@@ -309,7 +309,7 @@
 C<O_NOCTTY>, C<O_NDELAY> and C<O_LARGEFILE>.  Consult your open(2)
 manpage or its local equivalent for details.  (Note: starting from
 Perl release 5.6 the O_LARGEFILE flag, if available, is automatically
-added to the sysopen() flags because large files are the the default.)
+added to the sysopen() flags because large files are the default.)

 Here's how to use C<sysopen> to emulate the simple C<open> calls we had
 before.  We'll omit the C<|| die $!> checks for clarity, but make sure
diff -ruN bleadperl_old/pod/perltodo.pod bleadperl/pod/perltodo.pod
--- bleadperl_old/pod/perltodo.pod Mon Apr 03 15:08:24 2000
+++ bleadperl/pod/perltodo.pod     Mon Apr 03 15:14:29 2000
@@ -863,7 +863,7 @@

 =head2 autocroak?

-This is the Fatal.pm module, so any builtin that that does
+This is the Fatal.pm module, so any builtin that does
 not return success automatically die()s.  If you're feeling brave, tie
 this in with the unified exceptions scheme.

diff -ruN bleadperl_old/pod/perltootc.pod bleadperl/pod/perltootc.pod
--- bleadperl_old/pod/perltootc.pod      Mon Apr 03 15:08:24 2000
+++ bleadperl/pod/perltootc.pod    Mon Apr 03 15:15:23 2000
@@ -184,7 +184,7 @@
 we have much better approaches, like nested hashes or hashes of arrays.
 But there's nothing wrong with using symbolic references to manipulate
 something that is meaningful only from the perspective of the package
-symbol symbol table, like method names or package variables.  In other
+symbol table, like method names or package variables.  In other
 words, when you want to refer to the symbol table, use symbol references.

 Clustering all the class attributes in one place has several advantages.

----------------------------------------------------------------