8 files changed, 40 insertions, 40 deletions
diff --git a/lib/Net/Config.eg b/lib/Net/Config.eg
index 450acacd76..77dc1f138b 100644
--- a/lib/Net/Config.eg
+++ b/lib/Net/Config.eg
@@ -26,7 +26,7 @@ use strict;
 	# your internet domain
 	inet_domain => undef,
 
-	# If you have an ftp proxy firewall (not a http firewall)
+	# If you have an ftp proxy firewall (not an http firewall)
 	# then set this to the name of the firewall
 	ftp_firewall => undef,
 
diff --git a/lib/Net/Config.pm b/lib/Net/Config.pm
index 5a262fd0f8..23db846629 100644
--- a/lib/Net/Config.pm
+++ b/lib/Net/Config.pm
@@ -169,7 +169,7 @@ Your internet domain name
 
 =item ftp_firewall
 
-If you have an FTP proxy firewall (B<NOT> a HTTP or SOCKS firewall)
+If you have an FTP proxy firewall (B<NOT> an HTTP or SOCKS firewall)
 then this value should be set to the firewall hostname. If your firewall
 does not listen to port 21, then this value should be set to
 C<"hostname:port"> (eg C<"hostname:99">)
diff --git a/lib/Net/FTP.pm b/lib/Net/FTP.pm
index 531ff405bb..ffa21e16af 100644
--- a/lib/Net/FTP.pm
+++ b/lib/Net/FTP.pm
@@ -1247,17 +1247,17 @@ this if you really know what you're doing).
 =item new (HOST [,OPTIONS])
 
 This is the constructor for a new Net::FTP object. C<HOST> is the
-name of the remote host to which a FTP connection is required.
+name of the remote host to which an FTP connection is required.
 
 C<OPTIONS> are passed in a hash like fashion, using key and value pairs.
 Possible options are:
 
-B<Firewall> - The name of a machine which acts as a FTP firewall. This can be
+B<Firewall> - The name of a machine which acts as an FTP firewall. This can be
 overridden by an environment variable C<FTP_FIREWALL>. If specified, and the
 given host cannot be directly connected to, then the
 connection is made to the firewall machine and the string C<@hostname> is
 appended to the login identifier. This kind of setup is also refered to
-as a ftp proxy.
+as an ftp proxy.
 
 B<FirewallType> - The type of firewall running on the machine indicated by
 B<Firewall>. This can be overridden by an environment variable
@@ -1394,7 +1394,7 @@ a scalar context, returns a reference to a list.
 =item get ( REMOTE_FILE [, LOCAL_FILE [, WHERE]] )
 
 Get C<REMOTE_FILE> from the server and store locally. C<LOCAL_FILE> may be
-a filename or a filehandle. If not specified the the file will be stored in
+a filename or a filehandle. If not specified, the file will be stored in
 the current directory with the same leafname as the remote file.
 
 If C<WHERE> is given then the first C<WHERE> bytes of the file will
@@ -1476,7 +1476,7 @@ reference to a C<Net::FTP::dataconn> based object.
 
 =item nlst ( [ DIR ] )
 
-Send a C<NLST> command to the server, with an optional parameter.
+Send an C<NLST> command to the server, with an optional parameter.
 
 =item list ( [ DIR ] )
 
@@ -1517,7 +1517,7 @@ C<put_unique> and those that do not require data connections.
 =item port ( [ PORT ] )
 
 Send a C<PORT> command to the server. If C<PORT> is specified then it is sent
-to the server. If not the a listen socket is created and the correct information
+to the server. If not, the a listen socket is created and the correct information
 sent to the server.
 
 =item pasv ()
@@ -1593,7 +1593,7 @@ be performed using these.
 
 Read C<SIZE> bytes of data from the server and place it into C<BUFFER>, also
 performing any <CRLF> translation necessary. C<TIMEOUT> is optional, if not
-given the the timeout value from the command connection will be used.
+given, the timeout value from the command connection will be used.
 
 Returns the number of bytes read before any <CRLF> translation.
 
@@ -1601,7 +1601,7 @@ Returns the number of bytes read before any <CRLF> translation.
 
 Write C<SIZE> bytes of data from C<BUFFER> to the server, also
 performing any <CRLF> translation necessary. C<TIMEOUT> is optional, if not
-given the the timeout value from the command connection will be used.
+given, the timeout value from the command connection will be used.
 
 Returns the number of bytes written before any <CRLF> translation.
 
diff --git a/lib/Net/NNTP.pm b/lib/Net/NNTP.pm
index 56c97b3caf..53df6e01ea 100644
--- a/lib/Net/NNTP.pm
+++ b/lib/Net/NNTP.pm
@@ -1016,7 +1016,7 @@ the beginning of the test string just inside the open square
 bracket.
 
 The final operation uses the backslash character to
-invalidate the special meaning of the a open square bracket C<[>,
+invalidate the special meaning of an open square bracket C<[>,
 the asterisk, backslash or the question mark. Two backslashes in
 sequence will result in the evaluation of the backslash as a
 character with no special meaning.
diff --git a/lib/Net/POP3.pm b/lib/Net/POP3.pm
index fb919164ad..f23157ccca 100644
--- a/lib/Net/POP3.pm
+++ b/lib/Net/POP3.pm
@@ -417,7 +417,7 @@ Send the PASS command. Returns the number of messages in the mailbox.
 
 =item login ( [ USER [, PASS ]] )
 
-Send both the the USER and PASS commands. If C<PASS> is not given the
+Send both the USER and PASS commands. If C<PASS> is not given the
 C<Net::POP3> uses C<Net::Netrc> to lookup the password using the host
 and username. If the username is not specified then the current user name
 will be used.
diff --git a/lib/Net/README.libnet b/lib/Net/README.libnet
index 59001acff1..fd115a21ba 100644
--- a/lib/Net/README.libnet
+++ b/lib/Net/README.libnet
@@ -55,7 +55,7 @@ CONFIGURE
 
 Normally when perl Makefile.PL is run it will run Configure which will
 ask some questions about your system. The results of these questions
-will be stored in in a file called libnet.cfg which will be installed
+will be stored in a file called libnet.cfg which will be installed
 alongside the other perl modules in this distribution. The Makefile.PL
 will run Configure in an interactive mode unless these exists a file
 called libnet.cfg in the build directory.
diff --git a/lib/Net/SMTP.pm b/lib/Net/SMTP.pm
index f2647b7ed8..ce5777db07 100644
--- a/lib/Net/SMTP.pm
+++ b/lib/Net/SMTP.pm
@@ -444,7 +444,7 @@ known as mailhost:
 =item new Net::SMTP [ HOST, ] [ OPTIONS ]
 
 This is the constructor for a new Net::SMTP object. C<HOST> is the
-name of the remote host to which a SMTP connection is required.
+name of the remote host to which an SMTP connection is required.
 
 If C<HOST> is not given, then the C<SMTP_Host> specified in C<Net::Config>
 will be used.
diff --git a/lib/Net/libnetFAQ.pod b/lib/Net/libnetFAQ.pod
index 4e2152aa76..1216ff7202 100644
--- a/lib/Net/libnetFAQ.pod
+++ b/lib/Net/libnetFAQ.pod
@@ -6,8 +6,8 @@ libnetFAQ - libnet Frequently Asked Questions
 
 =head2 Where to get this document
 
-This document is distributed with the libnet disribution, and is also
-avaliable on the libnet web page at
+This document is distributed with the libnet distribution, and is also
+available on the libnet web page at
 
     http://www.pobox.com/~gbarr/libnet/
 
@@ -20,7 +20,7 @@ gbarr@pobox.com.
 
 Copyright (c) 1997-1998 Graham Barr. All rights reserved.
 This document is free; you can redistribute it and/or modify it
-under the terms of the Artistic Licence.
+under the terms of the Artistic License.
 
 =head2 Disclaimer
 
@@ -35,7 +35,7 @@ in respect of this information or its use.
 =head2 What is libnet ?
 
 libnet is a collection of perl5 modules which all related to network
-programming. The majority of the modules avaliable provided the
+programming. The majority of the modules available provided the
 client side of popular server-client protocols that are used in
 the internet community.
 
@@ -55,7 +55,7 @@ these modules.
 
 =head2 What machines support libnet ?
 
-libnet itself is an entirly perl-code distribution so it should work
+libnet itself is an entirely perl-code distribution so it should work
 on any machine that perl runs on. However IO may not work
 with some machines and earlier releases of perl. But this
 should not be the case with perl version 5.004 or later.
@@ -67,14 +67,14 @@ in
 
  http://www.cpan.org/modules/by-module/Net/
 
-The latest release and information is also avaliable on the libnet web page
+The latest release and information is also available on the libnet web page
 at
 
  http://www.pobox.com/~gbarr/libnet/
 
 =head1 Using Net::FTP
 
-=head2 How do I download files from a FTP server ?
+=head2 How do I download files from an FTP server ?
 
 An example taken from an article posted to comp.lang.perl.misc
 
@@ -135,9 +135,9 @@ But this is not guaranteed to work.
 
 =head2 Can I do a reget operation like the ftp command ?
 
-=head2 How do I get a directory listing from a FTP server ?
+=head2 How do I get a directory listing from an FTP server ?
 
-=head2 Changeing directory to "" does not fail ?
+=head2 Changing directory to "" does not fail ?
 
 Passing an argument of "" to ->cwd() has the same affect of calling ->cwd()
 without any arguments. Turn on Debug (I<See below>) and you will see what is
@@ -155,19 +155,19 @@ gives
 =head2 I am behind a SOCKS firewall, but the Firewall option does not work ?
 
 The Firewall option is only for support of one type of firewall. The type
-supported is a ftp proxy.
+supported is an ftp proxy.
 
 To use Net::FTP, or any other module in the libnet distribution,
 through a SOCKS firewall you must create a socks-ified perl executable
 by compiling perl with the socks library.
 
-=head2 I am behind a FTP proxy firewall, but cannot access machines outside ?
+=head2 I am behind an FTP proxy firewall, but cannot access machines outside ?
 
-Net::FTP implements the most popular ftp proxy firewall approach. The sceme
-implemented is that where you loginin to the firewall with C<user@hostname>
+Net::FTP implements the most popular ftp proxy firewall approach. The scheme
+implemented is that where you log in to the firewall with C<user@hostname>
 
 I have heard of one other type of firewall which requires a login to the
-firewall with an accont, then a second login with C<user@hostname>. You can
+firewall with an account, then a second login with C<user@hostname>. You can
 still use Net::FTP to traverse these firewalls, but a more manual approach
 must be taken, eg
 
@@ -178,7 +178,7 @@ must be taken, eg
 =head2 My ftp proxy firewall does not listen on port 21
 
 FTP servers usually listen on the same port number, port 21, as any other
-FTP server. But there is no reason why thi has to be the case.
+FTP server. But there is no reason why this has to be the case.
 
 If you pass a port number to Net::FTP then it assumes this is the port
 number of the final destination. By default Net::FTP will always try
@@ -201,7 +201,7 @@ chmod command via the C<SITE> command. This can be done with
 =head2 I have seen scripts call a method message, but cannot find it documented ?
 
 Net::FTP, like several other packages in libnet, inherits from Net::Cmd, so
-all the methods described in Net::Cmd are also avaliable on Net::FTP
+all the methods described in Net::Cmd are also available on Net::FTP
 objects.
 
 =head2 Why does Net::FTP not implement mput and mget methods
@@ -241,14 +241,14 @@ of this protocol.
 
 =head2 The verify method always returns true ?
 
-Well it may seem thay way, but it does not. The verify method returns true
-if the command suceeded. If you pass verify an address which the
-server would normally have to forward to another machine the the command
-will suceed with something like
+Well it may seem that way, but it does not. The verify method returns true
+if the command succeeded. If you pass verify an address which the
+server would normally have to forward to another machine, the command
+will succeed with something like
 
     252 Couldn't verify <someone@there> but will attempt delivery anyway
 
-This command will only fail if you pass it an address in a domain the
+This command will fail only if you pass it an address in a domain
 the server directly delivers for, and that address does not exist.
 
 =head1 Debugging scripts
@@ -259,7 +259,7 @@ Most of the libnet client classes allow options to be passed to the
 constructor, in most cases one option is called C<Debug>. Passing
 this option with a non-zero value will turn on a protocol trace, which
 will be sent to STDERR. This trace can be useful to see what commands
-are being sent to the remote server and what responces are being
+are being sent to the remote server and what responses are being
 received back.
 
     #!/your/path/to/perl
@@ -287,14 +287,14 @@ this script would output something like
  Net::FTP=GLOB(0x8152974)>>> QUIT
  Net::FTP=GLOB(0x8152974)<<< 221 Goodbye.
 
-The first few lines tell you the modules that Net::FTP uses and thier versions,
-this is usefule data to me when a user reports a bug. The last seven lines
+The first few lines tell you the modules that Net::FTP uses and their versions,
+this is useful data to me when a user reports a bug. The last seven lines
 show the communication with the server. Each line has three parts. The first
 part is the object itself, this is useful for separating the output
-if you are using mutiple objects. The second part is either C<<<<<> to
+if you are using multiple objects. The second part is either C<<<<<> to
 show data coming from the server or C<&gt&gt&gt&gt> to show data
 going to the server. The remainder of the line is the command
-being sent or responce being received.
+being sent or response being received.
 
 =head1 AUTHOR AND COPYRIGHT