From: Larry W. Virden <lvirden@cas.org>
Date: Wed, 11 Jun 1997 00:00:00 +0000 (+1200)
Subject: misc perl5.004 doc fixes
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=2ceaccd71c2e15067691ff5d6509bed0b81708ee;p=p5sagit%2Fp5-mst-13.2.git

misc perl5.004 doc fixes

here are a few doc changes that fix a few typos, etc.

p5p-msgid: 199705160419.AAA16317@cas.org
---

diff --git a/lib/Pod/Html.pm b/lib/Pod/Html.pm
index aaefc3c..6efaf1f 100644
--- a/lib/Pod/Html.pm
+++ b/lib/Pod/Html.pm
@@ -916,7 +916,7 @@ sub process_over {
 # process_back - process a pod back tag and convert it to HTML format.
 #
 sub process_back {
-    warn "$0: $podfile: unexpected =back directive in paragraph $paragraph.  ignorning.\n"
+    warn "$0: $podfile: unexpected =back directive in paragraph $paragraph.  ignoring.\n"
 	unless $listlevel;
     return unless $listlevel;
 
diff --git a/pod/perlfaq4.pod b/pod/perlfaq4.pod
index bcf0399..a5b505c 100644
--- a/pod/perlfaq4.pod
+++ b/pod/perlfaq4.pod
@@ -371,7 +371,7 @@ suggests (assuming your string is contained in $text):
 
 If you want to represent quotation marks inside a
 quotation-mark-delimited field, escape them with backslashes (eg,
-C<"like \"this\"").  Unescaping them is a task addressed earlier in
+C<"like \"this\"">.  Unescaping them is a task addressed earlier in
 this section.
 
 Alternatively, the Text::ParseWords module (part of the standard perl
diff --git a/pod/roffitall b/pod/roffitall
index d69054f..cbd19af 100755
--- a/pod/roffitall
+++ b/pod/roffitall
@@ -180,14 +180,22 @@ fi
 #psroff -t -man -rC1 -rD1 -rF1 > $tmp/PerlDoc.ps 2>$tmp/PerlTOC.raw
 #nroff -man -rC1 -rD1 -rF1 > $tmp/PerlDoc.txt 2>$tmp/PerlTOC.nr.raw
 
+# First, create the raw data
 run="$cmd -rC1 -rD1 -rF1 >$tmp/PerlDoc.$ext 2>$tmp/PerlTOC.$ext.raw"
 echo "$me: running $run"
 eval $run $toroff
+
+#Now create the TOC
 echo "$me: parsing TOC"
 ./rofftoc $tmp/PerlTOC.$ext.raw > $tmp/PerlTOC.tmp.man
 run="$cmd $tmp/PerlTOC.tmp.man >$tmp/PerlTOC.$ext"
 echo "$me: running $run"
 eval $run
+
+# Finally, recreate the Doc, without the blank page 0
+run="$cmd -rC1 -rD1 >$tmp/PerlDoc.$ext 2>$tmp/PerlTOC.$ext.raw"
+echo "$me: running $run"
+eval $run $toroff
 rm -f $tmp/PerlTOC.tmp.man $tmp/PerlTOC.$ext.raw
 echo "$me: leaving you with $tmp/PerlDoc.$ext and $tmp/PerlTOC.$ext"
 
diff --git a/vms/ext/DCLsym/DCLsym.pm b/vms/ext/DCLsym/DCLsym.pm
index 057951d..44c4b84 100644
--- a/vms/ext/DCLsym/DCLsym.pm
+++ b/vms/ext/DCLsym/DCLsym.pm
@@ -201,6 +201,8 @@ can also call methods directly to manipulate individual symbols.  In some
 cases, this allows you finer control than using a tied hash aggregate.  The
 following methods are supported:
 
+=over
+
 =item new
 
 This creates a C<VMS::DCLsym> object which can be used as a handle for later
diff --git a/vms/ext/Stdio/Stdio.pm b/vms/ext/Stdio/Stdio.pm
index 516e678..218c406 100644
--- a/vms/ext/Stdio/Stdio.pm
+++ b/vms/ext/Stdio/Stdio.pm
@@ -76,7 +76,7 @@ __END__
 
 =head1 NAME
 
-VMS::Stdio
+VMS::Stdio - standard I/O functions via VMS extensions
 
 =head1 SYNOPSIS
 
@@ -99,7 +99,7 @@ remove("another.file");
 
 =head1 DESCRIPTION
 
-This package gives Perl scripts access to VMS extensions to several
+This package gives Perl scripts access via VMS extensions to several
 C stdio operations not available through Perl's CORE I/O functions.
 The specific routines are described below.  These functions are
 prototyped as unary operators, with the exception of C<vmsopen>
@@ -141,6 +141,8 @@ VMS::Stdio function.  This compatibility interface will be
 removed in a future release of this extension, so please
 update your code to use the new routines.
 
+=over
+
 =item flush
 
 This function causes the contents of stdio buffers for the specified
diff --git a/vms/perlvms.pod b/vms/perlvms.pod
index 5f9e91f..c599e58 100644
--- a/vms/perlvms.pod
+++ b/vms/perlvms.pod
@@ -58,7 +58,7 @@ define a foreign command to invoke this image.
 Perl extensions are packages which provide both XS and Perl code
 to add new functionality to perl.  (XS is a meta-language which
 simplifies writing C code which interacts with Perl, see
-L<perlapi> for more details.)  The Perl code for an
+L<perlxs> for more details.)  The Perl code for an
 extension is treated like any other library module - it's
 made available in your script through the appropriate
 C<use> or C<require> statement, and usually defines a Perl