Description: fix POD spelling
Origin: vendor
Author: gregor herrmann <gregoa@debian.org>
Last-Update: 2017-01-27
Forwarded: https://rt.cpan.org/Ticket/Display.html?id=120007
Bug: https://rt.cpan.org/Ticket/Display.html?id=120007

--- a/lib/HTTP/Server/Simple/CGI/PreFork.pm
+++ b/lib/HTTP/Server/Simple/CGI/PreFork.pm
@@ -402,7 +402,7 @@
 $myserver->run(prefork => 1):
 
 Per default, prefork is turned off (e.g. server runs singlethreaded). This
-is very usefull for debugging and backward compatibility.
+is very useful for debugging and backward compatibility.
 
 Beware when forking: Keep in mind how database and filehandles behave. Normally,
 you should set up everything before the run method (cache files, load confiugurations,...),
@@ -437,12 +437,12 @@
 
 =head2 handle_continue_header
 
-Overrideable function that allows to to custom-handle the "100 Continue" status codes. This function
+Overrideable function that allows one to custom-handle the "100 Continue" status codes. This function
 is called if the client sends a a "Expect: 100-continue" header. It defaults to sending a "100 Continue"
 status line and proceed with the rest of the request.
 
 If you want to override this, for example to check upload size or permissions, subclass this function. You
-will recieve the headers as a hash as the only input (nothing much else has been parsed from the client as of
+will receive the headers as a hash as the only input (nothing much else has been parsed from the client as of
 this moment in time).
 
 It is your job to send/print the appropriate status line header, either "100 Continue" or the appropriate error code.
@@ -469,7 +469,7 @@
 
 Older versions of HSSC::Prefork did not automatically require the IPv6 modules on installation.
 This behaviour has changed, starting at version 2.0. This is in accordance with with RFC6540, titled
-"IPv6 Support Required for All IP-Capable Nodes". If you don't have an IPv6 address, thats OK (or more
+"IPv6 Support Required for All IP-Capable Nodes". If you don't have an IPv6 address, that's OK (or more
 precisely *your* problem). But the software now assumes that your system is technicaly capable of handling 
 IPv6 connections, even if you don't have an IPv6 uplink at the moment.
 
