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

--- a/lib/Thread/Conveyor/Monitored.pm
+++ b/lib/Thread/Conveyor/Monitored.pm
@@ -625,7 +625,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 (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.
@@ -656,7 +656,7 @@
 The "optimize" field specifies which implementation of the belt will be
 selected if there is no existing belt specified with the 'belt' field.
 Currently there are two choices: 'cpu' and 'memory'.  By default, the
-"memory" optimization will be selected if no specific optmization is specified.
+"memory" optimization will be selected if no specific optimization is specified.
 
 You can call the class method L<optimize> to change the default optimization.
 
@@ -723,7 +723,7 @@
  $optimize = Thread::Conveyor::Monitored->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:
@@ -733,7 +733,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