Merge pull request #16 from dsteinbrunner/patch-1

typo fixes

lib/POE.pm

@@ -197,8 +197,8 @@ POE components are often just plain Perl objects.  The previously
 mentioned L<POE::Component::DirWatch::Object|POE::Component::DirWatch::Object> uses L<Moose|Moose>.  Other object
 and meta-object frameworks are compatible.
 
-Also of interest is L<POE::Component::Generic|POE::Component::Generic>, which is allows you to create
-a POE component from nearly nearly any blocking module.
+Also of interest is L<POE::Component::Generic|POE::Component::Generic>, which allows you to create
+a POE component from nearly any blocking module.
 
 There are quite a lot of components on the CPAN.  
 L<http://search.cpan.org/search?query=poe+component&mode=all>

lib/POE/Component/Client/TCP.pm

@@ -439,7 +439,7 @@ inline_states parameter.
 
 =head4 ObjectStates
 
-If C<ObjectStates> is specified, it must holde an arrayref of objects
+If C<ObjectStates> is specified, it must hold an arrayref of objects
 and the events they will handle.  The arrayref must follow the syntax
 for POE::Session->create()'s object_states parameter.
 

lib/POE/Component/Server/TCP.pm

@@ -483,7 +483,7 @@ sub new {
       # We accepted a connection.  Do something with it.
       tcp_server_got_connection => $accept_callback,
 
-      # conncurrency on close.
+      # concurrency on close.
       disconnected => sub {
         $_[HEAP]->{connections}--;
         DEBUG and warn(
@@ -983,8 +983,7 @@ parameters as discussed there.
 
 A default error handler will be provided if Error is omitted.  The
 default handler will log the error to STDERR and shut down the server.
-Active connections will be permitted to to complete their
-transactions.
+Active connections will be permitted to complete their transactions.
 
   Error => sub {
     my ($syscall_name, $err_num, $err_str) = @_[ARG0..ARG2];
@@ -1076,7 +1075,7 @@ session's _stop handler.
 =head4 ListenerArgs
 
 C<ListenerArgs> is passed to the listener session as the C<args> parameter.  In
-other words, it must be an arrayref, and the values are are passed into the
+other words, it must be an arrayref, and the values are passed into the
 C<Started> handler as ARG0, ARG1, etc.
 
 =head3 Connection Session Configuration

lib/POE/Filter/HTTPD.pm

@@ -20,7 +20,7 @@ $VERSION = '1.356';
 sub BUFFER        () { 0 } # raw data buffer to build requests
 sub STATE         () { 1 } # built a full request
 sub REQUEST       () { 2 } # partial request being built
-sub CLIENT_PROTO  () { 3 } # client protoco version requested
+sub CLIENT_PROTO  () { 3 } # client protocol version requested
 sub CONTENT_LEN   () { 4 } # expected content length
 sub CONTENT_ADDED () { 5 } # amount of content added to request
 

lib/POE/Kernel.pm

@@ -1730,7 +1730,7 @@ sub call {
 
   # TODO The difference between synchronous and asynchronous events
   # should be made more clear in the documentation, so that people
-  # have a tendency not to abuse them.  I discovered in xws that that
+  # have a tendency not to abuse them.  I discovered in xws that
   # mixing the two types makes it harder than necessary to write
   # deterministic programs, but the difficulty can be ameliorated if
   # programmers set some base rules and stick to them.

lib/POE/Loop.pm

@@ -517,7 +517,7 @@ versions.
 =head3 loop_resume_filehandle FILE_HANDLE, IO_MODE
 
 This is a lightweight form of loop_watch_filehandle().  It is used
-along with loop_pause_filehandle() to temporarily toggle a a watcher's
+along with loop_pause_filehandle() to temporarily toggle a watcher's
 state for a FILE_HANDLE in a particular IO_MODE.
 
 =head1 HOW POE FINDS EVENT LOOP BRIDGES

lib/POE/Loop/IO_Poll.pm

@@ -30,7 +30,7 @@ sub skip_tests {
 use strict;
 
 # Be sure we're using a contemporary version of IO::Poll.  There were
-# issues with certain versios of IO::Poll prior to 0.05.  The latest
+# issues with certain versions of IO::Poll prior to 0.05.  The latest
 # version is 0.01, however.
 use IO::Poll 0.01;
 

lib/POE/Resource.pm

@@ -64,7 +64,7 @@ L<POE::Resource::SIDs>,
 L<POE::Resource::Sessions>,
 L<POE::Resource::Signals>
 
-Also see L<POE::Kernel/Resources> for for public information about POE
+Also see L<POE::Kernel/Resources> for public information about POE
 resources.
 
 =head1 BUGS

lib/POE/Resource/Aliases.pm

@@ -155,7 +155,7 @@ POE::Kernel, so it has no public interface.
 See L<POE::Kernel/Session Identifiers (IDs and Aliases)> for the
 public alias API.
 
-See L<POE::Kernel/Resources> for for public information about POE
+See L<POE::Kernel/Resources> for public information about POE
 resources.
 
 See L<POE::Resource> for general discussion about resources and the

lib/POE/Resource/Clock.pm

@@ -316,15 +316,15 @@ features to keep an internal monotonic clock and a wall clock.  It also
 converts between this monotonic clock and the wall clock.
 
 The monotonic clock is used to keep an ordered queue of events.  The wall
-clock is used to comunicate the time with user code
+clock is used to communicate the time with user code
 (L<POE::Kernel/alarm_set>, L<POE::Kernel/alarm_remove>).
 
 There are 3 possible clock sources in order of preference:
 L<POSIX::RT::Clock>, L<Time::HiRes> and L<perlfunc/time>.  Only
-C<POSIX::RT::Clock> has a seperate monotonic and wall clock; the other two use the
+C<POSIX::RT::Clock> has a separate monotonic and wall clock; the other two use the
 same source for both clocks.
 
-Clock selection and behaviour is controled with the following:
+Clock selection and behaviour is controlled with the following:
 
 =head2 USE_POSIXRT
 
@@ -366,15 +366,15 @@ the following two alarms is undefined.
 
     export POE_USE_EXACT_EPOCH=1
         or
-    sub POE::Kernel::USE_EACT_EPOCH { 1 }
+    sub POE::Kernel::USE_EXACT_EPOCH { 1 }
 
 There currently no way to exactly get the monotonic clock's epoch.  Instead
 the difference between the current monotonic clock value to the realtime
 clock's value is used.  This is obviously inexact because there is a slight
 delay between the 2 system calls.  Setting USE_EXACT_EPOCH to true will
 calculate an average of this difference over 250 ms or at least 20 samples. 
 What's more, the system calls are done in both orders (monotonic then
-realtime, realtime then monotonic) to try and get a more eact value.
+realtime, realtime then monotonic) to try and get a more exact value.
 
 Defaults to false.  Only relevant if L</USE_STATIC_EPOCH> is true.
 

lib/POE/Resource/Events.pm

@@ -401,7 +401,7 @@ internally by POE::Kernel, so it has no public interface.
 See L<POE::Kernel/Asynchronous Messages (FIFO Events)> for one public
 events API.
 
-See L<POE::Kernel/Resources> for for public information about POE
+See L<POE::Kernel/Resources> for public information about POE
 resources.
 
 See L<POE::Resource> for general discussion about resources and the

lib/POE/Resource/Extrefs.pm

@@ -195,7 +195,7 @@ by POE::Kernel, so it has no public interface.
 See L<POE::Kernel/Public Reference Counters> for the public extref
 API.
 
-See L<POE::Kernel/Resources> for for public information about POE
+See L<POE::Kernel/Resources> for public information about POE
 resources.
 
 See L<POE::Resource> for general discussion about resources and the

lib/POE/Resource/FileHandles.pm

@@ -743,7 +743,7 @@ internally by POE::Kernel, so it has no public interface.
 See L<POE::Kernel/I/O Watchers (Selects)> for the public file watcher
 API.
 
-See L<POE::Kernel/Resources> for for public information about POE
+See L<POE::Kernel/Resources> for public information about POE
 resources.
 
 See L<POE::Resource> for general discussion about resources and the

lib/POE/Resource/SIDs.pm

@@ -100,7 +100,7 @@ by POE::Kernel, so it has no public interface.
 See L<POE::Kernel/Session Identifiers (IDs and Aliases)> for more
 information about session IDs.
 
-See L<POE::Kernel/Resources> for for public information about POE
+See L<POE::Kernel/Resources> for public information about POE
 resources.
 
 See L<POE::Resource> for general discussion about resources and the

lib/POE/Resource/Sessions.pm

@@ -632,7 +632,7 @@ come and go.
 See L<POE::Kernel/Session Helper Methods> for friend methods between
 POE::Kernel and POE::Session classes.
 
-See L<POE::Kernel/Resources> for for public information about POE
+See L<POE::Kernel/Resources> for public information about POE
 resources.
 
 See L<POE::Resource> for general discussion about resources and the

lib/POE/Resource/Signals.pm

@@ -1050,7 +1050,7 @@ handling.
 See L<POE::Kernel/Signal Watcher Methods> for POE's public signals
 API.
 
-See L<POE::Kernel/Resources> for for public information about POE
+See L<POE::Kernel/Resources> for public information about POE
 resources.
 
 See L<POE::Resource> for general discussion about resources and the

lib/POE/Resources.pm

@@ -69,7 +69,7 @@ load() falls back to C<POE::Resource::...>.
 
 =head1 SEE ALSO
 
-See L<POE::Kernel/Resources> for for public information about POE
+See L<POE::Kernel/Resources> for public information about POE
 resources.
 
 See L<POE::Resource> for general discussion about resources and the

lib/POE/Session.pm

@@ -1018,7 +1018,7 @@ C<$_[SENDER]> is commonly used as a return address for responses.  It may
 also be compared against C<$_[KERNEL]> to verify that timers and other
 POE::Kernel-generated events were not spoofed.
 
-This C<echo_handler()> reponds to the sender with an "echo" event that
+This C<echo_handler()> responds to the sender with an "echo" event that
 contains all the parameters it received.  It avoids a feedback loop by
 ensuring the sender session and event (STATE) are not identical to the
 current ones.
@@ -1261,7 +1261,7 @@ resolve to a different subroutine.
 
 POE::Session sessions support a small number of options, which may be
 initially set with the C<option> constructor parameter and changed at
-run time with the C<option()|/option> mehtod.
+run time with the C<option()|/option> method.
 
 C<option> takes a hashref with option =E<gt> value pairs:
 

lib/POE/Wheel/Run.pm

@@ -498,7 +498,7 @@ sub new {
     # The child doesn't need to read from the semaphore pipe.
     $sem_pipe_read = undef;
 
-    # Run Perl code.  This is farily consistent across most systems.
+    # Run Perl code.  This is fairly consistent across most systems.
 
     if (ref($program) eq 'CODE') {