[ID 20010525.001] Pod typo nits fixed

From: lvirden@cas.org
Date: Fri, 25 May 2001 06:57:43 -0400 (EDT)
Message-Id: <200105251057.f4PAvhY13003@lwv26awu.cas.org>

minus the perlsolaris decimation plus the

Subject: Re: [ID 20010525.001] Pod typo nits fixed
From: "Philip Newton" <Philip.Newton@gmx.net>
Date: Fri, 25 May 2001 18:05:55 +0200
Message-Id: <200105251604.f4PG4kt15034@chaos.wustl.edu>

p4raw-id: //depot/perl@10226

9 files changed, 30 insertions, 20 deletions

diff --git a/pod/perl5005delta.pod b/pod/perl5005delta.pod
index 78bf90f616..c60d37c3e6 100644
--- a/pod/perl5005delta.pod
+++ b/pod/perl5005delta.pod
@@ -145,7 +145,7 @@ Most of the Perl documentation was previously under the implicit GNU
 General Public License or the Artistic License (at the user's choice).
 Now much of the documentation unambiguously states the terms under which
 it may be distributed.  Those terms are in general much less restrictive
-than the GNU GPL.  See L<perl> and the individual perl man pages listed
+than the GNU GPL.  See L<perl> and the individual perl manpages listed
 therein.
 
 =head1 Core Changes
diff --git a/pod/perldebtut.pod b/pod/perldebtut.pod
index e11102e567..693e938e94 100644
--- a/pod/perldebtut.pod
+++ b/pod/perldebtut.pod
@@ -666,7 +666,7 @@ and there's a B<vi> interface too.
 
 You don't have to do this all on the command line, though, there are a few GUI
 options out there.  The nice thing about these is you can wave a mouse over a
-variable and a dump of it's data will appear in an appropriate window, or in a
+variable and a dump of its data will appear in an appropriate window, or in a
 popup balloon, no more tiresome typing of 'x $varname' :-)
 
 In particular have a hunt around for the following:
diff --git a/pod/perlebcdic.pod b/pod/perlebcdic.pod
index ccfe1392ba..c98b46c6e7 100644
--- a/pod/perlebcdic.pod
+++ b/pod/perlebcdic.pod
@@ -45,7 +45,7 @@ A particular 8-bit extension to ASCII that includes grave and acute
 accented Latin characters.  Languages that can employ ISO 8859-1 
 include all the languages covered by ASCII as well as Afrikaans, 
 Albanian, Basque, Catalan, Danish, Faroese, Finnish, Norwegian, 
-Portugese, Spanish, and Swedish.  Dutch is covered albeit without 
+Portuguese, Spanish, and Swedish.  Dutch is covered albeit without 
 the ij ligature.  French is covered too but without the oe ligature. 
 German can use ISO 8859-1 but must do so without German-style
 quotation marks.  This set is based on Western European extensions 
@@ -597,7 +597,7 @@ XPG operability often implies the presence of an I<iconv> utility
 available from the shell or from the C library.  Consult your system's
 documentation for information on iconv.
 
-On OS/390 or z/OS see the iconv(1) man page.  One way to invoke the iconv 
+On OS/390 or z/OS see the iconv(1) manpage.  One way to invoke the iconv 
 shell utility from within perl would be to:
 
     # OS/390 or z/OS example
@@ -1243,7 +1243,7 @@ translation difficulties.  In particular one popular nroff implementation
 was known to strip accented characters to their unaccented counterparts 
 while attempting to view this document through the B<pod2man> program 
 (for example, you may see a plain C<y> rather than one with a diaeresis 
-as in E<yuml>).  Another nroff truncated the resultant man page at
+as in E<yuml>).  Another nroff truncated the resultant manpage at
 the first occurrence of 8 bit characters.
 
 Not all shells will allow multiple C<-e> string arguments to perl to
diff --git a/pod/perlfaq3.pod b/pod/perlfaq3.pod
index fdfa26d277..dabe5687a5 100644
--- a/pod/perlfaq3.pod
+++ b/pod/perlfaq3.pod
@@ -11,7 +11,7 @@ and programming support.
 
 Have you looked at CPAN (see L<perlfaq2>)?  The chances are that
 someone has already written a module that can solve your problem.
-Have you read the appropriate man pages?  Here's a brief index:
+Have you read the appropriate manpages?  Here's a brief index:
 
 	Basics	        perldata, perlvar, perlsyn, perlop, perlsub
 	Execution	perlrun, perldebug
@@ -25,12 +25,12 @@ Have you read the appropriate man pages?  Here's a brief index:
 	Various 	http://www.perl.com/CPAN/doc/FMTEYEWTK/index.html
 			(not a man-page but still useful)
 
-A crude table of contents for the Perl man page set is found in L<perltoc>.
+A crude table of contents for the Perl manpage set is found in L<perltoc>.
 
 =head2 How can I use Perl interactively?
 
 The typical approach uses the Perl debugger, described in the
-perldebug(1) man page, on an ``empty'' program, like this:
+perldebug(1) manpage, on an ``empty'' program, like this:
 
     perl -de 42
 
diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index 94c6dfd96b..6b67e5706b 100644
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -273,7 +273,7 @@ From http://rsync.samba.org/README.html:
 
    "Rsync uses rsh or ssh for communication. It does not need to be
     setuid and requires no special privileges for installation.  It
-    does not require a inetd entry or a deamon.  You must, however,
+    does not require an inetd entry or a daemon.  You must, however,
     have a working rsh or ssh system.  Using ssh is recommended for
     its security features."
 
@@ -434,7 +434,7 @@ look how others apply the fix.
 =item Finding the source of misbehaviour
 
 When you keep in sync with bleadperl, the pumpking would love to
-I<see> that the community efforts realy work. So after each of his
+I<see> that the community efforts really work. So after each of his
 sync points, you are to 'make test' to check if everything is still
 in working order. If it is, you do 'make ok', which will send an OK
 report to perlbug@perl.org. (If you do not have access to a mailer
@@ -442,7 +442,7 @@ from the system you just finished successfully 'make test', you can
 do 'make okfile', which creates the file C<perl.ok>, which you can
 than take to your favourite mailer and mail yourself).
 
-But of course, as always, things will not allways lead to a success
+But of course, as always, things will not always lead to a success
 path, and one or more test do not pass the 'make test'. Before
 sending in a bug report (using 'make nok' or 'make nokfile'), check
 the mailing list if someone else has reported the bug already and if
@@ -1813,9 +1813,9 @@ In Tru64 the following options are available:
 
 =over 4
 
-=item -p[rodecures]
+=item -p[rocedures]
 
-Procecures sorted in descending order by the number of cycles executed
+Procedures sorted in descending order by the number of cycles executed
 in each procedure.  Useful for finding the hotspot procedures.
 (This is the default option.)
 
diff --git a/pod/perltoc.pod b/pod/perltoc.pod
index a75f39ea1f..f22aacbcb1 100644
--- a/pod/perltoc.pod
+++ b/pod/perltoc.pod
@@ -4214,11 +4214,12 @@ PerlIO_apply_layers(f,mode,layers), PerlIO_binmode(f,ptype,imode,layers),
 
 =item Rewrite perldoc
 
-=item Install .3p man pages
+=item Install .3p manpages
 
 =item Unicode tutorial
 
 =item Update POSIX.pm for 1003.1-2
+
 =head2 Retargetable installation
 
 =item POSIX emulation on non-POSIX systems
@@ -4242,7 +4243,9 @@ PerlIO_apply_layers(f,mode,layers), PerlIO_binmode(f,ptype,imode,layers),
 =item Make tr/// return histogram
 
 =item Compile to real threaded code
+
 =head2 Structured types
+
 =head2 Modifiable $1 et al.
 
 =item Procedural interfaces for IO::*, etc.
@@ -4352,9 +4355,11 @@ PerlIO_apply_layers(f,mode,layers), PerlIO_binmode(f,ptype,imode,layers),
 =item Lexically scoped typeglobs
 
 =item format BOTTOM
+
 =head2 report HANDLE
 
 =item Generalised want()/caller())
+
 =head2 Named prototypes
 
 =item Built-in globbing
diff --git a/pod/perltodo.pod b/pod/perltodo.pod
index 8c94a29c9a..a8bfbabcb4 100644
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -418,9 +418,9 @@ There are a few suggestions for what to do with C<perldoc>: maybe a
 full-text search, an index function, locating pages on a particular
 high-level subject, and so on.
 
-=head2 Install .3p man pages
+=head2 Install .3p manpages
 
-This is a bone of contention; we can create C<.3p> man pages for each
+This is a bone of contention; we can create C<.3p> manpages for each
 built-in function, but should we install them by default? Tcl does this,
 and it clutters up C<apropos>.
 
@@ -429,6 +429,7 @@ and it clutters up C<apropos>.
 Simon Cozens promises to do this before he gets old.
 
 =head2 Update POSIX.pm for 1003.1-2
+
 =head2 Retargetable installation
 
 Allow C<@INC> to be changed after Perl is built.
@@ -468,7 +469,9 @@ code.
 There is a patch for this, but it may require Unicodification.
 
 =head2 Compile to real threaded code
+
 =head2 Structured types
+
 =head2 Modifiable $1 et al.
 
     ($x = "elephant") =~ /e(ph)/;
@@ -690,11 +693,13 @@ This would break old code; use C<do{{ }}> instead.
 Not needed now we have lexical IO handles.
 
 =head2 format BOTTOM
+
 =head2 report HANDLE
 
 Damian Conway's text formatting modules seem to be the Way To Go.
 
 =head2 Generalised want()/caller())
+
 =head2 Named prototypes
 
 These both seem to be delayed until Perl 6.
diff --git a/pod/perlutil.pod b/pod/perlutil.pod
index 45341d9e85..f299f2d13f 100644
--- a/pod/perlutil.pod
+++ b/pod/perlutil.pod
@@ -29,7 +29,7 @@ described in this document.
 
 If it's run from a terminal, F<perldoc> will usually call F<pod2man> to
 translate POD (Plain Old Documentation - see L<perlpod> for an
-explanation) into a man page, and then run F<man> to display it; if
+explanation) into a manpage, and then run F<man> to display it; if
 F<man> isn't available, F<pod2text> will be used instead and the output
 piped through your favourite pager.
 
diff --git a/pod/perlxstut.pod b/pod/perlxstut.pod
index f06e166326..ad648ebf37 100644
--- a/pod/perlxstut.pod
+++ b/pod/perlxstut.pod
@@ -915,9 +915,9 @@ way to store and load your extra subroutines.
 
 There is absolutely no excuse for not documenting your extension.
 Documentation belongs in the .pm file.  This file will be fed to pod2man,
-and the embedded documentation will be converted to the man page format,
-then placed in the blib directory.  It will be copied to Perl's man
-page directory when the extension is installed.
+and the embedded documentation will be converted to the manpage format,
+then placed in the blib directory.  It will be copied to Perl's
+manpage directory when the extension is installed.
 
 You may intersperse documentation and Perl code within the .pm file.
 In fact, if you want to use method autoloading, you must do this,