Integrate:

[ 23945]
A small precision in the docs for overloaded regexp escapes
(see bug #33906)

[ 23963]
Mac OS Classic vs Mac OS X clarications
by Sherm Pendley

[ 23971]
Fix documentation bug in using Socket's import tags :

Subject: [perl #34141] example in perlbug -f getsockopt incomplete
From: David Dyck (via RT) <perlbug-followup@perl.org>
Date: 15 Feb 2005 07:35:45 -0000
Message-ID: <rt-3.0.11-34141-107730.6.0777451251105@perl.org>

[ 24000]
do "filename" is not really used with perl subroutine librairies
anymore.

[ 24021]
8 is not an octal digit. (from Debian)

[ 24024]
FAQ sync

[ 24033]
Doc patches to clarify the stringification rules of {} and =>
by Jarkko (bug #34419)

[ 24036]
Subject: Re: [perl #34155] perldoc -f hex should say how to convert back
From: David Nicol <davidnicol@gmail.com>
Date: Tue, 8 Mar 2005 18:23:11 -0600
Message-ID: <934f64a20503081623713f6d27@mail.gmail.com>

[ 24045]
Remove trie optimisation from the todo list

[ 24047]
Subject: [PATCH] perlrun typo (env PERLDB_OPTS)
From: Alexey Tourbin <at@altlinux.ru>
Date: Sat, 19 Mar 2005 03:40:13 +0300
Message-ID: <20050319004013.GJ12596@solemn.turbinal.org>

[ 24066]
Fix unresolved POD link

[ 24090]
Make the spelling of whitespace (vs white-space and white space)
  more consistent
From: Offer Kaye <offer.kaye@gmail.com>
Date: Thu, 17 Mar 2005 14:47:36 -0500
Message-ID: <5694250503171147668e73c7@mail.gmail.com>

[ 24123]
This is 5.9.2. Mostly.

[ 24127]
Add a note about installhtml

[ 24128]
FAQ sync.

[ 24129]
POD fixes.
p4raw-link: @24129 on //depot/perl: c234bec13fe4a2f24d15acc1160981b4c4765876
p4raw-link: @24128 on //depot/perl: 571e049f835793c9e2ebba49d438be94a271f3ee
p4raw-link: @24127 on //depot/perl: 3a89a73cb887422a8ff6ad0a1a2725cc8f177fb7
p4raw-link: @24123 on //depot/perl: 690cf44b891769f83179a3b154e2b155ab8c433c
p4raw-link: @24090 on //depot/perl: 6b0ac556af9eedace4d32a9b51232914d1118023
p4raw-link: @24066 on //depot/perl: ae4c54028c3d99561d10bd627f850a84553c8e0c
p4raw-link: @24047 on //depot/perl: fdac53cdf7b8b7030448d0e63e6537e85a7a19df
p4raw-link: @24045 on //depot/perl: 5ee738cbe35eeb5b92b8391ea3fa711d75f88414
p4raw-link: @24036 on //depot/perl: 38366c114d966e1bfc88beb6923273d54aa6e78d
p4raw-link: @24033 on //depot/perl: 719b43e8a7892cfc854b9123fcad88c53828b0b9
p4raw-link: @24024 on //depot/perl: 7678ccedef3d2583c849cbd8e5a13ba36925ac4c
p4raw-link: @24021 on //depot/perl: 6ed007ae6b14c10b7b8e33947dc7bbed976b6e7c
p4raw-link: @24000 on //depot/perl: ea63ef19ca3f585d76378df52ef140c169642026
p4raw-link: @23971 on //depot/perl: 4852725b6599d1cee72970100a6c19e0adc9b5b7
p4raw-link: @23963 on //depot/perl: 8e30f651d14878f73c030bd08b8c6efdc65d89fe
p4raw-link: @23945 on //depot/perl: 580a9fe1f2eadca33b9bfe7700739a00e7d804ca

p4raw-id: //depot/maint-5.8/perl@24141
p4raw-integrated: from //depot/perl@24140 'copy in' pod/perllocale.pod
	(@16520..) pod/perlxstut.pod (@17766..) pod/perlreref.pod
	(@20661..) pod/perlmodinstall.pod (@22735..) pod/perlfaq2.pod
	pod/perlfaq8.pod pod/perlfaq9.pod (@23466..) pod/perlhist.pod
	(@23570..) pod/perlfaq5.pod (@23647..) pod/perlopentut.pod
	(@23963..) pod/perlfaq.pod pod/perlfaq1.pod pod/perlfaq3.pod
	pod/perlfaq4.pod (@24024..) 'edit in' pod/perlre.pod (@23945..)
	pod/perlop.pod (@24033..) 'merge in' pod/perldata.pod
	(@23496..)
p4raw-integrated: from //depot/perl@24045 'ignore' pod/perltodo.pod
	(@23754..)
p4raw-integrated: from //depot/perl@24024 'ignore' pod/perlfaq6.pod
	pod/perlfaq7.pod (@23509..)
p4raw-integrated: from //depot/perl@24000 'edit in' pod/perlfunc.pod
	(@23971..)
p4raw-integrated: from //depot/perl@23963 'edit in' pod/perlrun.pod
	(@23907..)

1 files changed, 5 insertions, 5 deletions

diff --git a/pod/perlopentut.pod b/pod/perlopentut.pod
index 3116f785c1..f023434ed3 100644
--- a/pod/perlopentut.pod
+++ b/pod/perlopentut.pod
@@ -67,7 +67,7 @@ examples would effectively mean
 which is definitely not what you want.
 
 The other important thing to notice is that, just as in the shell,
-any white space before or after the filename is ignored.  This is good,
+any whitespace before or after the filename is ignored.  This is good,
 because you wouldn't want these to do different things:
 
     open INFO,   "<datafile"   
@@ -82,7 +82,7 @@ in from a different file, and forget to trim it before opening:
 
 This is not a bug, but a feature.  Because C<open> mimics the shell in
 its style of using redirection arrows to specify how to open the file, it
-also does so with respect to extra white space around the filename itself
+also does so with respect to extra whitespace around the filename itself
 as well.  For accessing files with naughty names, see 
 L<"Dispelling the Dweomer">.
 
@@ -332,7 +332,7 @@ C<sysopen> takes 3 (or 4) arguments.
 
 The HANDLE argument is a filehandle just as with C<open>.  The PATH is
 a literal path, one that doesn't pay attention to any greater-thans or
-less-thans or pipes or minuses, nor ignore white space.  If it's there,
+less-thans or pipes or minuses, nor ignore whitespace.  If it's there,
 it's part of the path.  The FLAGS argument contains one or more values
 derived from the Fcntl module that have been or'd together using the
 bitwise "|" operator.  The final argument, the MASK, is optional; if
@@ -364,7 +364,7 @@ added to the sysopen() flags because large files are the default.)
 Here's how to use C<sysopen> to emulate the simple C<open> calls we had
 before.  We'll omit the C<|| die $!> checks for clarity, but make sure
 you always check the return values in real code.  These aren't quite
-the same, since C<open> will trim leading and trailing white space,
+the same, since C<open> will trim leading and trailing whitespace,
 but you'll get the idea.
 
 To open a file for reading:
@@ -521,7 +521,7 @@ working directory, slash the directory separator, and disallows ASCII
 NULs within a valid filename.  Most systems follow these conventions,
 including all POSIX systems as well as proprietary Microsoft systems.
 The only vaguely popular system that doesn't work this way is the
-proprietary Macintosh system, which uses a colon where the rest of us
+"Classic" Macintosh system, which uses a colon where the rest of us
 use a slash.  Maybe C<sysopen> isn't such a bad idea after all.
 
 If you want to use C<< <ARGV> >> processing in a totally boring