Make the spelling of whitespace (vs white-space and white space)

  more consistent
Message-ID: <5694250503171147668e73c7@mail.gmail.com>

p4raw-id: //depot/perl@24090

5 files changed, 12 insertions, 12 deletions

diff --git a/pod/perllocale.pod b/pod/perllocale.pod
index e2ea04d9dc..3e36543f85 100644
--- a/pod/perllocale.pod
+++ b/pod/perllocale.pod
@@ -736,8 +736,8 @@ Scalar true/false result never tainted.
 Subpatterns, either delivered as a list-context result or as $1 etc.
 are tainted if C<use locale> is in effect, and the subpattern regular
 expression contains C<\w> (to match an alphanumeric character), C<\W>
-(non-alphanumeric character), C<\s> (white-space character), or C<\S>
-(non white-space character).  The matched-pattern variable, $&, $`
+(non-alphanumeric character), C<\s> (whitespace character), or C<\S>
+(non whitespace character).  The matched-pattern variable, $&, $`
 (pre-match), $' (post-match), and $+ (last match) are also tainted if
 C<use locale> is in effect and the regular expression contains C<\w>,
 C<\W>, C<\s>, or C<\S>.
diff --git a/pod/perlop.pod b/pod/perlop.pod
index 7c96ee05ac..98d39ef6a7 100644
--- a/pod/perlop.pod
+++ b/pod/perlop.pod
@@ -1383,9 +1383,9 @@ Examples:
 	\*/	# Match the closing delimiter.
     } []gsx;
 
-    s/^\s*(.*?)\s*$/$1/;	# trim white space in $_, expensively
+    s/^\s*(.*?)\s*$/$1/;	# trim whitespace in $_, expensively
 
-    for ($variable) {		# trim white space in $variable, cheap
+    for ($variable) {		# trim whitespace in $variable, cheap
 	s/^\s+//;
 	s/\s+$//;
     }
diff --git a/pod/perlopentut.pod b/pod/perlopentut.pod
index 72d91b73a3..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:
diff --git a/pod/perlre.pod b/pod/perlre.pod
index bc5e7c914d..bf319ba16c 100644
--- a/pod/perlre.pod
+++ b/pod/perlre.pod
@@ -1265,7 +1265,7 @@ Overloaded constants (see L<overload>) provide a simple way to extend
 the functionality of the RE engine.
 
 Suppose that we want to enable a new RE escape-sequence C<\Y|> which
-matches at boundary between white-space characters and non-whitespace
+matches at boundary between whitespace characters and non-whitespace
 characters.  Note that C<(?=\S)(?<!\S)|(?!\S)(?<=\S)> matches exactly
 at these positions, so we want to have each C<\Y|> in the place of the
 more complicated version.  We can create a module C<customre> to do
diff --git a/pod/perlxstut.pod b/pod/perlxstut.pod
index ceb65e0b5b..d1edf61a76 100644
--- a/pod/perlxstut.pod
+++ b/pod/perlxstut.pod
@@ -233,9 +233,9 @@ Add the following to the end of Mytest.xs:
 	    OUTPUT:
 		RETVAL
 
-There does not need to be white space at the start of the "C<int input>"
+There does not need to be whitespace at the start of the "C<int input>"
 line, but it is useful for improving readability.  Placing a semi-colon at
-the end of that line is also optional.  Any amount and kind of white space
+the end of that line is also optional.  Any amount and kind of whitespace
 may be placed between the "C<int>" and "C<input>".
 
 Now re-run make to rebuild our new shared library.
@@ -413,7 +413,7 @@ of round is of type "void".
 
 You specify the parameters that will be passed into the XSUB on the line(s)
 after you declare the function's return value and name.  Each input parameter
-line starts with optional white space, and may have an optional terminating
+line starts with optional whitespace, and may have an optional terminating
 semicolon.
 
 The list of output parameters occurs at the very end of the function, just