Fix typos

For: #18201

Committer: Samanta Navarro is now a Perl author.

To keep 'make test_porting' happy:  Increment $VERSION in several files.
Regenerate uconfig.h via './perl -Ilib regen/uconfig_h.pl'.

AUTHORS

@@ -1124,6 +1124,7 @@ Salvador Ortiz Garcia          <[email protected]>
 Sam Kimbrel                    <[email protected]>
 Sam Tregar                     <[email protected]>
 Sam Vilain                     <[email protected]>
+Samanta Navarro                <[email protected]>
 Samuel Smith                   <[email protected]>
 Samuel Thibault                <[email protected]>
 Samuli Kärkkäinen              <[email protected]>

NetWare/config_H.wc

@@ -242,7 +242,7 @@
 
 /* HAS_MBLEN:
  *	This symbol, if defined, indicates that the mblen routine is available
- *	to find the number of bytes in a multibye character.
+ *	to find the number of bytes in a multibyte character.
  */
 #define HAS_MBLEN		/**/
 

Porting/Glossary

@@ -1610,7 +1610,7 @@ d_long_double_style_ieee_extended (d_longdbl.U):
 	This variable conditionally defines LONG_DOUBLE_STYLE_IEEE_EXTENDED
 	if the long double is the 80-bit IEEE 754 extended precision.
 	Note that despite the 'extended' this is less than the 'std',
-	since thisis an extension of the double precision.
+	since this is an extension of the double precision.
 
 d_long_double_style_ieee_std (d_longdbl.U):
 	This variable conditionally defines LONG_DOUBLE_STYLE_IEEE_STD
@@ -1679,7 +1679,7 @@ d_malloc_usable_size (d_malloc_size.U):
 d_mblen (d_mblen.U):
 	This variable conditionally defines the HAS_MBLEN symbol, which
 	indicates to the C program that the mblen() routine is available
-	to find the number of bytes in a multibye character.
+	to find the number of bytes in a multibyte character.
 
 d_mbrlen (d_mbrlen.U):
 	This variable conditionally defines the HAS_MBRLEN symbol if the
@@ -1704,7 +1704,7 @@ d_mbtowc (d_mbtowc.U):
 d_memmem (d_memmem.U):
 	This variable conditionally defines the HAS_MEMMEM symbol, which
 	indicates to the C program that the memmem() routine is available
-	to return a pointer to the start of the first occurance of a
+	to return a pointer to the start of the first occurrence of a
 	substring in a memory area (or NULL if not found).
 
 d_memrchr (d_memrchr.U):

Porting/config_H

@@ -224,7 +224,7 @@
 
 /* HAS_MBLEN:
  *	This symbol, if defined, indicates that the mblen routine is available
- *	to find the number of bytes in a multibye character.
+ *	to find the number of bytes in a multibyte character.
  */
 #define HAS_MBLEN		/**/
 
@@ -2984,7 +2984,7 @@
 
 /* HAS_MEMMEM:
  *	This symbol, if defined, indicates that the memmem routine is
- *	available to return a pointer to the start of the first occurance
+ *	available to return a pointer to the start of the first occurrence
  *	of a substring in a memory area (or NULL if not found).
  */
 #define HAS_MEMMEM		/**/

README.irix

@@ -57,7 +57,7 @@ Some Irix cc versions, e.g. 7.3.1.1m (try cc -version) have been known
 to have issues (coredumps) when compiling perl.c.  If you've used
 -OPT:fast_io=ON and this happens, try removing it.  If that fails, or
 you didn't use that, then try adjusting other optimization options
-(-LNO, -INLINE, -O3 to -O2, etcetera).  The compiler bug has been
+(-LNO, -INLINE, -O3 to -O2, et cetera).  The compiler bug has been
 reported to SGI.  (Allen Smith <[email protected]>)
 
 =head2 Linker Problems in Irix

README.qnx

@@ -173,7 +173,7 @@ we will pass to Configure through -Dsysroot.
 =head3 Preparing the target system
 
 It's quite possible that the target system doesn't have a readily
-available /tmp, so it's generall safer to do something like this:
+available /tmp, so it's generally safer to do something like this:
 
  $ ssh $TARGETUSER@$TARGETHOST 'rm -rf perl; mkdir perl; mkdir perl/tmp'
  $ export TARGETDIR=`ssh $TARGETUSER@$TARGETHOST pwd`/perl

README.win32

@@ -127,15 +127,15 @@ build usually works in this circumstance, but some tests will fail.
 
 The nmake that comes with Visual C++ will suffice for building. Visual C++
 requires that certain things be set up in the console before Visual C++ will
-sucessfully run. To make a console box be able to run the C compiler, you will
+successfully run. To make a console box be able to run the C compiler, you will
 need to beforehand, run C<vcvarsall.bat x86> to compile for x86-32 and for
 x86-64 C<vcvarsall.bat amd64>. On a typical install of a Microsoft C++
 compiler product, these batch files will already be in your C<PATH>
 environment variable so you may just type them without an absolute path into
 your console. If you need to find the absolute path to the batch file, it is
 usually found somewhere like
 C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC.
-With some newer Micrsoft C products (released after ~2004), the installer will
+With some newer Microsoft C products (released after ~2004), the installer will
 put a shortcut in the start menu to launch a new console window with the
 console already set up for your target architecture (x86-32 or x86-64 or IA64).
 With the newer compilers, you may also use the older batch files if you choose

config_h.SH

@@ -255,7 +255,7 @@ sed <<!GROK!THIS! >$CONFIG_H -e 's!^#undef\(.*/\)\*!/\*#define\1 \*!' -e 's!^#un
 
 /* HAS_MBLEN:
  *	This symbol, if defined, indicates that the mblen routine is available
- *	to find the number of bytes in a multibye character.
+ *	to find the number of bytes in a multibyte character.
  */
 #$d_mblen HAS_MBLEN		/**/
 
@@ -3021,7 +3021,7 @@ sed <<!GROK!THIS! >$CONFIG_H -e 's!^#undef\(.*/\)\*!/\*#define\1 \*!' -e 's!^#un
 
 /* HAS_MEMMEM:
  *	This symbol, if defined, indicates that the memmem routine is
- *	available to return a pointer to the start of the first occurance
+ *	available to return a pointer to the start of the first occurrence
  *	of a substring in a memory area (or NULL if not found).
  *	In glibc, memmem is a GNU extension.  The function is visible in
  *	libc, but the prototype is only visible if _GNU_SOURCE is #defined.

dist/ExtUtils-ParseXS/lib/perlxs.pod

@@ -2273,7 +2273,7 @@ per-thread locales.  Perl makes this transparent to perl-space code.  It
 continues to use C<POSIX::setlocale()>, and the interpreter translates
 that into the per-thread functions.
 
-All other locale-senstive functions automatically use the per-thread
+All other locale-sensitive functions automatically use the per-thread
 locale, if that is turned on, and failing that, the global locale.  Thus
 calls to C<setlocale> are ineffective on POSIX systems for the current
 thread if that thread is using a per-thread locale.  If perl is compiled

dist/I18N-LangTags/lib/I18N/LangTags.pm

@@ -18,7 +18,7 @@ our @EXPORT_OK = qw(is_language_tag same_language_tag
                );
 our %EXPORT_TAGS = ('ALL' => \@EXPORT_OK);
 
-our $VERSION = "0.44";
+our $VERSION = "0.45";
 our %Panic;
 
 sub uniq { my %seen; return grep(!($seen{$_}++), @_); } # a util function
@@ -677,7 +677,7 @@ sub alternate_language_tags {
    # And the panic languages for English is, of course, nil!
 
    # My guesses at Slavic intelligibility:
-   ([qw(ru be uk)]) x 2,  # Russian, Belarusian, Ukranian
+   ([qw(ru be uk)]) x 2,  # Russian, Belarusian, Ukrainian
    ([qw(sr hr bs)]) x 2,  # Serbian, Croatian, Bosnian
    'cs' => 'sk', 'sk' => 'cs', # Czech + Slovak
 

dist/Locale-Maketext/lib/Locale/Maketext/TPJ13.pod

@@ -460,13 +460,13 @@ numbers from the beginning of this article; obviously, you'd want to
 write only once the hairy code that, given a numeric value, would
 return some specification of which case and number a given quantified
 noun should use.  But suppose that you discover, while localizing an
-interface for, say, Ukranian (a Slavic language related to Russian,
+interface for, say, Ukrainian (a Slavic language related to Russian,
 spoken by several million people, many of whom would be relieved to
 find that your Web site's or software's interface is available in
-their language), that the rules in Ukranian are the same as in Russian
+their language), that the rules in Ukrainian are the same as in Russian
 for quantification, and probably for many other grammatical functions.
 While there may well be no phrases in common between Russian and
-Ukranian, you could still choose to have the Ukranian module inherit
+Ukrainian, you could still choose to have the Ukrainian module inherit
 from the Russian module, just for the sake of inheriting all the
 various grammatical methods.  Or, probably better organizationally,
 you could move those functions to a module called C<_E_Slavic> or

dist/Storable/Storable.pm

@@ -28,7 +28,7 @@ our @EXPORT_OK = qw(
 our ($canonical, $forgive_me);
 
 BEGIN {
-  our $VERSION = '3.22';
+  our $VERSION = '3.23';
 }
 
 our $recursion_limit;
@@ -1423,7 +1423,7 @@ Murray Nesbitt made Storable thread-safe.  Marc Lehmann added overloading
 and references to tied items support.  Benjamin Holzman added a performance
 improvement for overloaded classes; thanks to Grant Street Group for footing
 the bill.
-Reini Urban took over maintainance from p5p, and added security fixes
+Reini Urban took over maintenance from p5p, and added security fixes
 and huge object support.
 
 =head1 AUTHOR

dist/base/t/fields-5_6_0.t

@@ -182,7 +182,7 @@ ok( fstr($ph) eq 'a:1,b:2,c:3' );
 $ph = fields::phash([qw/a b c/], [1, 2, 3]);
 ok( fstr($ph) eq 'a:1,b:2,c:3' );
 
-# The way exists() works with psuedohashes changed from 5.005 to 5.6
+# The way exists() works with pseudohashes changed from 5.005 to 5.6
 $ph = fields::phash([qw/a b c/], [1]);
 if( $] > 5.006 ) {
     ok( !( exists $ph->{b} or exists $ph->{c} or !exists $ph->{a} ) );

ext/Amiga-ARexx/ARexx.pm

@@ -26,7 +26,7 @@ our @EXPORT_OK = ( @{ $EXPORT_TAGS{'all'} } );
 our @EXPORT = qw(
 );
 
-our $VERSION = '0.04';
+our $VERSION = '0.05';
 
 require XSLoader;
 XSLoader::load('Amiga::ARexx', $VERSION);
@@ -309,7 +309,7 @@ Send the "commandstring" to host "desthost" for execution. Commandstring might b
 
 	$m = $msg->message();
 
-Retreive the message "command" as a string;
+Retrieve the message "command" as a string;
 
 
 =head2 reply

ext/Devel-Peek/Peek.pm

@@ -3,7 +3,7 @@
 
 package Devel::Peek;
 
-$VERSION = '1.29';
+$VERSION = '1.30';
 $XS_VERSION = $VERSION;
 $VERSION = eval $VERSION;
 
@@ -119,7 +119,7 @@ All output is to STDERR.
 
 The C<Dump()> function takes one or two arguments: something to dump, and
 an optional limit for recursion and array elements (default is 4).  The
-first argument is evaluted in rvalue scalar context, with exceptions for
+first argument is evaluated in rvalue scalar context, with exceptions for
 @array and %hash, which dump the array or hash itself.  So C<Dump @array>
 works, as does C<Dump $foo>.  And C<Dump pos> will call C<pos> in rvalue
 context, whereas C<Dump ${\pos}> will call it in lvalue context.

ext/XS-APItest/t/clone-with-stack.t

@@ -10,7 +10,7 @@ use XS::APItest;
 # clone_with_stack creates a clone of the perl interpreter including
 # the stack, then destroys the original interpreter and runs the
 # remaining code using the new one.
-# This is like doing a psuedo-fork and exiting the parent.
+# This is like doing a pseudo-fork and exiting the parent.
 
 use Config;
 if (not $Config{'useithreads'}) {

handy.h

@@ -834,7 +834,7 @@ the variants.
 
 =cut
 
-Here and below, we add the protoypes of these macros for downstream programs
+Here and below, we add the prototypes of these macros for downstream programs
 that would be interested in them, such as Devel::PPPort
 
 =for apidoc Am|bool|isALPHANUMERIC|UV ch
@@ -2408,7 +2408,7 @@ typedef U32 line_t;
 #define OCTAL_VALUE(c) (__ASSERT_(isOCTAL(c)) (7 & (c)))
 
 /* Efficiently returns a boolean as to if two native characters are equivalent
- * case-insenstively.  At least one of the characters must be one of [A-Za-z];
+ * case-insensitively.  At least one of the characters must be one of [A-Za-z];
  * the ALPHA in the name is to remind you of that.  This is asserted() in
  * DEBUGGING builds.  Because [A-Za-z] are invariant under UTF-8, this macro
  * works (on valid input) for both non- and UTF-8-encoded bytes.

hints/aix.sh

@@ -566,7 +566,7 @@ fi
 # * Does not fully support the IEEE special numbers NaN and INF.
 # * Does not support IEEE status flags for overflow, underflow,
 #   and other conditions. These flags have no meaning for the 128-bit
-#   long double inplementation.
+#   long double implementation.
 # * The 128-bit long double data type does not support the following math
 #   APIs: atanhl, cbrtl, copysignl, exp2l, expm1l, fdiml, fmal, fmaxl,
 #   fminl, hypotl, ilogbl, llrintl, llroundl, log1pl, log2l, logbl,

locale.c

@@ -2528,7 +2528,7 @@ the other advantages of C<Perl_langinfo()>; not keeping C<LC_NUMERIC> in the C
 =item *
 
 The system function it replaces can have its static return buffer trashed,
-not only by a subesequent call to that function, but by a C<freelocale>,
+not only by a subsequent call to that function, but by a C<freelocale>,
 C<setlocale>, or other locale change.  The returned buffer of this function is
 not changed until the next call to it, so the buffer is never in a trashed
 state.

metaconfig.SH

@@ -15,7 +15,7 @@
 # H.Merijn Brand [17 Feb 2004]
 # This comment is just to ensure that Configure will find variables that
 # are removed/replaced in patches on blead, but are still needed in the
-# 5.8.x, 5.6.x and 5.005.x maintainance tracks.
+# 5.8.x, 5.6.x and 5.005.x maintenance tracks.
 # metaconfig -m will scan all .SH files on this level (not deeper), and
 # not in other subfolders. This file is as good as any .SH
 # patch   references

op.h

@@ -859,7 +859,7 @@ Return a member of the XOP structure.  C<which> is a cpp token
 indicating which entry to return.  If the member is not set
 this will return a default value.  The return type depends
 on C<which>.  This macro evaluates its arguments more than
-once.  If you are using C<Perl_custom_op_xop> to retreive a
+once.  If you are using C<Perl_custom_op_xop> to retrieve a
 C<XOP *> from a C<OP *>, use the more efficient L</XopENTRYCUSTOM> instead.
 
 =for apidoc Am||XopENTRYCUSTOM|const OP *o|which

os2/OS2/OS2-Process/Makefile.PL

@@ -35,7 +35,7 @@ sub create_constants {
 	  '-M^(HWND|WM|SC|SWP|WC|PROG|QW|EDI|WS|QWS|QWP|QWL|FF|FI|LS|FS|FCF|BS|MS|TBM|CF|CFI|FID|MB|MBID|CF|CFI|SPTR)_',
 	    '-F', '-DINCL_NLS -DINCL_BASE -DINCL_PM', # Define more symbols
 	      'os2emx.h'	# EMX version of OS/2 API
-    and warn("Can't build module with contants, falling back to no constants"),
+    and warn("Can't build module with constants, falling back to no constants"),
       return;
   rename 'OS2/Process/Const', 'Process_constants'
     or warn("Error renaming module, falling back to no constants: $!"),

pad.c

@@ -1070,7 +1070,7 @@ associated with the C<PARENT_FAKELEX_FLAGS> field of a fake pad name.
 Note that C<pad_findlex()> is recursive; it recurses up the chain of CVs,
 then comes back down, adding fake entries
 as it goes.  It has to be this way
-because fake names in anon protoypes have to store in C<xpadn_low> the
+because fake names in anon prototypes have to store in C<xpadn_low> the
 index into the parent pad.
 
 =cut

plan9/config.plan9

@@ -299,7 +299,7 @@
 
 /* HAS_MBLEN:
  *	This symbol, if defined, indicates that the mblen routine is available
- *	to find the number of bytes in a multibye character.
+ *	to find the number of bytes in a multibyte character.
  */
 #define HAS_MBLEN		/**/
 

plan9/config_h.sample

@@ -224,7 +224,7 @@
 
 /* HAS_MBLEN:
  *	This symbol, if defined, indicates that the mblen routine is available
- *	to find the number of bytes in a multibye character.
+ *	to find the number of bytes in a multibyte character.
  */
 #define HAS_MBLEN		/**/
 

pod/perl5100delta.pod

@@ -290,7 +290,7 @@ Cwd::cwd() may return a short directory name, and glob() may return short
 names as well.  On the NTFS file system these short names can always be
 represented in the ANSI codepage.  This will not be true for all other file
 system drivers; e.g. the FAT filesystem stores short filenames in the OEM
-codepage, so some files on FAT volumes remain unaccessible through the
+codepage, so some files on FAT volumes remain inaccessible through the
 ANSI APIs.
 
 Similarly, $^X, @INC, and $ENV{PATH} are preprocessed at startup to make

pod/perl5180delta.pod

@@ -792,7 +792,7 @@ Perl's future on them, please contact us.
 
 We believe that Perl has long been unable to build on mixed endian
 architectures (such as PDP-11s), and intend to remove any remaining
-support code. Similarly, code supporting the long umaintained GNU
+support code. Similarly, code supporting the long unmaintained GNU
 dld will be removed soon if no-one makes themselves known as an
 active user.
 

pod/perl5200delta.pod

@@ -2497,7 +2497,7 @@ a NULL C<sv> being passed to sv_2*v* functions, is if XS code defines its own
 getter type Sv*V* macros, which check for NULL B<before> dereferencing and
 checking the SV's flags through public API Sv*OK* macros or directly using
 private API C<SvFLAGS>, and if C<sv> is NULL, then calling the sv_2*v functions
-with a NULL litteral or passing the C<sv> containing a NULL value.
+with a NULL literal or passing the C<sv> containing a NULL value.
 
 =item *
 
@@ -2914,7 +2914,7 @@ to, even when the subroutine was not an lvalue sub.  This has been fixed.
 In Perl v5.18.0 dualvars that had an empty string for the string part but a
 non-zero number for the number part starting being treated as true.  In
 previous versions they were treated as false, the string representation
-taking precedeence.  The old behaviour has been restored. [RT #118159]
+taking precedence.  The old behaviour has been restored. [RT #118159]
 
 =item *
 
@@ -3544,7 +3544,7 @@ An initial C<{> at the beginning of a format argument line was always
 interpreted as the beginning of a block prior to v5.18.  In Perl v5.18, it
 started being treated as an ambiguous token.  The parser would guess
 whether it was supposed to be an anonymous hash constructor or a block
-based on the contents.  Now the previous behavious has been restored.
+based on the contents.  Now the previous behaviour has been restored.
 [perl #119973]
 
 =item *

pod/perl5220delta.pod

@@ -683,8 +683,8 @@ C<qr//blahblah> op.
 C<B::PMOP> now provides a C<pmregexp> method returning a C<B::REGEXP> object.
 Two new classes, C<B::PADNAME> and C<B::PADNAMELIST>, have been introduced.
 
-A bug where, after an ithread creation or psuedofork, special/immortal SVs in
-the child ithread/psuedoprocess did not have the correct class of
+A bug where, after an ithread creation or pseudofork, special/immortal SVs in
+the child ithread/pseudoprocess did not have the correct class of
 C<B::SPECIAL>, has been fixed.
 The C<id> and C<outid> PADLIST methods have been added.
 

pod/perldata.pod

@@ -126,7 +126,7 @@ rules apply:
 That is, a "start" character followed by any number of "continue"
 characters.  Perl requires every character in an identifier to also
 match C<\w> (this prevents some problematic cases); and Perl
-additionally accepts identfier names beginning with an underscore.
+additionally accepts identifier names beginning with an underscore.
 
 If not under C<use utf8>, the source is treated as ASCII + 128 extra
 generic characters, and identifiers should match

pod/perldiag.pod

@@ -3409,7 +3409,7 @@ The other common cause is for the characters
 
  $ + < = > ^ ` | ~
 
-These are probematic.  The C standard says that these should be
+These are problematic.  The C standard says that these should be
 considered punctuation in the C locale (and the POSIX standard defers to
 the C standard), and Unicode is generally considered a superset of
 the C locale.  But Unicode has added an extra category, "Symbol", and