Typos in *.p[lm]

From: "Piotr Fusik" <pfusik@op.pl>
Message-ID: <001401c595bd$dccb5d80$0bd34dd5@piec>

p4raw-id: //depot/perl@25266

5 files changed, 5 insertions, 5 deletions

diff --git a/lib/ExtUtils/MM_Win95.pm b/lib/ExtUtils/MM_Win95.pm
index d0e2cb2af3..003f810fb0 100644
--- a/lib/ExtUtils/MM_Win95.pm
+++ b/lib/ExtUtils/MM_Win95.pm
@@ -22,7 +22,7 @@ ExtUtils::MM_Win95 - method to customize MakeMaker for Win9X
 This is a subclass of ExtUtils::MM_Win32 containing changes necessary
 to get MakeMaker playing nice with command.com and other Win9Xisms.
 
-=head2 Overriden methods
+=head2 Overridden methods
 
 Most of these make up for limitations in the Win9x/nmake command shell.
 Mostly its lack of &&.
diff --git a/lib/ExtUtils/MakeMaker/FAQ.pod b/lib/ExtUtils/MakeMaker/FAQ.pod
index b64d2483f0..facc42c601 100644
--- a/lib/ExtUtils/MakeMaker/FAQ.pod
+++ b/lib/ExtUtils/MakeMaker/FAQ.pod
@@ -151,7 +151,7 @@ To shut off its generation, pass the C<NO_META> flag to C<WriteMakefile()>.
 
 XS code is very sensitive to the module version number and will
 complain if the version number in your Perl module doesn't match.  If
-you change your module's version # without reruning Makefile.PL the old
+you change your module's version # without rerunning Makefile.PL the old
 version number will remain in the Makefile causing the XS code to be built
 with the wrong number.
 
diff --git a/lib/Net/libnetFAQ.pod b/lib/Net/libnetFAQ.pod
index 9858f2b5e1..4e7d46218c 100644
--- a/lib/Net/libnetFAQ.pod
+++ b/lib/Net/libnetFAQ.pod
@@ -84,7 +84,7 @@ An example taken from an article posted to comp.lang.perl.misc
 
     use Net::FTP;
 
-    # for debuging: $ftp = Net::FTP->new('site','Debug',10);
+    # for debugging: $ftp = Net::FTP->new('site','Debug',10);
     # open a connection and log in!
 
     $ftp = Net::FTP->new('target_site.somewhere.xxx');
diff --git a/lib/Test/Harness/TAP.pod b/lib/Test/Harness/TAP.pod
index 15b51b8725..bfecee5266 100644
--- a/lib/Test/Harness/TAP.pod
+++ b/lib/Test/Harness/TAP.pod
@@ -294,7 +294,7 @@ This listing shows that the entire listing is a skip. No tests were run.
 =head2 Got spare tuits?
 
 The following example reports that four tests are run and the last two
-tests failed. However, becauses the failing tests are marked as things
+tests failed. However, because the failing tests are marked as things
 to do later, they are considered successes. Thus, a harness should report
 this entire listing as a success.
 
diff --git a/lib/Test/Tutorial.pod b/lib/Test/Tutorial.pod
index 7a6c084d31..b730918c75 100644
--- a/lib/Test/Tutorial.pod
+++ b/lib/Test/Tutorial.pod
@@ -174,7 +174,7 @@ run that and you get:
     # Looks like you failed 1 tests of 8.
 
 Whoops, a failure! [4] Test::Simple helpfully lets us know on what line
-the failure occured, but not much else.  We were supposed to get 17,
+the failure occurred, but not much else.  We were supposed to get 17,
 but we didn't.  What did we get??  Dunno.  We'll have to re-run the
 test in the debugger or throw in some print statements to find out.