develooper Front page | perl.perl5.porters | Postings from January 2011

[perl #81906] [PATCH] Fix typos in pod/*

Thread Next
January 7, 2011 01:57
[perl #81906] [PATCH] Fix typos in pod/*
Message ID:
# New Ticket Created by  (Peter J. Acklam) 
# Please include the string:  [perl #81906]
# in the subject line of all future correspondence about this issue. 
# <URL: >

 pod/buildtoc            |    2 +-
 pod/perl5110delta.pod   |    6 +++---
 pod/perl5120delta.pod   |    6 +++---
 pod/perl5121delta.pod   |    2 +-
 pod/perl5130delta.pod   |    2 +-
 pod/perl5136delta.pod   |    6 +++---
 pod/perl572delta.pod    |    4 ++--
 pod/perl589delta.pod    |    6 +++---
 pod/perldiag.pod        |    4 ++--
 pod/perlebcdic.pod      |    2 +-
 pod/perlfaq3.pod        |    4 ++--
 pod/perlfaq4.pod        |    6 +++---
 pod/perlfaq6.pod        |    2 +-
 pod/perlfaq9.pod        |    2 +-
 pod/perlfunc.pod        |    2 +-
 pod/perlglossary.pod    |   10 +++++-----
 pod/perlhack.pod        |    2 +-
 pod/perlipc.pod         |    2 +-
 pod/perlmod.pod         |    4 ++--
 pod/perlport.pod        |    2 +-
 pod/perlreapi.pod       |    2 +-
 pod/perlrebackslash.pod |    2 +-
 pod/perlsyn.pod         |    2 +-
 pod/perlthrtut.pod      |    4 ++--
 pod/perltodo.pod        |    4 ++--
 pod/perlunicode.pod     |    2 +-
 pod/perlvms.pod         |    6 +++---
 27 files changed, 49 insertions(+), 49 deletions(-)

diff --git a/pod/buildtoc b/pod/buildtoc
index 418133b..401201f 100644
--- a/pod/buildtoc
+++ b/pod/buildtoc
@@ -526,7 +526,7 @@ sub generate_perlpod {
 sub generate_manifest {
-  # Annyoingly unexpand doesn't consider it good form to replace a single
+  # Annoyingly, unexpand doesn't consider it good form to replace a single
   # space before a tab with a tab
   # Annoyingly (2) it returns read only values.
   my @temp = unexpand (map {sprintf "%-32s%s\n", @$_} @_);
diff --git a/pod/perl5110delta.pod b/pod/perl5110delta.pod
index 1b722ed..7ceb174 100644
--- a/pod/perl5110delta.pod
+++ b/pod/perl5110delta.pod
@@ -32,7 +32,7 @@ to match whichever property they like, including the new artificial definitions.
 B<NOTE:> This is a backwards incompatible no-warning change in behaviour. If you are upgrading
 and you process large volumes of text look for POSIX and Perl style character classes and
-change them to the relevent property name (by removing the word 'Posix' from the current name).
+change them to the relevant property name (by removing the word 'Posix' from the current name).
 The following table maps the POSIX character class names, the escapes and the old and new
 Unicode property mappings:
@@ -63,7 +63,7 @@ in regcomp.h, and then setting
-to true your enviornment when testing.
+to true your environment when testing.
 =head2 @INC reorganization
@@ -1544,7 +1544,7 @@ simpler to spot and correct the suspicious character.
 =item *
-Explicitely point to $. when it causes an uninitialized warning for ranges in scalar context
+Explicitly point to $. when it causes an uninitialized warning for ranges in scalar context
 =item *
diff --git a/pod/perl5120delta.pod b/pod/perl5120delta.pod
index afe6773..cfee564 100644
--- a/pod/perl5120delta.pod
+++ b/pod/perl5120delta.pod
@@ -287,7 +287,7 @@ those installed in C<ARCHLIB> and C<PRIVLIB>.
 =head2 REGEXPs are now first class
-Internally, Perl now treates compiled regular expressions (such as
+Internally, Perl now treats compiled regular expressions (such as
 those created with C<qr//>) as first class entities. Perl modules which
 serialize, deserialize or otherwise have deep interaction with Perl's
 internal data structures need to be updated for this change.  Most
@@ -589,7 +589,7 @@ on CPAN which require these should add them to their prerequisites. The
 core versions of these modules warnings will issue a deprecation warning.
 If you ship a packaged version of Perl, either alone or as part of a
-larger system, then you should carefully consider the reprecussions of
+larger system, then you should carefully consider the repercussions of
 core module deprecations. You may want to consider shipping your default
 build of Perl with packages for some or all deprecated modules which
 install into C<vendor> or C<site> perl library directories. This will
@@ -1667,7 +1667,7 @@ C<\N{...}> now compiles better, always forces UTF-8 internal representation
 Perl's developers have fixed several problems with the recognition of
 C<\N{...}> constructs.  As part of this, perl will store any scalar
 or regex containing C<\N{I<name>}> or C<\N{U+I<wide hex char>}> in its
-definition in UTF-8 format. (This was true previously for all occurences
+definition in UTF-8 format. (This was true previously for all occurrences
 of C<\N{I<name>}> that did not use a custom translator, but now it's
 always true.)
diff --git a/pod/perl5121delta.pod b/pod/perl5121delta.pod
index ca922bc..37ac9b4 100644
--- a/pod/perl5121delta.pod
+++ b/pod/perl5121delta.pod
@@ -60,7 +60,7 @@ We made a small fix to the L<CPANPLUS> test suite to fix an occasional spurious
 =item *
-We upgraded L<Safe> to version 2.27 to wrap coderefs retured by C<reval()> and C<rdo()>.
+We upgraded L<Safe> to version 2.27 to wrap coderefs returned by C<reval()> and C<rdo()>.
diff --git a/pod/perl5130delta.pod b/pod/perl5130delta.pod
index 9fbe1cc..c5d5169 100644
--- a/pod/perl5130delta.pod
+++ b/pod/perl5130delta.pod
@@ -22,7 +22,7 @@ should give a few percent speed increase, and eliminates almost all of
 the speed penalty caused by the introduction of "safe signals" in
 5.8.0. Signals should still be dispatched within the same statement as
 they were previously - if this is not the case, or it is possible to
-create uninterruptable loops, this is a bug, and reports are encouraged
+create uninterruptible loops, this is a bug, and reports are encouraged
 of how to recreate such issues.
 =head2 Assignment to C<$0> sets the legacy process name with C<prctl()> on Linux
diff --git a/pod/perl5136delta.pod b/pod/perl5136delta.pod
index b285209..f812257 100644
--- a/pod/perl5136delta.pod
+++ b/pod/perl5136delta.pod
@@ -17,7 +17,7 @@ L<perl5135delta>, which describes differences between 5.13.4 and
 =head2  C<(?^...)> regex construct added to signify default modifiers
-A caret (also called a "cirumflex accent") C<"^"> immediately following
+A caret (also called a "circumflex accent") C<"^"> immediately following
 a C<"(?"> in a regular expression now means that the subexpression is to
 not inherit the surrounding modifiers such as C</i>, but to revert to the
 Perl defaults.  Any modifiers following the caret override the defaults.
@@ -290,7 +290,7 @@ working with tainted values
 (L<CPAN RT #40727|>).
 C<< ->maketext >> calls will now backup and restore C<$@> so that error
-messages are not supressed
+messages are not suppressed
 (L<CPAN RT #34182|>).
 =item *
@@ -666,7 +666,7 @@ fixed.
 =item *
 C<sort> with a custom sort routine could crash if too many nested
-subroutine calls occurrred from within the sort routine
+subroutine calls occurred from within the sort routine
 L<[perl #77930]|>.
 This bug was introduced in an earlier 5.13 release, and did not affect
diff --git a/pod/perl572delta.pod b/pod/perl572delta.pod
index 21585ed..67d0912 100644
--- a/pod/perl572delta.pod
+++ b/pod/perl572delta.pod
@@ -760,10 +760,10 @@ hard-to-fix ways.  As a stop-gap measure to avoid people from getting
 frustrated at the mysterious results (core dumps, most often) it is
 for now forbidden (you will get a fatal error even from an attempt).
-=head2 Variable Attributes are not Currently Usable for Tieing
+=head2 Variable Attributes are not Currently Usable for Tying
 This limitation will hopefully be fixed in future.  (Subroutine
-attributes work fine for tieing, see L<Attribute::Handlers>).
+attributes work fine for tying, see L<Attribute::Handlers>).
 =head2 Building Extensions Can Fail Because Of Largefiles
diff --git a/pod/perl589delta.pod b/pod/perl589delta.pod
index 2070cc3..8cd1cf6 100644
--- a/pod/perl589delta.pod
+++ b/pod/perl589delta.pod
@@ -92,7 +92,7 @@ C<system> operator. See L<perlvar> for details. (Contributed by Gisle Aas.)
 This variable controls the state of the internal UTF-8 offset caching code.
 1 for on (the default), 0 for off, -1 to debug the caching code by checking
-all its results against linear scans, and panicing on any discrepancy.
+all its results against linear scans, and panicking on any discrepancy.
@@ -1655,7 +1655,7 @@ a C<system> call.
 =item *
-Fixed bug RT #37886, symbolic deferencing was allowed in the argument of
+Fixed bug RT #37886, symbolic dereferencing was allowed in the argument of
 C<defined> even under the influence of C<use strict 'refs'>.
 =item *
@@ -1811,7 +1811,7 @@ The process id is no longer truncated to 16 bits on some Windows platforms
 =item *
-Fixed bug RT #54828 in F<perlio.c> where calling C<binmode> on Win32 and Cgywin
+Fixed bug RT #54828 in F<perlio.c> where calling C<binmode> on Win32 and Cygwin
 may cause a segmentation fault.
diff --git a/pod/perldiag.pod b/pod/perldiag.pod
index aa1f5c4..0fd2f26 100644
--- a/pod/perldiag.pod
+++ b/pod/perldiag.pod
@@ -84,7 +84,7 @@ dereferenced according to its overloading, not its underlying reference type.
 The warning is issued when C<%{}> overloading exists on a blessed arrayref,
 when C<@{}> overloading exists on a blessed hashref, or when both overloadings
 are defined (in which case C<%{}> is used).  You can force the interpretation
-of the object by explictly dereferencing it as an array or hash instead of
+of the object by explicitly dereferencing it as an array or hash instead of
 passing the object itself to C<keys>, C<values> or C<each>.
 =item Ambiguous range in transliteration operator
@@ -5125,7 +5125,7 @@ to be huge numbers, and so usually indicates programmer error.
 If you really do mean it, explicitly numify your reference, like so:
 C<$array[0+$ref]>.  This warning is not given for overloaded objects,
 either, because you can overload the numification and stringification
-operators and then you assumably know what you are doing.
+operators and then you presumably know what you are doing.
 =item Use of reserved word "%s" is deprecated
diff --git a/pod/perlebcdic.pod b/pod/perlebcdic.pod
index d4fffee..f6cf3ba 100644
--- a/pod/perlebcdic.pod
+++ b/pod/perlebcdic.pod
@@ -1272,7 +1272,7 @@ omitted for brevity):
     $string =~ s/=([0-9A-Fa-f][0-9A-Fa-f])/chr $a2e[hex $1]/ge;
     $string =~ s/=[\n\r]+$//;
-=head2 Caesarian ciphers
+=head2 Caesarean ciphers
 The practice of shifting an alphabet one or more characters for encipherment
 dates back thousands of years and was explicitly detailed by Gaius Julius
diff --git a/pod/perlfaq3.pod b/pod/perlfaq3.pod
index e2fe116..66c3272 100644
--- a/pod/perlfaq3.pod
+++ b/pod/perlfaq3.pod
@@ -267,7 +267,7 @@ Ctags uses an index to quickly find things in source code, and many
 popular editors support ctags for several different languages,
 including Perl.
-Exuberent ctags supports Perl:
+Exuberant ctags supports Perl:
 You might also try pltags:
@@ -583,7 +583,7 @@ These are Perl bindings for the Gtk toolkit ( ). The
 interface changed significantly between versions 1 and 2 so they have
 separate Perl modules. It runs under Unix, Win32 and Mac OS X (currently
 it requires an X server on Mac OS, but a 'native' port is underway), and
-the widgets look the same on every plaform: i.e., they don't match the
+the widgets look the same on every platform: i.e., they don't match the
 native widgets. As with Wx, the Perl bindings follow the C API closely,
 and the documentation requires you to read the C documentation to
 understand it.
diff --git a/pod/perlfaq4.pod b/pod/perlfaq4.pod
index 392ed97..bf00acc 100644
--- a/pod/perlfaq4.pod
+++ b/pod/perlfaq4.pod
@@ -1221,7 +1221,7 @@ for list operations, so list operations also work on arrays:
 	wash_animals( qw( dog cat bird ) );
 	wash_animals( @animals );
-Array operations, which change the scalars, reaaranges them, or adds
+Array operations, which change the scalars, rearranges them, or adds
 or subtracts some scalars, only work on arrays. These can't work on a
 list, which is fixed. Array operations include C<shift>, C<unshift>,
 C<push>, C<pop>, and C<splice>.
@@ -1268,7 +1268,7 @@ context. The comma operator (yes, it's an operator!) in scalar
 context evaluates its lefthand side, throws away the result, and
 evaluates it's righthand side and returns the result. In effect,
 that list-lookalike assigns to C<$scalar> it's rightmost value. Many
-people mess this up becuase they choose a list-lookalike whose
+people mess this up because they choose a list-lookalike whose
 last element is also the count they expect:
 	my $scalar = ( 1, 2, 3 );  # $scalar gets 3, accidentally
@@ -1714,7 +1714,7 @@ Or, simply:
 	my $element = $array[ rand @array ];
 =head2 How do I permute N elements of a list?
-X<List::Permuter> X<permute> X<Algorithm::Loops> X<Knuth>
+X<List::Permutor> X<permute> X<Algorithm::Loops> X<Knuth>
 X<The Art of Computer Programming> X<Fischer-Krause>
 Use the C<List::Permutor> module on CPAN. If the list is actually an
diff --git a/pod/perlfaq6.pod b/pod/perlfaq6.pod
index 0238c9a..a705988 100644
--- a/pod/perlfaq6.pod
+++ b/pod/perlfaq6.pod
@@ -770,7 +770,7 @@ though.
 For more details on regular expression efficiency, see I<Mastering
-Regular Expressions> by Jeffrey Freidl. He explains how regular
+Regular Expressions> by Jeffrey Friedl. He explains how regular
 expressions engine work and why some patterns are surprisingly
 inefficient. Once you understand how perl applies regular expressions,
 you can tune them for individual situations.
diff --git a/pod/perlfaq9.pod b/pod/perlfaq9.pod
index 0c382f6..41de7e8 100644
--- a/pod/perlfaq9.pod
+++ b/pod/perlfaq9.pod
@@ -659,7 +659,7 @@ This can make tasks like fetching the newsgroup list as simple as
 (contributed by brian d foy)
-The C<LWP> family of modules (available on CPAN as the libwww-perl distibution)
+The C<LWP> family of modules (available on CPAN as the libwww-perl distribution)
 can work with FTP just like it can with many other protocols. C<LWP::Simple>
 makes it quite easy to fetch a file:
diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index f1df33c..ec265b1 100644
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -7675,7 +7675,7 @@ and C<${^CHILD_ERROR_NATIVE}>.
 Note that a return value of C<-1> could mean that child processes are
 being automatically reaped, as described in L<perlipc>.
-If you use wait in your handler for $SIG{CHLD} it may accidently wait for the
+If you use wait in your handler for $SIG{CHLD} it may accidentally for the
 child created by qx() or system(). See L<perlipc> for details.
 =item waitpid PID,FLAGS
diff --git a/pod/perlglossary.pod b/pod/perlglossary.pod
index bbd1434..c4fb406 100644
--- a/pod/perlglossary.pod
+++ b/pod/perlglossary.pod
@@ -507,7 +507,7 @@ the class (its L<objects|/object>).  See also L</inheritance>.
 =item class method
-A L</method> whose L</invocant> is a L</package> name, not an
+A L</method> whose L</invocand> is a L</package> name, not an
 L</object> reference.  A method associated with the class as a whole.
 =item client
@@ -1470,7 +1470,7 @@ Perl, C<print STDOUT "$foo\n";> can be understood as "verb
 indirect-object object" where L</STDOUT> is the recipient of the
 L<print|perlfunc/print> action, and C<"$foo"> is the object being
 printed.  Similarly, when invoking a L</method>, you might place the
-invocant between the method and its arguments:
+invocand between the method and its arguments:
   $gollum = new Pathetic::Creature "Smeagol";
   give $gollum "Fisssssh!";
@@ -1548,11 +1548,11 @@ of compiler that takes a program and turns it into a more executable
 form (L<syntax trees|/syntax tree>) within the I<perl> process itself,
 which the Perl L</run time> system then interprets.
-=item invocant
+=item invocand
 The agent on whose behalf a L</method> is invoked.  In a L</class>
-method, the invocant is a package name.  In an L</instance> method,
-the invocant is an object reference.
+method, the invocand is a package name.  In an L</instance> method,
+the invocand is an object reference.
 =item invocation
diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index ab82c30..c8b0065 100644
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -244,7 +244,7 @@ If you are a member of the perl5-porters mailing list, it is a good
 thing to keep in touch with the most recent changes. If not only to
 verify if what you would have posted as a bug report isn't already
 solved in the most recent available perl development branch, also
-known as perl-current, bleading edge perl, bleedperl or bleadperl.
+known as perl-current, bleeding edge perl, bleedperl or bleadperl.
 Needless to say, the source code in perl-current is usually in a perpetual
 state of evolution.  You should expect it to be very buggy.  Do B<not> use
diff --git a/pod/perlipc.pod b/pod/perlipc.pod
index 6225d95..3009913 100644
--- a/pod/perlipc.pod
+++ b/pod/perlipc.pod
@@ -398,7 +398,7 @@ C<waitpid> calls will always be retried.
 =item Signals as "faults"
 Certain signals like SEGV, ILL, and BUS are generated by virtual memory
-addressing errors and similiar "faults". These are normally fatal: there is
+addressing errors and similar "faults". These are normally fatal: there is
 little a Perl-level handler can do with them.  So Perl now delivers them
 immediately rather than attempting to defer them.
diff --git a/pod/perlmod.pod b/pod/perlmod.pod
index 7c5358f..1a166a8 100644
--- a/pod/perlmod.pod
+++ b/pod/perlmod.pod
@@ -571,7 +571,7 @@ like for example handle the cloning of non-Perl data, if necessary.
 C<CLONE> will be called once as a class method for every package that has it
 defined (or inherits it).  It will be called in the context of the new thread,
 so all modifications are made in the new area.  Currently CLONE is called with
-no parameters other than the invocant package name, but code should not assume
+no parameters other than the invocand package name, but code should not assume
 that this will remain unchanged, as it is likely that in future extra parameters
 will be passed in to give more information about the state of cloning.
@@ -593,7 +593,7 @@ to make use of the objects, then a more sophisticated approach is
 Like C<CLONE>, C<CLONE_SKIP> is currently called with no parameters other
-than the invocant package name, although that may change. Similarly, to
+than the invocand package name, although that may change. Similarly, to
 allow for future expansion, the return value should be a single C<0> or
 C<1> value.
diff --git a/pod/perlport.pod b/pod/perlport.pod
index fc3acab..234db2d 100644
--- a/pod/perlport.pod
+++ b/pod/perlport.pod
@@ -1187,7 +1187,7 @@ feature known as extended names.  On these releases, file names
 can contain up to 255 characters, are prohibited from starting
 with a C<-> character, and the set of prohibited characters is
 reduced to any character matching C<< tr/#%*<>?// >>.  There are
-restrictions involving spaces and apostrophies:  these characters
+restrictions involving spaces and apostrophes:  these characters
 must not begin or end a name, nor can they immediately precede or
 follow a period.  Additionally, a space must not immediately
 precede another space or hyphen.  Specifically, the following
diff --git a/pod/perlreapi.pod b/pod/perlreapi.pod
index cc76502..dfe7af5 100644
--- a/pod/perlreapi.pod
+++ b/pod/perlreapi.pod
@@ -317,7 +317,7 @@ behave in the same situation:
     package main;
-    tie my $sv => "CatptureVar";
+    tie my $sv => "CaptureVar";
     $sv =~ y/a/b/;
 Because C<$sv> is C<undef> when the C<y///> operator is applied to it
diff --git a/pod/perlrebackslash.pod b/pod/perlrebackslash.pod
index 9bab138..1b0689b 100644
--- a/pod/perlrebackslash.pod
+++ b/pod/perlrebackslash.pod
@@ -227,7 +227,7 @@ form.
 In some contexts, a backslash followed by two or even one octal digits may be
 interpreted as an octal escape, sometimes with a warning, and because of some
 bugs, sometimes with surprising results.  Also, if you are creating a regex
-out of smaller snippets concatentated together, and you use fewer than three
+out of smaller snippets concatenated together, and you use fewer than three
 digits, the beginning of one snippet may be interpreted as adding digits to the
 ending of the snippet before it.  See L</Absolute referencing> for more
 discussion and examples of the snippet problem.
diff --git a/pod/perlsyn.pod b/pod/perlsyn.pod
index bb2a9ce..5564b4d 100644
--- a/pod/perlsyn.pod
+++ b/pod/perlsyn.pod
@@ -936,7 +936,7 @@ most C preprocessors: it matches the regular expression
 with C<$1> being the line number for the next line, and C<$3> being
 the optional filename (specified with or without quotes). Note that
-no whitespace may preceed the C<< # >>, unlike modern C preprocessors.
+no whitespace may precede the C<< # >>, unlike modern C preprocessors.
 There is a fairly obvious gotcha included with the line directive:
 Debuggers and profilers will only show the last source line to appear
diff --git a/pod/perlthrtut.pod b/pod/perlthrtut.pod
index fb947b6..30f8357 100644
--- a/pod/perlthrtut.pod
+++ b/pod/perlthrtut.pod
@@ -1080,13 +1080,13 @@ on your way to becoming a threaded Perl expert.
 Annotated POD for L<threads>:
-Lastest version of L<threads> on CPAN:
+Latest version of L<threads> on CPAN:
 Annotated POD for L<threads::shared>:
-Lastest version of L<threads::shared> on CPAN:
+Latest version of L<threads::shared> on CPAN:
 Perl threads mailing list:
diff --git a/pod/perltodo.pod b/pod/perltodo.pod
index 3bd0c06..e77f501 100644
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -189,7 +189,7 @@ The F<installman> script is slow. All it is doing text processing, which we're
 told is something Perl is good at. So it would be nice to know what it is doing
 that is taking so much CPU, and where possible address it.
-=head2 enable lexical enabling/disabling of inidvidual warnings
+=head2 enable lexical enabling/disabling of individual warnings
 Currently, warnings can only be enabled or disabled by category. There
 are times when it would be useful to quash a single warning, not a
@@ -929,7 +929,7 @@ be C<*$> instead. (This is changed in F<>)
 Currently C<$foo ~~ $object> will die with the message "Smart matching a
 non-overloaded object breaks encapsulation". It would be nice to allow
-to bypass this by using explictly the syntax C<$foo ~~ %$object> or
+to bypass this by using explicitly the syntax C<$foo ~~ %$object> or
 C<$foo ~~ @$object>.
 =head2 error reporting of [$a ; $b]
diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod
index 242238f..0ca64ad 100644
--- a/pod/perlunicode.pod
+++ b/pod/perlunicode.pod
@@ -456,7 +456,7 @@ written right to left.
 The world's languages are written in a number of scripts.  This sentence
 (unless you're reading it in translation) is written in Latin, while Russian is
-written in Cyrllic, and Greek is written in, well, Greek; Japanese mainly in
+written in Cyrillic, and Greek is written in, well, Greek; Japanese mainly in
 Hiragana or Katakana.  There are many more.
 The Unicode Script property gives what script a given character is in,
diff --git a/pod/perlvms.pod b/pod/perlvms.pod
index 17175db..fe2b5d8 100644
--- a/pod/perlvms.pod
+++ b/pod/perlvms.pod
@@ -265,14 +265,14 @@ created by an older version of an archive utility or a build utility
 such as MMK or MMS may generate a filename in all upper case even on an
 ODS-5 volume.  If this filename is later retrieved by a Perl script or
 module in a case preserving environment, that upper case name may not
-match the mixed-case or lower-case expections of the Perl code.  Your
+match the mixed-case or lower-case exceptions of the Perl code.  Your
 best bet is to follow an all-or-nothing approach to case preservation:
 either don't use it at all, or make sure your entire toolchain and
 application environment support and use it.
 OpenVMS Alpha v7.3-1 and later and all version of OpenVMS I64 support
 case sensitivity as a process setting (see C<SET PROCESS
-/CASE_LOOKUP=SENSITIVE>). Perl does not currently suppport case
+/CASE_LOOKUP=SENSITIVE>). Perl does not currently support case
 sensitivity on VMS, but it may in the future, so Perl programs should
 use the C<< File::Spec->case_tolerant >> method to determine the state, and
 not the C<$^O> variable.
@@ -1188,7 +1188,7 @@ consequence of ignoring this advice will be undefined to allow future
 improvements in the POSIX exit handling.
 In general, with C<PERL_VMS_POSIX_EXIT> enabled, more detailed information
-will be availble in the exit status for DCL scripts or other native VMS tools,
+will be available in the exit status for DCL scripts or other native VMS tools,
 and will give the expected information for Posix programs.  It has not been
 made the default in order to preserve backward compatibility.

Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About