Typos in *.p[lm]

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

p4raw-id: //depot/perl@25266

diff --git a/ext/Encode/lib/Encode/PerlIO.pod b/ext/Encode/lib/Encode/PerlIO.pod
index 1b0547f..abd1f2d 100644 (file)
--- a/ext/Encode/lib/Encode/PerlIO.pod
+++ b/ext/Encode/lib/Encode/PerlIO.pod
@@ -140,7 +140,7 @@ headers.  See L<Encode::MIME::Header> for details.
 
 As of this writing, any encoding whose class belongs to Encode::XS and
 Encode::Unicode works.  The Encode module has a C<perlio_ok> method
-which you can use before appling PerlIO encoding to the filehandle.
+which you can use before applying PerlIO encoding to the filehandle.
 Here is an example:
 
   my $use_perlio = perlio_ok($enc);

diff --git a/ext/Encode/lib/Encode/Supported.pod b/ext/Encode/lib/Encode/Supported.pod
index 7a535c6..fab86e9 100644 (file)
--- a/ext/Encode/lib/Encode/Supported.pod
+++ b/ext/Encode/lib/Encode/Supported.pod
@@ -94,7 +94,7 @@ To find how (UCS-2|UTF-(16|32))(LE|BE)? differ from one another,
 see L<Encode::Unicode>. 
 
 UTF-7 is a special encoding which "re-encodes" UTF-16BE into a 7-bit
-encoding.  It is implemeneted seperately by Encode::Unicode::UTF7.
+encoding.  It is implemented seperately by Encode::Unicode::UTF7.
 
 =head2 Encode::Byte -- Extended ASCII
 

diff --git a/lib/ExtUtils/MM_Win95.pm b/lib/ExtUtils/MM_Win95.pm
index d0e2cb2..003f810 100644 (file)
--- 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 b64d248..facc42c 100644 (file)
--- 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 9858f2b..4e7d462 100644 (file)
--- 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 15b51b8..bfecee5 100644 (file)
--- 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 7a6c084..b730918 100644 (file)
--- 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.
 

diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index 63fba1d..cb66169 100644 (file)
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -3373,7 +3373,7 @@ of values, as follows:
 
     a  A string with arbitrary binary data, will be null padded.
     A  A text (ASCII) string, will be space padded.
-    Z  A null terminated (ASCIZ) string, will be null padded.
+    Z  A null terminated (ASCIIZ) string, will be null padded.
 
     b  A bit string (ascending bit order inside each byte, like vec()).
     B  A bit string (descending bit order inside each byte).

diff --git a/pod/perltoc.pod b/pod/perltoc.pod
index 26dba85..dd01b90 100644 (file)
--- a/pod/perltoc.pod
+++ b/pod/perltoc.pod
@@ -13409,7 +13409,7 @@ CHECK]);
 
 =item Handling Malformed Data
 
-B<NOTE:> Not all encoding suppport this feature, I<CHECK> =
+B<NOTE:> Not all encoding support this feature, I<CHECK> =
 Encode::FB_DEFAULT ( == 0), I<CHECK> = Encode::FB_CROAK ( == 1), I<CHECK> =
 Encode::FB_QUIET, I<CHECK> = Encode::FB_WARN, perlqq mode (I<CHECK> =
 Encode::FB_PERLQQ), HTML charref mode (I<CHECK> = Encode::FB_HTMLCREF), XML
@@ -15251,7 +15251,7 @@ os_flavor
 
 =over 4
 
-=item Overriden methods
+=item Overridden methods
 
 xs_c