Clean up docmentation installation errors.

5 files changed, 13 insertions, 7 deletions

diff --git a/pod/perlapio.pod b/pod/perlapio.pod
index 85900f157c..5d87ff0e05 100644
--- a/pod/perlapio.pod
+++ b/pod/perlapio.pod
@@ -89,7 +89,7 @@ These are is fprintf()/vfprintf equivalents.
 =item B<PerlIO_stdoutf(fmt,...)>
 
 This is printf() equivalent. printf is #defined to this function,
-so it is (currently) legal to use printf(fmt,...) in perl sources.
+so it is (currently) legal to use C<printf(fmt,...)> in perl sources.
 
 =item B<PerlIO_read(f,buf,count)>, B<PerlIO_write(f,buf,count)>
 
diff --git a/pod/perlre.pod b/pod/perlre.pod
index a364916b29..6d21a65f31 100644
--- a/pod/perlre.pod
+++ b/pod/perlre.pod
@@ -156,7 +156,7 @@ WARNING below.) The scope of $<digit> (and C<$`>, C<$&>, and C<$'>)
 extends to the end of the enclosing BLOCK or eval string, or to the next
 successful pattern match, whichever comes first.  If you want to use
 parentheses to delimit a subpattern (e.g. a set of alternatives) without
-saving it as a subpattern, follow the ( with a ?.
+saving it as a subpattern, follow the ( with a ?:.
 
 You may have as many parentheses as you wish.  If you have more
 than 9 substrings, the variables $10, $11, ... refer to the
diff --git a/pod/perltrap.pod b/pod/perltrap.pod
index be58bc52e2..c3a316564b 100644
--- a/pod/perltrap.pod
+++ b/pod/perltrap.pod
@@ -796,7 +796,7 @@ that perl4 exhibits only for scalars.
     # SUB: this should never appear
     # SUB: this should never appear
 
-=back 
+=back
 
 =head2 Context Traps - scalar, list contexts
 
@@ -868,6 +868,8 @@ Probably a bug.
 
 Perl4-to-Perl5 traps involving precedence order.
 
+=over 5
+
 =item * 
 
 These are now semantic errors because of precedence:
@@ -1324,6 +1326,8 @@ immediately.
 
 Everything else.
 
+=over 5
+
 =item * Unclassified
 
 C<require>/C<do> trap using returned value
diff --git a/pod/perlxstut.pod b/pod/perlxstut.pod
index 592f2ee189..85a8c71f3f 100644
--- a/pod/perlxstut.pod
+++ b/pod/perlxstut.pod
@@ -88,7 +88,7 @@ test" is sufficient.
 Our first extension will be very simple.  When we call the routine in the
 extension, it will print out a well-known message and return.
 
-Run "h2xs -A -n Mytest".  This creates a directory named Mytest, possibly under
+Run C<h2xs -A -n Mytest>.  This creates a directory named Mytest, possibly under
 ext/ if that directory exists in the current working directory.  Several files
 will be created in the Mytest dir, including MANIFEST, Makefile.PL, Mytest.pm,
 Mytest.xs, test.pl, and Changes.
@@ -271,7 +271,7 @@ contain the shared library that we will build.  Once we have tested it, we
 can install it into its final location.
 
 Invoking the test script via "make test" did something very important.  It
-invoked perl with all those -I arguments so that it could find the various
+invoked perl with all those C<-I> arguments so that it could find the various
 files that are part of the extension.
 
 It is I<very> important that while you are still testing extensions that
@@ -582,11 +582,13 @@ for equality, but rather the difference being below a certain epsilon factor,
 
 Run "make test" and all should be well.
 
-=head 2 WHAT HAS HAPPENED HERE?
+=head2 WHAT HAS HAPPENED HERE?
 
 Unlike previous examples, we've now run h2xs on a real include file.  This
 has caused some extra goodies to appear in both the .pm and .xs files.
 
+=over 4
+
 =item *
 
 In the .xs file, there's now a #include declaration with the full path to
diff --git a/pod/pod2man.PL b/pod/pod2man.PL
index 8c054ca521..85c98c55e3 100644
--- a/pod/pod2man.PL
+++ b/pod/pod2man.PL
@@ -402,7 +402,7 @@ if ($name ne 'something') {
 		    $oops++;
 		    warn "$0: Improper man page - no dash in NAME header in paragraph $. of $ARGV[0]\n"
 		}
-		%namedesc = split /\s+-\s+/;
+		%namedesc = split /\s+-+\s+/;
 		last FCHECK;
 	    }
 	    next if /^=cut\b/;	# DB_File and Net::Ping have =cut before NAME