Description: Fix spellings in POD
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=104639
 (not current version)
Author: Christopher Hoskin <christopher.hoskin@gmail.com>
Reviewed-by: gregor herrmann <gregoa@debian.org>
Last-Update: 2019-11-16

--- a/lib/Thread/Pool.pm
+++ b/lib/Thread/Pool.pm
@@ -1310,7 +1310,7 @@
 
 When a worker is told to finish, the "post" routine is executed if available.
 
-Results of jobs must be obtained seperately, unless a "stream" or a "monitor"
+Results of jobs must be obtained separately, unless a "stream" or a "monitor"
 routine is specified.  Then the result of each job will be streamed to the
 "stream" or "monitor" routine in the order in which the jobs were submitted.
 
@@ -1375,7 +1375,7 @@
 
 The "optimize" field specifies which implementation of the belt will be
 selected.  Currently there are two choices: 'cpu' and 'memory'.  By default,
-the "memory" optimization will be selected if no specific optmization is
+the "memory" optimization will be selected if no specific optimization is
 specified.
 
 You can call the class method L<optimize> to change the default optimization.
@@ -1461,7 +1461,7 @@
 
 The "post" field specifies the subroutine to be executed B<each> time a worker
 thread is B<removed> (either when being specifically L<remove>d, or when the
-pool is L<shutdown> specifically or implicitely when the Thread::Pool object
+pool is L<shutdown> specifically or implicitly when the Thread::Pool object
 is destroyed.  It must be specified as either the name of a subroutine or as
 a reference to a (anonymous) subroutine.
 
@@ -1572,7 +1572,7 @@
 
  checkpoint => sub {print "anonymous sub to do checkpointing\n"},
 
-The "checkpoint" field specifies the subroutine to be executed everytime a
+The "checkpoint" field specifies the subroutine to be executed every time a
 checkpoint should be made by a monitoring routine (e.g. for saving or updating
 status).  It must be specified as either the name of a subroutine or as a
 reference to a (anonymous) subroutine.
@@ -1674,7 +1674,7 @@
  $optimize = Thread::Pool->optimize;
 
 The "optimize" class method allows you to specify the default optimization
-type that will be used if no "optimize" field has been explicitely specified
+type that will be used if no "optimize" field has been explicitly specified
 with a call to L<new>.  It returns the current default type of optimization.
 
 Currently two types of optimization can be selected:
@@ -1684,7 +1684,7 @@
 =item memory
 
 Attempt to use as little memory as possible.  Currently, this is achieved by
-starting a seperate thread which hosts an unshared array.  This uses the
+starting a separate thread which hosts an unshared array.  This uses the
 "Thread::Conveyor::Thread" sub-class.
 
 =item cpu
@@ -1916,7 +1916,7 @@
 
 The "shutdown" method call the "join" method after removing all the active
 worker threads.  You therefore seldom need to call the "join" method
-seperately.
+separately.
 
 =head2 removed