[PATCH] Doc spellcheck + podcheck

From: Autrijus Tang <autrijus@egb.elixus.org>
Date: Thu, 15 Nov 2001 22:49:05 -0800
Message-Id: <20011116064905.GA44092@egb.elixus.org>

Subject: [PATCH] podcheck+spellcheck, the rest of the story
From: Autrijus Tang <autrijus@egb.elixus.org>
Date: Fri, 16 Nov 2001 00:42:20 -0800
Message-Id: <20011116084220.GA44295@egb.elixus.org>

Subject: Re: [PATCH] podcheck+spellcheck, the rest of the story
From: Nicholas Clark <nick@ccl4.org>
Date: Fri, 16 Nov 2001 10:32:01 +0000
Message-Id: <20011116103200.F62891@plum.flirble.org>
(Applied after suitable de-mangling.)

p4raw-id: //depot/perl@13041

18 files changed, 170 insertions, 160 deletions

diff --git a/pod/perl571delta.pod b/pod/perl571delta.pod
index df132ccf77..80478716ec 100644
--- a/pod/perl571delta.pod
+++ b/pod/perl571delta.pod
@@ -420,7 +420,7 @@ parsing algorithms.  See L<Text::Balanced> for more information.
 =item *
 
 Tie::RefHash::Nestable, by Edward Avis, allows storing hash references
-(unlike the standard Tie::Refhash)  The module is contained within
+(unlike the standard Tie::RefHash)  The module is contained within
 Tie::RefHash.
 
 =item *
diff --git a/pod/perl572delta.pod b/pod/perl572delta.pod
index bfe44c46e9..1e7251e33d 100644
--- a/pod/perl572delta.pod
+++ b/pod/perl572delta.pod
@@ -599,7 +599,7 @@ Don't panic.  Read INSTALL 'make test' section instead.
 
 The subtests 11 and 12 sometimes fail and sometimes work.
 
-=head2 HP-UX lib/io_multihomed Fails When LP64-Configur
+=head2 HP-UX lib/io_multihomed Fails When LP64-Configured
 
 The lib/io_multihomed test may hang in HP-UX if Perl has been
 configured to be 64-bit. Because other 64-bit platforms do not hang in
@@ -726,7 +726,7 @@ Compaq C V6.2-008 on OpenVMS Alpha V7.1
   [.lib]vmsish............................FAILED on test 13
   Failed 4/399 tests, 92.48% okay.
 
-Compac C V6.4-005 on OpenVMS Alpha 7.2.1
+Compaq C V6.4-005 on OpenVMS Alpha 7.2.1
 
   [-.ext.b]showlex........................FAILED on test 1
   [-.ext.list.util.t]tainted..............FAILED on test 3
diff --git a/pod/perlapi.pod b/pod/perlapi.pod
index ef4ab300ce..dba60c4f66 100644
--- a/pod/perlapi.pod
+++ b/pod/perlapi.pod
@@ -2041,7 +2041,6 @@ Found in file sharedsv.c
 
 =item sortsv
 
-   
 Sort an array. Here is an example:
 
     sortsv(AvARRAY(av), av_len(av)+1, Perl_sv_cmp_locale); 
diff --git a/pod/perlapio.pod b/pod/perlapio.pod
index ad80a6c2e5..d378e6e12e 100644
--- a/pod/perlapio.pod
+++ b/pod/perlapio.pod
@@ -104,7 +104,7 @@ above abstraction which allows perl more control over how IO is done
 as it decouples IO from the way the operating system and C library
 choose to do things. For USE_PERLIO PerlIO * has an extra layer of
 indirection - it is a pointer-to-a-pointer.  This allows the PerlIO *
-to remain with a known value while swapping the implementation arround
+to remain with a known value while swapping the implementation around
 underneath I<at run time>. In this case all the above are true (but
 very simple) functions which call the underlying implementation.
 
@@ -138,7 +138,7 @@ These correspond to fopen()/fdopen() and the arguments are the same.
 Return C<NULL> and set C<errno> if there is an error.  There may be an
 implementation limit on the number of open handles, which may be lower
 than the limit on the number of open files - C<errno> may not be set
-when C<NULL> is returned if this limnit is exceeded.
+when C<NULL> is returned if this limit is exceeded.
 
 =item B<PerlIO_reopen(path,mode,f)>
 
@@ -289,7 +289,7 @@ problem. However in other cases then mechanisms must exist to create a
 FILE * which can be passed to library code which is going to use stdio
 calls.
 
-The fisrt step is to add this line:
+The first step is to add this line:
 
    #define PERLIO_NOT_STDIO 0
 
@@ -432,7 +432,7 @@ case.
 =item PerlIO_binmode(f,ptype,imode,layers)
 
 The hook used by perl's C<binmode> operator.
-B<ptype> is perl's charcter for the kind of IO:
+B<ptype> is perl's character for the kind of IO:
 
 =over 8
 
diff --git a/pod/perldata.pod b/pod/perldata.pod
index 3e2482e784..f2484dbc7e 100644
--- a/pod/perldata.pod
+++ b/pod/perldata.pod
@@ -219,7 +219,7 @@ an array that was previously shortened does not recover values
 that were in those elements.  (It used to do so in Perl 4, but we
 had to break this to make sure destructors were called when expected.)
 
-You can also gain some miniscule measure of efficiency by pre-extending
+You can also gain some minuscule measure of efficiency by pre-extending
 an array that is going to get big.  You can also extend an array
 by assigning to an element that is off the end of the array.  You
 can truncate an array down to nothing by assigning the null list
@@ -416,8 +416,8 @@ plain paranoid, you can force the correct interpretation with curly
 braces as above.
 
 If you're looking for the information on how to use here-documents,
-which used to be here, that's been moved to L<perlop> in the section on
-L<Quote and Quote-like Operators>.
+which used to be here, that's been moved to
+L<perlop/Quote and Quote-like Operators>.
 
 =head2 List value constructors
 
diff --git a/pod/perlebcdic.pod b/pod/perlebcdic.pod
index c98b46c6e7..86dcba29a5 100644
--- a/pod/perlebcdic.pod
+++ b/pod/perlebcdic.pod
@@ -1054,7 +1054,7 @@ following will print "Yes indeed\n" on either an ASCII or EBCDIC computer:
     $all_byte_chrs = '';
     for (0..255) { $all_byte_chrs .= chr($_); }
     $uuencode_byte_chrs = pack('u', $all_byte_chrs);
-    ($uu = <<'    ENDOFHEREDOC') =~ s/^\s*//gm;
+    ($uu = <<'ENDOFHEREDOC') =~ s/^\s*//gm;
     M``$"`P0%!@<("0H+#`T.#Q`1$A,4%187&!D:&QP='A\@(2(C)"4F)R@I*BLL
     M+2XO,#$R,S0U-C<X.3H[/#T^/T!!0D-$149'2$E*2TQ-3D]045)35%565UA9
     M6EM<75Y?8&%B8V1E9F=H:6IK;&UN;W!Q<G-T=79W>'EZ>WQ]?G^`@8*#A(6&
diff --git a/pod/perlfaq4.pod b/pod/perlfaq4.pod
index f602d24b27..0196407871 100644
--- a/pod/perlfaq4.pod
+++ b/pod/perlfaq4.pod
@@ -136,13 +136,15 @@ functions is that it works with numbers of ANY size, that it is
 optimized for speed on some operations, and for at least some
 programmers the notation might be familiar.
 
+=over 4
+
 =item B<How do I convert Hexadecimal into decimal:>
 
 Using perl's built in conversion of 0x notation:
 
     $int = 0xDEADBEEF;
     $dec = sprintf("%d", $int);
- 
+
 Using the hex function:
 
     $int = hex("DEADBEEF");
@@ -247,6 +249,7 @@ Using Bit::Vector:
 The remaining transformations (e.g. hex -> oct, bin -> hex, etc.)
 are left as an exercise to the inclined reader.
 
+=back
 
 =head2 Why doesn't & work the way I want it to?
 
@@ -1849,7 +1852,7 @@ in L<perltoot>.
 
 =head2 How can I use a reference as a hash key?
 
-You can't do this directly, but you could use the standard Tie::Refhash
+You can't do this directly, but you could use the standard Tie::RefHash
 module distributed with Perl.
 
 =head1 Data: Misc
diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index 74778acd21..679fe3734f 100644
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -1201,7 +1201,7 @@ C code have superseded it.
 If you're looking to use L<dump> to speed up your program, consider
 generating bytecode or native C code as described in L<perlcc>.  If
 you're just trying to accelerate a CGI script, consider using the
-C<mod_perl> extension to B<Apache>, or the CPAN module, Fast::CGI.
+C<mod_perl> extension to B<Apache>, or the CPAN module, CGI::Fast.
 You might also consider autoloading or selfloading, which at least
 make your program I<appear> to run faster.
 
diff --git a/pod/perlguts.pod b/pod/perlguts.pod
index 148ae9600c..8a1d511cde 100644
--- a/pod/perlguts.pod
+++ b/pod/perlguts.pod
@@ -1695,7 +1695,7 @@ C<sv_dump> to produce debugging output from Perl-space, so users of that
 module should already be familiar with its format.
 
 C<Perl_op_dump> can be used to dump an C<OP> structure or any of its
-derivatives, and produces output similiar to C<perl -Dx>; in fact,
+derivatives, and produces output similar to C<perl -Dx>; in fact,
 C<Perl_dump_eval> will dump the main root of the code being evaluated,
 exactly like C<-Dx>.
 
diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index 66a8ea0db6..49d7625ab0 100644
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -1638,7 +1638,7 @@ extremely important to test any addition thoroughly and add new tests
 to explore all boundary conditions that your new function is expected
 to handle.  If your new function is used only by one module (e.g. toke),
 then it should probably be named S_your_function (for static); on the
-other hand, if you expect it to accessable from other functions in
+other hand, if you expect it to accessible from other functions in
 Perl, you should name it Perl_your_function.  See L<perlguts/Internal Functions>
 for more details.
 
@@ -1679,7 +1679,7 @@ Lastly, TEST TEST TEST TEST TEST any code before posting to p5p.
 Test on as many platforms as you can find.  Test as many perl
 Configure options as you can (e.g. MULTIPLICITY).  If you have
 profiling or memory tools, see L<EXTERNAL TOOLS FOR DEBUGGING PERL>
-below for how to use them to futher test your code.  Remember that
+below for how to use them to further test your code.  Remember that
 most of the people on P5P are doing this on their own time and
 don't have the time to debug your code.
 
diff --git a/pod/perliol.pod b/pod/perliol.pod
index a31ffd1847..e51f309106 100644
--- a/pod/perliol.pod
+++ b/pod/perliol.pod
@@ -69,9 +69,13 @@ A "layer" is composed of two parts:
 
 =over 4
 
-=item 1. The functions and attributes of the "layer class".
+=item 1.
+
+The functions and attributes of the "layer class".
+
+=item 2.
 
-=item 2. The per-instance data for a particular handle.
+The per-instance data for a particular handle.
 
 =back
 
diff --git a/pod/perlpod.pod b/pod/perlpod.pod
index 91cc81ac84..80c9ba134a 100644
--- a/pod/perlpod.pod
+++ b/pod/perlpod.pod
@@ -173,21 +173,21 @@ usually used just when you want to start a Pod block with an ordinary
 paragraph or a verbatim paragraph.  For example:
 
   =item stuff()
-  
+
   This function does stuff.
-  
+
   =cut
-  
+
   sub stuff {
     ...
   }
-  
+
   =pod
-  
+
   Remember to check its return value, as in:
-  
-    stuff() || die "Couldn't do stufF!";
-  
+
+    stuff() || die "Couldn't do stuff!";
+
   =cut
 
 =item C<=begin I<formatname>>
@@ -208,10 +208,10 @@ is meant for formatters that understand the special format
 called I<formatname>.  For example,
 
   =begin html
-  
+
   <hr> <img src="thang.png">
   <p> This is a raw HTML paragraph </p>
-  
+
   =end html
 
 The command "=for I<formatname> I<text...>"
@@ -613,7 +613,7 @@ wish to work around.
 =item *
 
 If you're more familiar with writing in HTML than with writing in Pod, you
-can try your hand at writing documentation in simple HTML, and coverting
+can try your hand at writing documentation in simple HTML, and converting
 it to Pod with the experimental L<Pod::HTML2Pod|Pod::HTML2Pod> module,
 (available in CPAN), and looking at the resulting code.  The experimental
 L<Pod::PXML|Pod::PXML> module in CPAN might also be useful.
@@ -626,7 +626,7 @@ line.  Having something like this:
 
  # - - - - - - - - - - - -
  =item $firecracker->boom()
- 
+
  This noisily detonates the firecracker object.
  =cut
  sub boom {
@@ -638,13 +638,13 @@ at all.
 Instead, have it like this:
 
  # - - - - - - - - - - - -
- 
+
  =item $firecracker->boom()
- 
+
  This noisily detonates the firecracker object.
- 
+
  =cut
- 
+
  sub boom {
  ...
 
diff --git a/pod/perlpodspec.pod b/pod/perlpodspec.pod
index 46d3ec8707..145309c58f 100644
--- a/pod/perlpodspec.pod
+++ b/pod/perlpodspec.pod
@@ -121,7 +121,7 @@ But they may span several (non-blank) lines:
   =for comment
   Hm, I wonder what it would look like if
   you tried to write a BNF for Pod from this.
-  
+
   =head3 Dr. Strangelove, or: How I Learned to
   Stop Worrying and Love the Bomb
 
@@ -176,11 +176,11 @@ For example: consider the following paragraphs:
   # <- that's the 0th column
 
   =head1 Foo
-  
+
   Stuff
-  
+
     $foo->bar
-  
+
   =cut
 
 Here, "=head1 Foo" and "=cut" are command paragraphs because the first
@@ -208,7 +208,7 @@ This command indicates that the text in the remainder of the paragraph
 is a heading.  That text may contain formatting codes.  Examples:
 
   =head1 Object Attributes
-  
+
   =head3 What B<Not> to Do!
 
 =item "=pod"
@@ -219,9 +219,9 @@ all.)  If there is any text in this command paragraph after "=pod",
 it must be ignored.  Examples:
 
   =pod
-  
+
   This is a plain Pod paragraph.
-  
+
   =pod This text is ignored.
 
 =item "=cut"
@@ -251,9 +251,9 @@ explained in the L</"About =over...=back Regions"> section, further
 below.  Formatting codes are not expanded.  Examples:
 
   =over 3
-  
+
   =over 3.5
-  
+
   =over
 
 =item "=item"
@@ -265,20 +265,20 @@ explained in the L</"About =over...=back Regions"> section, further
 below.  Examples:
 
   =item
-  
+
   =item *
-  
+
   =item      *    
-  
+
   =item 14
-  
+
   =item   3.
-  
+
   =item C<< $thing->stuff(I<dodad>) >>
-  
+
   =item For transporting us beyond seas to be tried for pretended
   offenses
-  
+
   =item He is at this time transporting large armies of foreign
   mercenaries to complete the works of death, desolation and
   tyranny, already begun with circumstances of cruelty and perfidy
@@ -320,9 +320,9 @@ L</About Data Paragraphs and "=beginE<sol>=end" Regions>.
 This is synonymous with:
 
      =begin formatname
-     
+
      text...
-     
+
      =end formatname
 
 That is, it creates a region consisting of a single paragraph; that
@@ -517,7 +517,7 @@ starting at line 123: 'Time objects are not...'").  So these
 two paragraphs:
 
   I<I told you not to do this!
-  
+
   Don't make me say it again!>
 
 ...must I<not> be parsed as two paragraphs in italics (with the I
@@ -526,7 +526,7 @@ the first paragraph should generate a warning, but that aside, the
 above code must parse as if it were:
 
   I<I told you not to do this!>
-  
+
   Don't make me say it again!E<gt>
 
 (In SGMLish jargon, all Pod commands are like block-level
@@ -645,11 +645,11 @@ version numbers of any modules it might be using to process the Pod.
 Minimal examples:
 
   %% POD::Pod2PS v3.14159, using POD::Parser v1.92
-  
+
   <!-- Pod::HTML v3.14159, using POD::Parser v1.92 -->
-  
+
   {\doccomm generated by Pod::Tree::RTF 3.14159 using Pod::Tree 1.08}
-  
+
   .\" Pod::Man version 3.14159, using POD::Parser version 1.92
 
 Formatters may also insert additional comments, including: the
@@ -802,7 +802,7 @@ characters (also defined there by Unicode, with the same meaning),
 which all Pod formatters must render faithfully.  Characters
 in the ranges 0-31 and 127-159 should not be used (neither as
 literals, nor as EE<lt>number> codes), except for the
-literal byte-sequences for newline (13, 13 10, or 13), and tab (9).
+literal byte-sequences for newline (13, 13 10, or 10), and tab (9).
 
 Characters in the range 160-255 refer to Latin-1 characters (also
 defined there by Unicode, with the same meaning).  Characters above
@@ -861,7 +861,7 @@ it contains spaces, which aren't alphanumeric characters.  This
 presumably does not I<need> special treatment by a Pod processor;
 " 0 1 2 3 " doesn't look like a number in any base, so it would
 presumably be looked up in the table of HTML-like names.  Since
-there is (and cannot be) an HTML-like entity called " 0 1 2 3 ",
+there isn't (and cannot be) an HTML-like entity called " 0 1 2 3 ",
 this will be treated as an error.  However, Pod processors may
 treat "EE<lt> 0 1 2 3 >" or "EE<lt>e-acute>" as I<syntactically>
 invalid, potentially earning a different error message than the
@@ -942,7 +942,7 @@ unknown EE<lt>thing> sequence that the parser couldn't resolve to
 anything, renderable or not).  It is good practice to map Latin letters
 with diacritics (like "EE<lt>eacute>"/"EE<lt>233>") to the corresponding
 unaccented US-ASCII letters (like a simple character 101, "e"), but
-clearly this is often not feasable, and an unrenderable character may
+clearly this is often not feasible, and an unrenderable character may
 be represented as "?", or the like.  In attempting a sane fallback
 (as from EE<lt>233> to "e"), Pod formatters may use the
 %Latin1Code_to_fallback table in L<Pod::Escapes|Pod::Escapes>, or
@@ -987,7 +987,7 @@ representation that maps best to what the output format demands.
 
 =item *
 
-Some processors may find it the C<SE<lt>...E<gt>> code easiest to
+Some processors may find that the C<SE<lt>...E<gt>> code is easiest to
 implement by replacing each space in the parse tree under the content
 of the S, with an NBSP.  But note: the replacement should apply I<not> to
 spaces in I<all> text, but I<only> to spaces in I<printable> text.  (This
@@ -1018,7 +1018,7 @@ character/code and no code for "don't break this stuff across lines".
 
 Besides the NBSP character discussed above, implementors are reminded
 of the existence of the other "special" character in Latin-1, the
-"soft hyphen" chararacter, also known as "discretionary hyphen",
+"soft hyphen" character, also known as "discretionary hyphen",
 i.e. C<EE<lt>173E<gt>> = C<EE<lt>0xADE<gt>> =
 C<EE<lt>shyE<gt>>).  This character expresses an optional hyphenation
 point.  That is, it normally renders as nothing, but may render as a
@@ -1225,9 +1225,9 @@ as in:
 
   <h1><a name="About_the_-M_Operator">About the <code>-M</code>
   Operator</h1>
-  
+
   ...
-  
+
   <a href="somedoc#About_the_-M_Operator">About the <code>-M</code>
   Operator" in somedoc</a>
 
@@ -1434,17 +1434,17 @@ Pod processors should tolerate "=item *" / "=item I<number>" commands
 with no accompanying paragraph.  The middle item is an example:
 
   =over
-  
+
   =item 1
-  
+
   Pick up dry cleaning.
-  
+
   =item 2
-  
+
   =item 3
-  
+
   Stop by the store.  Get Abba Zabas, Stoli, and cheap lawn chairs.
-  
+
   =back
 
 =item *
@@ -1458,7 +1458,7 @@ Note that an "=over" ... "=back" region should have some
 content.  That is, authors should not have an empty region like this:
 
   =over
-  
+
   =back
 
 Pod processors seeing such a contentless "=over" ... "=back" region,
@@ -1479,7 +1479,7 @@ Authors of Pod formatters should note that this construct:
   =item Porro
 
   =item Quisquam Est
-  
+
   Qui dolorem ipsum quia dolor sit amet, consectetur, adipisci 
   velit, sed quia non numquam eius modi tempora incidunt ut
   labore et dolore magnam aliquam quaerat voluptatem.
@@ -1494,9 +1494,9 @@ paragraph "Qui dolorem ipsum quia dolor..."; and then an item
 "Ut Enim".  In that case, you'd want to format it like so:
 
   Neque
-  
+
   Porro
-  
+
   Quisquam Est
     Qui dolorem ipsum quia dolor sit amet, consectetur, adipisci
     velit, sed quia non numquam eius modi tempora incidunt ut
@@ -1534,7 +1534,7 @@ authors to distinguish which grouping is meant by the above
 
   Ut Enim
 
-That is, there should be (at least roughtly) equal spacing between
+That is, there should be (at least roughly) equal spacing between
 items as between paragraphs (although that spacing may well be less
 than the full height of a line of text).  This leaves it to the reader
 to use (con)textual cues to figure out whether the "Qui dolorem
@@ -1554,9 +1554,9 @@ to be used (typically passed through) when rendering the document to
 a specific format:
 
   =begin rtf
-  
+
   \par{\pard\qr\sa4500{\i Printed\~\chdate\~\chtime}\par}
-  
+
   =end rtf
 
 The exact same effect could, incidentally, be achieved with a single
@@ -1570,11 +1570,11 @@ meaning as one, and Pod parsers may parse it as one.)
 Another example of a data paragraph:
 
   =begin html
-  
+
   I like <em>PIE</em>!
-  
+
   <hr>Especially pecan pie!
-  
+
   =end html
 
 If these were ordinary paragraphs, the Pod parser would try to
@@ -1620,26 +1620,26 @@ Note that a "=begin I<identifier>"..."=end I<identifier>" region where
 I<identifier> begins with a colon, I<can> contain commands.  For example:
 
   =begin :biblio
-  
+
   Wirth's classic is available in several editions, including:
-  
+
   =for comment
    hm, check abebooks.com for how much used copies cost.
-  
+
   =over
-  
+
   =item
-  
+
   Wirth, Niklaus.  1975.  I<Algorithmen und Datenstrukturen.>
   Teubner, Stuttgart.  [Yes, it's in German.]
-  
+
   =item
-  
+
   Wirth, Niklaus.  1976.  I<Algorithms + Data Structures =
   Programs.>  Prentice-Hall, Englewood Cliffs, NJ.
-  
+
   =back
-  
+
   =end :biblio
 
 Note, however, a "=begin I<identifier>"..."=end I<identifier>"
@@ -1648,13 +1648,13 @@ directly contain "=head1" ... "=head4" commands, nor "=over", nor "=back",
 nor "=item".  For example, this may be considered invalid:
 
   =begin somedata
-  
+
   This is a data paragraph.
-  
+
   =head1 Don't do this!
-  
+
   This is a data paragraph too.
-  
+
   =end somedata
 
 A Pod processor may signal that the above (specifically the "=head1"
@@ -1662,48 +1662,48 @@ paragraph) is an error.  Note, however, that the following should
 I<not> be treated as an error:
 
   =begin somedata
-  
+
   This is a data paragraph.
-  
+
   =cut
-  
+
   # Yup, this isn't Pod anymore.
   sub excl { (rand() > .5) ? "hoo!" : "hah!" }
-  
+
   =pod
-  
+
   This is a data paragraph too.
-  
+
   =end somedata
 
 And this too is valid:
 
   =begin someformat
-  
+
   This is a data paragraph.
-  
+
     And this is a data paragraph.
-  
+
   =begin someotherformat
-  
+
   This is a data paragraph too.
-  
+
     And this is a data paragraph too.
-  
+
   =begin :yetanotherformat
 
   =head2 This is a command paragraph!
 
   This is an ordinary paragraph!
-  
+
     And this is a verbatim paragraph!
-  
+
   =end :yetanotherformat
-  
+
   =end someotherformat
-  
+
   Another data paragraph!
-  
+
   =end someformat
 
 The contents of the above "=begin :yetanotherformat" ...
@@ -1720,35 +1720,35 @@ other than "=end", "=pod", and "=cut".
 Also consider this valid structure:
 
   =begin :biblio
-  
+
   Wirth's classic is available in several editions, including:
-  
+
   =over
-  
+
   =item
-  
+
   Wirth, Niklaus.  1975.  I<Algorithmen und Datenstrukturen.>
   Teubner, Stuttgart.  [Yes, it's in German.]
-  
+
   =item
-  
+
   Wirth, Niklaus.  1976.  I<Algorithms + Data Structures =
   Programs.>  Prentice-Hall, Englewood Cliffs, NJ.
 
   =back
-  
+
   Buy buy buy!
-  
+
   =begin html
-  
+
   <img src='wirth_spokesmodeling_book.png'>
-  
+
   <hr>
-  
+
   =end html
-  
+
   Now now now!
-  
+
   =end :biblio
 
 There, the "=begin html"..."=end html" region is nested inside
@@ -1774,22 +1774,22 @@ contentless "=for I<something>" and "=for :I<something>"
 paragraphs.  I.e., these should be tolerated:
 
   =for html
-  
+
   =begin html
-  
+
   =end html
-  
+
   =begin :biblio
-  
+
   =end :biblio
 
 Incidentally, note that there's no easy way to express a data
 paragraph starting with something that looks like a command.  Consider:
 
   =begin stuff
-  
+
   =shazbot
-  
+
   =end stuff
 
 There, "=shazbot" will be parsed as a Pod command "shazbot", not as a data
@@ -1804,40 +1804,40 @@ Note that =end commands must match the currently open =begin command.  That
 is, they must properly nest.  For example, this is valid:
 
   =begin outer
-  
+
   X
-  
+
   =begin inner
-  
+
   Y
-  
+
   =end inner
-  
+
   Z
-  
+
   =end outer
 
 while this is invalid:
 
   =begin outer
-  
+
   X
-  
+
   =begin inner
-  
+
   Y
-  
+
   =end outer
-  
+
   Z
-  
+
   =end inner
-  
+
 This latter is improper because when the "=end outer" command is seen, the
 currently open region has the formatname "inner", not "outer".  (It just
 happens that "outer" is the format name of a higher-up region.)  This is
 an error.  Processors must by default report this as an error, and may halt
-processing the document containing that error.  A corrolary of this is that
+processing the document containing that error.  A corollary of this is that
 regions cannot "overlap" -- i.e., the latter block above does not represent
 a region called "outer" which contains X and Y, overlapping a region called
 "inner" which contains Y and Z.  But because it is invalid (as all
@@ -1847,7 +1847,7 @@ anything at all.
 Similarly, this is invalid:
 
   =begin thing
-  
+
   =end hting
 
 This is an error because the region is opened by "thing", and the "=end"
@@ -1856,7 +1856,7 @@ tries to close "hting" [sic].
 This is also invalid:
 
   =begin thing
-  
+
   =end
 
 This is invalid because every "=end" command must have a formatname
diff --git a/pod/perlrequick.pod b/pod/perlrequick.pod
index 1b483c0012..a31adab5eb 100644
--- a/pod/perlrequick.pod
+++ b/pod/perlrequick.pod
@@ -238,7 +238,7 @@ C<cat> is able to match earlier in the string.
     "cats"          =~ /cats|cat|ca|c/; # matches "cats"
 
 At a given character position, the first alternative that allows the
-regex match to succeed wil be the one that matches. Here, all the
+regex match to succeed will be the one that matches. Here, all the
 alternatives match at the first string position, so th first matches.
 
 =head2 Grouping things and hierarchical matching
diff --git a/pod/perlretut.pod b/pod/perlretut.pod
index 65dfb4782c..f4e9bb6440 100644
--- a/pod/perlretut.pod
+++ b/pod/perlretut.pod
@@ -550,7 +550,7 @@ to give them a chance to match.
 
 The last example points out that character classes are like
 alternations of characters.  At a given character position, the first
-alternative that allows the regexp match to succeed wil be the one
+alternative that allows the regexp match to succeed will be the one
 that matches.
 
 =head2 Grouping things and hierarchical matching
@@ -587,7 +587,7 @@ are
 
 Alternations behave the same way in groups as out of them: at a given
 string position, the leftmost alternative that allows the regexp to
-match is taken.  So in the last example at tth first string position,
+match is taken.  So in the last example at the first string position,
 C<"20"> matches the second alternative, but there is nothing left over
 to match the next two digits C<\d\d>.  So perl moves on to the next
 alternative, which is the null alternative and that works, since
diff --git a/pod/perltodo.pod b/pod/perltodo.pod
index 44a7d1030e..f0b1b721c2 100644
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -173,7 +173,7 @@ C<[1234567890]> aren't the only numerals any more.
 
 =head2 POSIX Unicode character classes
 
-([=a=] for equivalance classes, [.ch.] for collation.)
+(C<[=a=]> for equivalance classes, C<[.ch.]> for collation.)
 These are dependent on Unicode normalization and collation.
 
 =head2 Factoring out common suffices/prefices in regexps (trie optimization)
@@ -213,7 +213,7 @@ fp_setmask(), fp_getmask(), fp_setround(), fp_getround()
 (no metaconfig units yet for these).  Don't forget finitel(), fp_classl(),
 fp_class_l(), (yes, both do, unfortunately, exist), and unorderedl().)
 
-As of Perl 5.6.1 is a Perl macro, Perl_isnan().
+As of Perl 5.6.1, there is a Perl macro, Perl_isnan().
 
 =head2 IV/UV preservation
 
@@ -279,7 +279,7 @@ mark-and-sweep GC implementation.
 
 Alan notes that: The basic idea was to extend the parser token stack
 (C<YYSTYPE>) to include a type field so we knew what sort of thing each
-element of the stack was.  The F<<perly.c> code would then have to be
+element of the stack was.  The F<perly.c> code would then have to be
 postprocessed to record the type of each entry on the stack as it was
 created, and the parser patched so that it could unroll the stack
 properly on error.
@@ -322,11 +322,11 @@ Damian Conway is planning to work on this, but it hasn't happened yet.
 
 =head2 Using POSIX calls internally
 
-When faced with a BSD vs. SySV -style interface to some library or
+When faced with a BSD vs. SysV -style interface to some library or
 system function, perl's roots show in that it typically prefers the BSD
 interface (but falls back to the SysV one).  One example is getpgrp().
 Other examples include C<memcpy> vs. C<bcopy>.  There are others, mostly in
-F<<pp_sys.c>.
+F<pp_sys.c>.
 
 Mostly, this item is a suggestion for which way to start a journey into
 an C<#ifdef> forest.  It is not primarily a suggestion to eliminate any of
@@ -444,7 +444,7 @@ Look at the "reification" code in C<av.c>
 
 Currently, indirect object syntax bypasses prototype checks.
 
-=head2 Install HMTL
+=head2 Install HTML
 
 HTML versions of the documentation need to be installed by default; a
 call to C<installhtml> from C<installperl> may be all that's necessary.
@@ -621,11 +621,11 @@ can be found on the CPAN.
 
 =head2 gettimeofday
 
-C<Time::Hires> has been integrated into the core.
+C<Time::HiRes> has been integrated into the core.
 
 =head2 setitimer and getimiter
 
-Adding C<Time::Hires> got us this too.
+Adding C<Time::HiRes> got us this too.
 
 =head2 Testing __DIE__ hook
 
diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod
index e56f3ff9da..e1dcf4b9b5 100644
--- a/pod/perlunicode.pod
+++ b/pod/perlunicode.pod
@@ -275,6 +275,8 @@ have their directionality defined:
     BidiWS      Whitespace
     BidiON      Other Neutrals
 
+=back
+
 =head2 Scripts
 
 The scripts available for C<\p{In...}> and C<\P{In...}>, for example
@@ -481,6 +483,8 @@ below list that have the C<Block> appended).
    Yi Radicals
    Yi Syllables
 
+=over 4
+
 =item *
 
 The special pattern C<\X> match matches any extended Unicode sequence
@@ -563,7 +567,7 @@ than one Unicode character
 
 =back
 
-What doesn't yet work are the followng cases:
+What doesn't yet work are the following cases:
 
 =over 8
 
diff --git a/pod/perlvar.pod b/pod/perlvar.pod
index 2f31ea72e1..2f39d561c2 100644
--- a/pod/perlvar.pod
+++ b/pod/perlvar.pod
@@ -261,7 +261,7 @@ with the rightmost closing parenthesis) of the last successful search
 pattern.  (Mnemonic: the (possibly) Nested parenthesis that most
 recently closed.)
 
-This is primarly used inside C<(?{...})> blocks for examining text
+This is primarily used inside C<(?{...})> blocks for examining text
 recently matched. For example, to effectively capture text to a variable
 (in addition to C<$1>, C<$2>, etc.), replace C<(...)> with