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

README.netware

@@ -118,8 +118,8 @@ I<sys:\perl\system> folder.  Copy this to I<sys:\system> folder.
 
 Example: At the command prompt Type "nmake nwinstall".
           This will install NetWare Perl on the NetWare Server.
-          Similiarly if you type "nmake install",
-          This will cause the binaries to be installed on the local machine.
+          Similarly, if you type "nmake install",
+          this will cause the binaries to be installed on the local machine.
           (Typically under the c:\perl folder)
 
 =head1 BUILD NEW EXTENSIONS

mg.c

@@ -1746,7 +1746,7 @@ Perl_magic_setnkeys(pTHX_ SV *sv, MAGIC *mg)
 
 Invoke a magic method (like FETCH).
 
-* sv and mg are the tied thinggy and the tie magic;
+* sv and mg are the tied thingy and the tie magic;
 * meth is the name of the method to call;
 * argc is the number of args (in addition to $self) to pass to the method;
        the args themselves are any values following the argc argument.

pod/perl.pod

@@ -273,7 +273,7 @@ Perl was originally a language optimized for scanning arbitrary
 text files, extracting information from those text files, and printing
 reports based on that information.  It quickly became a good language
 for many system management tasks. Over the years, Perl has grown into
-a general-purpose progammming language. It's widely used for everything
+a general-purpose programming language. It's widely used for everything
 from quick "one-liners" to full-scale application development.
 
 The language is intended to be practical (easy to use, efficient,

pod/perl5120delta.pod

@@ -1515,7 +1515,7 @@ The documentation for C<$1> in perlvar.pod has been clarified.
 
 =item *
 
-C<\N{U+I<wide hex char>}> is now documented.
+C<\N{U+I<code point>}> is now documented.
 
 =back
 
@@ -1666,7 +1666,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
+or regex containing C<\N{I<name>}> or C<\N{U+I<code point>}> in its
 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.)

pod/perl5139delta.pod

@@ -486,7 +486,7 @@ structures have been removed.  These are: C<Rxf_Pmf_LOCALE>,
 C<Rxf_Pmf_UNICODE>, and C<PMf_LOCALE>.  Instead there are encodes and
 three static in-line functions for accessing the information:
 C<get_regex_charset()>, C<set_regex_charset()>, and C<get_regex_charset_name()>,
-which are defined in the places where the orginal flags were.
+which are defined in the places where the original flags were.
 
 =item *
 

pod/perl592delta.pod

@@ -242,7 +242,7 @@ C<map> in scalar context is now optimized.
 =item *
 
 The regexp engine now implements the trie optimization : it's able to
-factorize common prefixes and suffixes in regular expressions. A new
+factor out common prefixes and suffixes in regular expressions. A new
 special variable, ${^RE_TRIE_MAXBUF}, has been added to fine-tune this
 optimization.
 

pod/perldelta.pod

@@ -30,7 +30,7 @@ here, but most should go in the L</Performance Enhancements> section.
 
 =head2 Add C<\p{Titlecase}> as a synonym for C<\p{Title}>
 
-This synyom is added for symmetry with the Unicode property names
+This synonym is added for symmetry with the Unicode property names
 C<\p{Uppercase}> and C<\p{Lowercase}>.
 
 =head2 New regular expression modifier option C</aa>

pod/perlfunc.pod

@@ -1680,7 +1680,8 @@ normally you I<would> like to use double quotes, except that in this
 particular situation, you can just use symbolic references instead, as
 in case 6.
 
-Before Perl 5.14, the assignment to C<$@> occured before restoration of localised variables, which means that, if your code is to run on older
+Before Perl 5.14, the assignment to C<$@> occurred before restoration 
+of localised variables, which means that for your code to run on older
 versions, a temporary is required if you want to mask some but not all
 errors:
 

pod/perlhack.pod

@@ -44,7 +44,7 @@ Keep hacking until the tests pass.
 
 =item * Commit your change
 
-Commiting your work will save the change I<on your local system>:
+Committing your work will save the change I<on your local system>:
 
   % git commit -a -m 'Commit message goes here'
 

pod/perlop.pod

@@ -1197,7 +1197,7 @@ X<\l> X<\u> X<\L> X<\U> X<\E> X<\Q>
 
 If C<use locale> is in effect, the case map used by C<\l>, C<\L>,
 C<\u> and C<\U> is taken from the current locale.  See L<perllocale>.
-If Unicode (for example, C<\N{}> or wide hex characters of 0x100 or
+If Unicode (for example, C<\N{}> or code points of 0x100 or
 beyond) is being used, the case map used by C<\l>, C<\L>, C<\u> and
 C<\U> is as defined by Unicode.
 
@@ -2143,12 +2143,12 @@ C<tr///>), the search is repeated once more.
 If the first delimiter is not an opening punctuation, three delimiters must
 be same such as C<s!!!> and C<tr)))>, in which case the second delimiter
 terminates the left part and starts the right part at once.
-If the left part is delimited by bracketing punctuations (that is C<()>,
+If the left part is delimited by bracketing punctuation (that is C<()>,
 C<[]>, C<{}>, or C<< <> >>), the right part needs another pair of
-delimiters such as C<s(){}> and C<tr[]//>.  In these cases, whitespaces
+delimiters such as C<s(){}> and C<tr[]//>.  In these cases, whitespace
 and comments are allowed between both parts, though the comment must follow
-at least one whitespace; otherwise a character expected as the start of
-the comment may be regarded as the starting delimiter of the right part.
+at least one whitespace character; otherwise a character expected as the 
+start of the comment may be regarded as the starting delimiter of the right part.
 
 During this search no attention is paid to the semantics of the construct.
 Thus:

pod/perlpolicy.pod

@@ -133,7 +133,7 @@ bug as a feature, we need to treat it as such.
 
 New syntax and semantics which don't break existing language constructs
 and syntax have a much lower bar.  They merely need to prove themselves
-to be useful, elegant, well designed and well tested.
+to be useful, elegant, well designed, and well tested.
 
 =head2 Terminology
 
@@ -198,9 +198,9 @@ acceptable.
 
 =item *
 
-Documentation updates that correct factual errors, explain significant
-bugs or deficiences in the current implementation or fix broken markup
-are acceptable.
+Acceptable documentation updates are those that correct factual errors,
+explain significant bugs or deficiencies in the current implementation, 
+or fix broken markup.
 
 =item *