multifile patch against blead/pod/*.pod

I mostly fixed spelling mistakes, some of very long standing,
but a few files got more attentive word-smithying.  I've updated:

    pod/perl.pod

    pod/perldelta.pod
    pod/perl592delta.pod
    pod/perl5120delta.pod
    pod/perl51310delta.pod
    pod/perl5139delta.pod

    pod/perlfunc.pod
    pod/perlop.pod

    pod/perlrebackslash.pod
    pod/perlrecharclass.pod

    pod/perlutil.pod

    pod/perlhack.pod
    pod/perlintern.pod
    pod/perlnetware.pod
    pod/perlpolicy.pod

1 files changed, 95 insertions, 92 deletions

diff --git a/pod/perlrecharclass.pod b/pod/perlrecharclass.pod
index de2256f97b..d9eff38fdf 100644
--- a/pod/perlrecharclass.pod
+++ b/pod/perlrecharclass.pod
@@ -74,14 +74,14 @@ character classes, see L<perlrebackslash>.)
 
 =head3 Digits
 
-C<\d> matches a single character that is considered to be a decimal I<digit>.
+C<\d> matches a single character considered to be a decimal I<digit>.
 What is considered a decimal digit depends on several factors, detailed
 below in L</Locale, EBCDIC, Unicode and UTF-8>.  If those factors
 indicate a Unicode interpretation, C<\d> not only matches the digits
-'0' - '9', but also Arabic, Devanagari and digits from other languages.
-Otherwise, if there is a locale in effect, it will match whatever
-characters the locale considers decimal digits.  Without a locale, C<\d>
-matches just the digits '0' to '9'.
+'0' - '9', but also Arabic, Devanagari, and digits from other languages.
+Otherwise, if a locale is in effect, it matches whatever characters that
+locale considers decimal digits.  Only when neither a Unicode interpretation
+nor locale prevails does C<\d> match only the digits '0' to '9' alone.
 
 Unicode digits may cause some confusion, and some security issues.  In UTF-8
 strings, unless the C<"a"> regular expression modifier is specified,
@@ -94,7 +94,7 @@ But Unicode also has a different property with a similar name,
 C<\p{Numeric_Type=Digit}>, which matches a completely different set of
 characters.  These characters are things such as subscripts.
 
-The design intent is for C<\d> to match all the digits (and no other characters)
+The design intent is for C<\d> to match all digits (and no other characters)
 that can be used with "normal" big-endian positional decimal syntax, whereby a
 sequence of such digits {N0, N1, N2, ...Nn} has the numeric value (...(N0 * 10
 + N1) * 10 + N2) * 10 ... + Nn).  In Unicode 5.2, the Tamil digits (U+0BE6 -
@@ -102,14 +102,14 @@ U+0BEF) can also legally be used in old-style Tamil numbers in which they would
 appear no more than one in a row, separated by characters that mean "times 10",
 "times 100", etc.  (See L<http://www.unicode.org/notes/tn21>.)
 
-Some of the non-European digits that C<\d> matches look like European ones, but
+Some non-European digits that C<\d> matches look like European ones, but
 have different values.  For example, BENGALI DIGIT FOUR (U+09EA) looks
 very much like an ASCII DIGIT EIGHT (U+0038).
 
 It may be useful for security purposes for an application to require that all
 digits in a row be from the same script.   See L<Unicode::UCD/charscript()>.
 
-Any character that isn't matched by C<\d> will be matched by C<\D>.
+Any character not matched by C<\d> is matched by C<\D>.
 
 =head3 Word characters
 
@@ -121,16 +121,16 @@ in the ASCII range it is the same as a string of Perl-identifier
 characters.  What is considered a
 word character depends on several factors, detailed below in L</Locale,
 EBCDIC, Unicode and UTF-8>.  If those factors indicate a Unicode
-interpretation, C<\w> matches the characters that are considered word
+interpretation, C<\w> matches the characters considered word
 characters in the Unicode database. That is, it not only matches ASCII letters,
 but also Thai letters, Greek letters, etc.  This includes connector
 punctuation (like the underscore) which connect two words together, or
-marks, such as a C<COMBINING TILDE>, which are generally used to add
-diacritical marks to letters.   If a Unicode interpretation
-is not indicated, C<\w> matches those characters that are considered
+diacritics, such as a C<COMBINING TILDE> and the modifier letters, which
+are generally used to add auxiliary markings to letters.   If a Unicode
+interpretation is not indicated, C<\w> matches those characters considered
 word characters by the current locale or EBCDIC code page.  Without a
-locale or EBCDIC code page, C<\w> matches the ASCII letters, digits and
-the underscore.
+locale or EBCDIC code page, C<\w> matches the underscore and ASCII letters 
+and digits. 
 
 There are a number of security issues with the full Unicode list of word
 characters.  See L<http://unicode.org/reports/tr36>.
@@ -140,36 +140,36 @@ language identifiers beyond the ASCII range, you may wish to instead use the
 more customized Unicode properties, "ID_Start", ID_Continue", "XID_Start", and
 "XID_Continue".  See L<http://unicode.org/reports/tr31>.
 
-Any character that isn't matched by C<\w> will be matched by C<\W>.
+Any character not matched by C<\w> is matched by C<\W>.
 
 =head3 Whitespace
 
-C<\s> matches any single character that is considered whitespace.  The exact
+C<\s> matches any single character considered whitespace.  The exact
 set of characters matched by C<\s> depends on several factors, detailed
 below in L</Locale, EBCDIC, Unicode and UTF-8>.  If those factors
 indicate a Unicode interpretation, C<\s> matches what is considered
 whitespace in the Unicode database; the complete list is in the table
-below. Otherwise, if there is a locale or EBCDIC code page in effect,
+below. Otherwise, if a locale or EBCDIC code page is in effect,
 C<\s> matches whatever is considered whitespace by the current locale or
 EBCDIC code page. Without a locale or EBCDIC code page, C<\s> matches
 the horizontal tab (C<\t>), the newline (C<\n>), the form feed (C<\f>),
 the carriage return (C<\r>), and the space.  (Note that it doesn't match
 the vertical tab, C<\cK>.)  Perhaps the most notable possible surprise
-is that C<\s> matches a non-breaking space only if a Unicode
+is that C<\s> matches a non-breaking space B<only> if a Unicode
 interpretation is indicated, or the locale or EBCDIC code page that is
-in effect has that character.
+in effect happens to have that character.
 
-Any character that isn't matched by C<\s> will be matched by C<\S>.
+Any character not matched by C<\s> is matched by C<\S>.
 
-C<\h> will match any character that is considered horizontal whitespace;
-this includes the space and the tab characters and a number other characters,
-all of which are listed in the table below.  C<\H> will match any character
-that is not considered horizontal whitespace.
+C<\h> matches any character considered horizontal whitespace;
+this includes the space and tab characters and several others 
+listed in the table below.  C<\H> matches any character
+not considered horizontal whitespace.
 
-C<\v> will match any character that is considered vertical whitespace;
-this includes the carriage return and line feed characters (newline) plus several
-other characters, all listed in the table below.
-C<\V> will match any character that is not considered vertical whitespace.
+C<\v> matches any character considered vertical whitespace;
+this includes the carriage return and line feed characters (newline) 
+plus several other characters, all listed in the table below.
+C<\V> matches any character not considered vertical whitespace.
 
 C<\R> matches anything that can be considered a newline under Unicode
 rules. It's not a character class, as it can match a multi-character
@@ -178,8 +178,8 @@ class; use C<\v> instead (vertical whitespace).
 Details are discussed in L<perlrebackslash>.
 
 Note that unlike C<\s>, C<\d> and C<\w>, C<\h> and C<\v> always match
-the same characters, without regard to other factors, such as if the
-source string is in UTF-8 format or not.
+the same characters, without regard to other factors, such as whether the
+source string is in UTF-8 format.
 
 One might think that C<\s> is equivalent to C<[\h\v]>. This is not true.  The
 vertical tab (C<"\x0b">) is not matched by C<\s>, it is however considered
@@ -187,9 +187,9 @@ vertical whitespace. Furthermore, if the source string is not in UTF-8 format,
 and any locale or EBCDIC code page that is in effect doesn't include them, the
 next line (ASCII-platform C<"\x85">) and the no-break space (ASCII-platform
 C<"\xA0">) characters are not matched by C<\s>, but are by C<\v> and C<\h>
-respectively.  If the C<"a"> modifier is not in effect, and the source
-string is in UTF-8 format, both the next line and
-the no-break space are matched by C<\s>.
+respectively.  If the C<"a"> modifier is not in effect and the source
+string is in UTF-8 format, both the next line and the no-break space 
+are matched by C<\s>.
 
 The following table is a complete listing of characters matched by
 C<\s>, C<\h> and C<\v> as of Unicode 5.2.
@@ -231,8 +231,8 @@ page is in effect that changes the C<\s> matching).
 =item [1]
 
 NEXT LINE and NO-BREAK SPACE only match C<\s> if the source string is in
-UTF-8 format and the C<"a"> modifier is not in effect; or the locale or
-EBCDIC code page that is in effect includes them.
+UTF-8 format and the C<"a"> modifier is not in effect, or if the locale 
+or EBCDIC code page in effect includes them.
 
 =back
 
@@ -242,7 +242,7 @@ use C<\d+>; to match a word, use C<\w+>.
 
 =head3 \N
 
-C<\N> is new in 5.12, and is experimental.  It, like the dot, will match any
+C<\N> is new in 5.12, and is experimental.  It, like the dot, matches any
 character that is not a newline. The difference is that C<\N> is not influenced
 by the I<single line> regular expression modifier (see L</The dot> above).  Note
 that the form C<\N{...}> may mean something completely different.  When the
@@ -252,7 +252,7 @@ non-newlines; C<\N{5,}> means to match 5 or more non-newlines.  But if C<{...}>
 is not a legal quantifier, it is presumed to be a named character.  See
 L<charnames> for those.  For example, none of C<\N{COLON}>, C<\N{4F}>, and
 C<\N{F4}> contain legal quantifiers, so Perl will try to find characters whose
-names are, respectively, C<COLON>, C<4F>, and C<F4>.
+names are respectively C<COLON>, C<4F>, and C<F4>.
 
 =head3 Unicode Properties
 
@@ -261,7 +261,7 @@ Unicode properties.  One letter property names can be used in the C<\pP> form,
 with the property name following the C<\p>, otherwise, braces are required.
 When using braces, there is a single form, which is just the property name
 enclosed in the braces, and a compound form which looks like C<\p{name=value}>,
-which means to match if the property "name" for the character has the particular
+which means to match if the property "name" for the character has that particular
 "value".
 For instance, a match for a number can be written as C</\pN/> or as
 C</\p{Number}/>, or as C</\p{Number=True}/>.
@@ -275,20 +275,21 @@ followed by a lowercase C<l>.
 
 Note that almost all properties are immune to case-insensitive matching.
 That is, adding a C</i> regular expression modifier does not change what
-they match.  There are two sets that are affected.  The first set is
+they match.  There are two sets affected.  The first set is
 C<Uppercase_Letter>,
 C<Lowercase_Letter>,
 and C<Titlecase_Letter>,
 all of which match C<Cased_Letter> under C</i> matching.
-And the second set is
+The second set is
 C<Uppercase>,
 C<Lowercase>,
 and C<Titlecase>,
 all of which match C<Cased> under C</i> matching.
 (The difference between these sets is that some things, such as Roman
-Numerals come in both upper and lower case so they are C<Cased>, but
-aren't considered to be letters, so they aren't C<Cased_Letter>s.)
-This set also includes its subsets C<PosixUpper> and C<PosixLower> both
+Numerals, come in both upper and lower case so they are C<Cased>, but
+aren't considered to be letters, so they aren't C<Cased_Letter>s. They're
+actually C<Letter_Number>s.) 
+This set also includes its subsets C<PosixUpper> and C<PosixLower>, both 
 of which under C</i> matching match C<PosixAlpha>.
 
 For more details on Unicode properties, see L<perlunicode/Unicode
@@ -329,10 +330,10 @@ The third form of character class you can use in Perl regular expressions
 is the bracketed character class.  In its simplest form, it lists the characters
 that may be matched, surrounded by square brackets, like this: C<[aeiou]>.
 This matches one of C<a>, C<e>, C<i>, C<o> or C<u>.  Like the other
-character classes, exactly one character will be matched. To match
+character classes, exactly one character is matched. To match
 a longer string consisting of characters mentioned in the character
 class, follow the character class with a L<quantifier|perlre/Quantifiers>.  For
-instance, C<[aeiou]+> matches a string of one or more lowercase English vowels.
+instance, C<[aeiou]+> matches one or more lowercase English vowels.
 
 Repeating a character in a character class has no
 effect; it's considered to be in the set only once.
@@ -393,6 +394,7 @@ A C<]> is normally either the end of a POSIX character class (see
 L</POSIX Character Classes> below), or it signals the end of the bracketed
 character class.  If you want to include a C<]> in the set of characters, you
 must generally escape it.
+
 However, if the C<]> is the I<first> (or the second if the first
 character is a caret) character of a bracketed character class, it
 does not denote the end of the class (as you cannot have an empty class)
@@ -413,26 +415,26 @@ Examples:
 =head3 Character Ranges
 
 It is not uncommon to want to match a range of characters. Luckily, instead
-of listing all the characters in the range, one may use the hyphen (C<->).
+of listing all characters in the range, one may use the hyphen (C<->).
 If inside a bracketed character class you have two characters separated
-by a hyphen, it's treated as if all the characters between the two are in
+by a hyphen, it's treated as if all characters between the two were in
 the class. For instance, C<[0-9]> matches any ASCII digit, and C<[a-m]>
-matches any lowercase letter from the first half of the ASCII alphabet.
+matches any lowercase letter from the first half of the old ASCII alphabet.
 
 Note that the two characters on either side of the hyphen are not
 necessarily both letters or both digits. Any character is possible,
 although not advisable.  C<['-?]> contains a range of characters, but
-most people will not know which characters that will be. Furthermore,
+most people will not know which characters that means.  Furthermore,
 such ranges may lead to portability problems if the code has to run on
 a platform that uses a different character set, such as EBCDIC.
 
 If a hyphen in a character class cannot syntactically be part of a range, for
 instance because it is the first or the last character of the character class,
-or if it immediately follows a range, the hyphen isn't special, and will be
-considered a character that is to be matched literally. You have to escape the
-hyphen with a backslash if you want to have a hyphen in your set of characters
-to be matched, and its position in the class is such that it could be
-considered part of a range.
+or if it immediately follows a range, the hyphen isn't special, and so is
+considered a character to be matched literally.  If you want a hyphen in
+your set of characters to be matched and its position in the class is such
+that it could be considered part of a range, you must escape that hyphen
+with a backslash.
 
 Examples:
 
@@ -450,13 +452,14 @@ Examples:
 
 It is also possible to instead list the characters you do not want to
 match. You can do so by using a caret (C<^>) as the first character in the
-character class. For instance, C<[^a-z]> matches a character that is not a
-lowercase ASCII letter.
+character class. For instance, C<[^a-z]> matches any character that is not a
+lowercase ASCII letter, which therefore includes almost a hundred thousand
+Unicode letters.
 
 This syntax make the caret a special character inside a bracketed character
 class, but only if it is the first character of the class. So if you want
-to have the caret as one of the characters you want to match, you either
-have to escape the caret, or not list it first.
+the caret as one of the characters to match, either escape the caret or 
+else not list it first.
 
 Examples:
 
@@ -469,8 +472,8 @@ Examples:
 
 You can put any backslash sequence character class (with the exception of
 C<\N> and C<\R>) inside a bracketed character class, and it will act just
-as if you put all the characters matched by the backslash sequence inside the
-character class. For instance, C<[a-f\d]> will match any decimal digit, or any
+as if you had put all characters matched by the backslash sequence inside the
+character class. For instance, C<[a-f\d]> matches any decimal digit, or any
 of the lowercase letters between 'a' and 'f' inclusive.
 
 C<\N> within a bracketed character class must be of the forms C<\N{I<name>}>
@@ -513,8 +516,8 @@ Be careful about the syntax,
 
 The latter pattern would be a character class consisting of a colon,
 and the letters C<a>, C<l>, C<p> and C<h>.
-POSIX character classes can be part of a larger bracketed character class.  For
-example,
+POSIX character classes can be part of a larger bracketed character class.  
+For example,
 
  [01[:alpha:]%]
 
@@ -523,7 +526,7 @@ is valid and matches '0', '1', any alphabetic character, and the percent sign.
 Perl recognizes the following POSIX character classes:
 
  alpha  Any alphabetical character ("[A-Za-z]").
- alnum  Any alphanumerical character. ("[A-Za-z0-9]")
+ alnum  Any alphanumeric character. ("[A-Za-z0-9]")
  ascii  Any character in the ASCII character set.
  blank  A GNU extension, equal to a space or a horizontal tab ("\t").
  cntrl  Any control character.  See Note [2] below.
@@ -543,22 +546,22 @@ derived from official Unicode properties.)  The table below shows the relation
 between POSIX character classes and these counterparts.
 
 One counterpart, in the column labelled "ASCII-range Unicode" in
-the table, will only match characters in the ASCII character set.
+the table, matches only characters in the ASCII character set.
 
 The other counterpart, in the column labelled "Full-range Unicode", matches any
 appropriate characters in the full Unicode character set.  For example,
-C<\p{Alpha}> will match not just the ASCII alphabetic characters, but any
-character in the entire Unicode character set that is considered to be
-alphabetic.  The column labelled "backslash sequence" is a (short) synonym for
+C<\p{Alpha}> matches not just the ASCII alphabetic characters, but any
+character in the entire Unicode character set considered alphabetic.  
+The column labelled "backslash sequence" is a (short) synonym for
 the Full-range Unicode form.
 
 (Each of the counterparts has various synonyms as well.
-L<perluniprops/Properties accessible through \p{} and \P{}> lists all the
-synonyms, plus all the characters matched by each of the ASCII-range
-properties.  For example C<\p{AHex}> is a synonym for C<\p{ASCII_Hex_Digit}>,
+L<perluniprops/Properties accessible through \p{} and \P{}> lists all
+synonyms, plus all characters matched by each ASCII-range property.  
+For example, C<\p{AHex}> is a synonym for C<\p{ASCII_Hex_Digit}>,
 and any C<\p> property name can be prefixed with "Is" such as C<\p{IsAlpha}>.)
 
-Both the C<\p> forms are unaffected by any locale that is in effect, or whether
+Both the C<\p> forms are unaffected by any locale in effect, or whether
 the string is in UTF-8 format or not, or whether the platform is EBCDIC or not.
 In contrast, the POSIX character classes are affected, unless the
 regular expression is compiled with the C<"a"> modifier.  If the C<"a">
@@ -607,7 +610,7 @@ C<\p{Blank}> and C<\p{HorizSpace}> are synonyms.
 =item [2]
 
 Control characters don't produce output as such, but instead usually control
-the terminal somehow: for example newline and backspace are control characters.
+the terminal somehow: for example, newline and backspace are control characters.
 In the ASCII range, characters whose ordinals are between 0 and 31 inclusive,
 plus 127 (C<DEL>) are control characters.
 
@@ -618,16 +621,16 @@ that in Unicode have ordinals from 128 through 159.
 =item [3]
 
 Any character that is I<graphical>, that is, visible. This class consists
-of all the alphanumerical characters and all punctuation characters.
+of all alphanumeric characters and all punctuation characters.
 
 =item [4]
 
-All printable characters, which is the set of all the graphical characters
-plus whitespace characters that are not also controls.
+All printable characters, which is the set of all graphical characters
+plus those whitespace characters which are not also controls.
 
 =item [5]
 
-C<\p{PosixPunct}> and C<[[:punct:]]> in the ASCII range match all the
+C<\p{PosixPunct}> and C<[[:punct:]]> in the ASCII range match all
 non-controls, non-alphanumeric, non-space characters:
 C<[-!"#$%&'()*+,./:;<=E<gt>?@[\\\]^_`{|}~]> (although if a locale is in effect,
 it could alter the behavior of C<[[:punct:]]>).
@@ -642,9 +645,9 @@ C<\p{XPosixPunct}> and (in Unicode mode) C<[[:punct:]]>, match what
 C<\p{PosixPunct}> matches in the ASCII range, plus what C<\p{Punct}>
 matches.  This is different than strictly matching according to
 C<\p{Punct}>.  Another way to say it is that
-for a UTF-8 string, C<[[:punct:]]> matches all the characters that Unicode
-considers to be punctuation, plus all the ASCII-range characters that Unicode
-considers to be symbols.
+for a UTF-8 string, C<[[:punct:]]> matches all characters that Unicode
+considers punctuation, plus all ASCII-range characters that Unicode
+considers symbols.
 
 =item [6]
 
@@ -654,7 +657,7 @@ matches the vertical tab, C<\cK>.   Same for the two ASCII-only range forms.
 =back
 
 There are various other synonyms that can be used for these besides
-C<\p{HorizSpace}> and \C<\p{XPosixBlank}>.  For example
+C<\p{HorizSpace}> and \C<\p{XPosixBlank}>.  For example,
 C<\p{PosixAlpha}> can be written as C<\p{Alpha}>.  All are listed
 in L<perluniprops/Properties accessible through \p{} and \P{}>.
 
@@ -679,10 +682,9 @@ below.
 
 =head4 [= =] and [. .]
 
-Perl will recognize the POSIX character classes C<[=class=]>, and
-C<[.class.]>, but does not (yet?) support them.  Use of
-such a construct will lead to an error.
-
+Perl recognizes the POSIX character classes C<[=class=]> and
+C<[.class.]>, but does not (yet?) support them.  Any attempt to use 
+either construct raises an exception.
 
 =head4 Examples
 
@@ -703,9 +705,9 @@ such a construct will lead to an error.
 =head2 Locale, EBCDIC, Unicode and UTF-8
 
 Some of the character classes have a somewhat different behaviour
-depending on the internal encoding of the source string, if the regular
-expression is marked as having Unicode semantics, the locale that is in
-effect, and if the program is running on an EBCDIC platform.
+depending on the internal encoding of the source string, whether the regular
+expression is marked as having Unicode semantics, whatever locale is in
+effect, and whether the program is running on an EBCDIC platform.
 
 C<\w>, C<\d>, C<\s> and the POSIX character classes (and their
 negations, including C<\W>, C<\D>, C<\S>) have this behaviour.  (Since
@@ -744,11 +746,12 @@ L<perlunicode/The "Unicode Bug">.
 For portability reasons, unless the C<"a"> modifier is specified,
 it may be better to not use C<\w>, C<\d>, C<\s> or the POSIX character
 classes and use the Unicode properties instead.
-That way you can control whether you want matching of just characters in
-the ASCII character set, or any Unicode characters.
-C<S<use feature "unicode_strings">> will allow seamless Unicode behavior
-no matter what the internal encodings are, but won't allow restricting
-to just the ASCII characters.
+
+That way you can control whether you want matching of characters in
+the ASCII character set alone, or whether to match Unicode characters.
+C<S<use feature "unicode_strings">> allows seamless Unicode behavior
+no matter the internal encodings, but won't allow restricting
+to ASCII characters only.
 
 =head4 Examples