* Backported Tom's perlfaq cleanup to the perlfaq repo, and now they are back here :)

5 files changed, 13 insertions, 13 deletions

diff --git a/pod/perlfaq2.pod b/pod/perlfaq2.pod
index 5f03873857..03dc2d3064 100644
--- a/pod/perlfaq2.pod
+++ b/pod/perlfaq2.pod
@@ -217,7 +217,7 @@ including setting the Followup-To header line to NOT include alt.sources;
 see their FAQ ( http://www.faqs.org/faqs/alt-sources-intro/ ) for details.
 
 If you're just looking for software, first use Google
-( http://www.google.com ), Google's usenet search interface
+( http://www.google.com ), Google's Usenet search interface
 ( http://groups.google.com ),  and CPAN Search ( http://search.cpan.org ).
 This is faster and more productive than just posting a request.
 
diff --git a/pod/perlfaq3.pod b/pod/perlfaq3.pod
index c529c269c9..e9fb3f3acb 100644
--- a/pod/perlfaq3.pod
+++ b/pod/perlfaq3.pod
@@ -275,7 +275,7 @@ You might also try pltags: http://www.mscha.com/pltags.zip
 
 Perl programs are just plain text, so any editor will do.
 
-If you're on Unix, you already have an IDE--Unix itself.  The UNIX
+If you're on Unix, you already have an IDE--Unix itself.  The Unix
 philosophy is the philosophy of several small tools that each do one
 thing and do it well.  It's like a carpenter's toolbox.
 
@@ -425,7 +425,7 @@ For vi lovers in general, Windows or elsewhere:
 
 nvi ( http://www.bostic.com/vi/ , available from CPAN in src/misc/) is
 yet another vi clone, unfortunately not available for Windows, but in
-UNIX platforms you might be interested in trying it out, firstly because
+Unix platforms you might be interested in trying it out, firstly because
 strictly speaking it is not a vi clone, it is the real vi, or the new
 incarnation of it, and secondly because you can embed Perl inside it
 to use Perl as the scripting language.  nvi is not alone in this,
@@ -489,7 +489,7 @@ MKS and U/WIN are commercial (U/WIN is free for educational and
 research purposes), Cygwin is covered by the GNU General Public
 License (but that shouldn't matter for Perl use).  The Cygwin, MKS,
 and U/WIN all contain (in addition to the shells) a comprehensive set
-of standard UNIX toolkit utilities.
+of standard Unix toolkit utilities.
 
 If you're transferring text files between Unix and Windows using FTP
 be sure to transfer them in ASCII mode so the ends of lines are
@@ -912,7 +912,7 @@ executables for HP-UX, Linux, Solaris and Windows."
 
 Perl2Exe ( http://www.indigostar.com/perl2exe.htm ) is a command line
 program for converting perl scripts to executable files.  It targets both
-Windows and unix platforms.
+Windows and Unix platforms.
 
 =head2 How can I get C<#!perl> to work on [MS-DOS,NT,...]?
 
@@ -1080,7 +1080,7 @@ or
 
 The C<ExtUtils::MakeMaker> module, better known simply as "MakeMaker",
 turns a Perl script, typically called C<Makefile.PL>, into a Makefile.
-The unix tool C<make> uses this file to manage dependencies and actions
+The Unix tool C<make> uses this file to manage dependencies and actions
 to process and install a Perl distribution.
 
 =head1 AUTHOR AND COPYRIGHT
diff --git a/pod/perlfaq4.pod b/pod/perlfaq4.pod
index 5c7e1346eb..f671b626bf 100644
--- a/pod/perlfaq4.pod
+++ b/pod/perlfaq4.pod
@@ -62,7 +62,7 @@ are in base 10:
 	print $string + 44; # prints 688, certainly not octal!
 
 This problem usually involves one of the Perl built-ins that has the
-same name a unix command that uses octal numbers as arguments on the
+same name a Unix command that uses octal numbers as arguments on the
 command line. In this example, C<chmod> on the command line knows that
 its first argument is octal because that's what it does:
 
@@ -537,7 +537,7 @@ doesn't matter and you end up with the previous date.
 
 (contributed by brian d foy)
 
-Perl itself never had a Y2K problem, although that nevers stopped people
+Perl itself never had a Y2K problem, although that never stopped people
 from creating Y2K problems on their own. See the documentation for
 C<localtime> for its proper use.
 
diff --git a/pod/perlfaq7.pod b/pod/perlfaq7.pod
index 1cc32c20e1..1bfab25854 100644
--- a/pod/perlfaq7.pod
+++ b/pod/perlfaq7.pod
@@ -656,7 +656,7 @@ see L<perltoot/"Overridden Methods">.
 Calling a subroutine as C<&foo> with no trailing parentheses ignores
 the prototype of C<foo> and passes it the current value of the argument
 list, C<@_>. Here's an example; the C<bar> subroutine calls C<&foo>,
-which prints what its arguments list:
+which prints its arguments list:
 
 	sub bar { &foo }
 
diff --git a/pod/perlfaq8.pod b/pod/perlfaq8.pod
index 9f78d30651..99173989bd 100644
--- a/pod/perlfaq8.pod
+++ b/pod/perlfaq8.pod
@@ -103,7 +103,7 @@ It even includes limited support for Windows.
 
 However, using the code requires that you have a working C compiler
 and can use it to build and install a CPAN module.  Here's a solution
-using the standard C<POSIX> module, which is already on your systems
+using the standard C<POSIX> module, which is already on your system
 (assuming your system supports POSIX).
 
 	use HotKey;
@@ -391,7 +391,7 @@ C<Parallel::ForkManager>, C<POE>, C<Proc::Background>, and
 C<Win32::Process>. There are many other modules you might use, so
 check those namespaces for other options too.
 
-If you are on a unix-like system, you might be able to get away with a
+If you are on a Unix-like system, you might be able to get away with a
 system call where you put an C<&> on the end of the command:
 
 	system("cmd &")
@@ -496,7 +496,7 @@ the VMS equivalent is C<set time>.
 However, if all you want to do is change your time zone, you can
 probably get away with setting an environment variable:
 
-	$ENV{TZ} = "MST7MDT";		   # unixish
+	$ENV{TZ} = "MST7MDT";		   # Unixish
 	$ENV{'SYS$TIMEZONE_DIFFERENTIAL'}="-5" # vms
 	system "trn comp.lang.perl.misc";
 
@@ -866,7 +866,7 @@ stuck, because Windows does not have an argc/argv-style API.
 =head2 Why can't my script read from STDIN after I gave it EOF (^D on Unix, ^Z on MS-DOS)?
 
 This happens only if your perl is compiled to use stdio instead of
-perlio, which is the default. Some (maybe all?) stdio's set error and
+perlio, which is the default. Some (maybe all?) stdios set error and
 eof flags that you may need to clear. The C<POSIX> module defines
 C<clearerr()> that you can use.  That is the technically correct way to
 do it.  Here are some less reliable workarounds: