Merge pull request #25 from dsteinbrunner/patch-1

typo fixes, thanks to dsteinbrunner.

lib/CGI.pm

@@ -171,7 +171,7 @@ $DefaultClass = 'CGI' unless defined $CGI::DefaultClass;
 $AutoloadClass = $DefaultClass unless defined $CGI::AutoloadClass;
 
 # The path separator is a slash, backslash or semicolon, depending
-# on the paltform.
+# on the platform.
 $SL = {
      UNIX    => '/',  OS2 => '\\', EPOC      => '/', CYGWIN => '/', NETWARE => '/',
      WINDOWS => '\\', DOS => '\\', MACINTOSH => ':', VMS    => '/'
@@ -4320,7 +4320,7 @@ submissions, file uploads, reading and writing cookies, query string generation
 and manipulation, and processing and preparing HTTP headers. Some HTML
 generation utilities are included as well.
 
-CGI.pm performs very well in in a vanilla CGI.pm environment and also comes
+CGI.pm performs very well in a vanilla CGI.pm environment and also comes
 with built-in support for mod_perl and mod_perl2 as well as FastCGI.
 
 It has the benefit of having developed and refined over 10 years with input

lib/CGI/Carp.pm

@@ -191,13 +191,13 @@ when a C<die()> is done inside an C<eval> body or expression.
 Even though the
 fatalsToBrower support takes precautions to avoid this,
 you still may get the error message printed to STDOUT.
-This may have some undesireable effects when the purpose of doing the
+This may have some undesirable effects when the purpose of doing the
 eval is to determine which of several algorithms is to be used.
 
 By setting C<$CGI::Carp::TO_BROWSER> to 0 you can suppress printing
 the C<die> messages but without all of the complexity of using
 C<set_die_handler>.  You can localize this effect to inside C<eval>
-bodies if this is desireable: For example:
+bodies if this is desirable: For example:
 
  eval {
    local $CGI::Carp::TO_BROWSER = 0;

lib/CGI/Pretty.pm

@@ -168,7 +168,7 @@ sub initialize_globals {
     # This is the string used for indentation of tags
     $CGI::Pretty::INDENT = "\t";
 
-    # This is the string used for seperation between tags
+    # This is the string used for separation between tags
     $CGI::Pretty::LINEBREAK = $/;
 
     # These tags are not prettify'd.

lib/CGI/Util.pm

@@ -210,7 +210,7 @@ sub unescape {
 # Byte strings were traditionally used directly as a sequence of octets.
 # This worked if they actually represented binary data (i.e. in CGI::Compress).
 # This also worked if these byte strings were actually utf-8 encoded; e.g.,
-# when the source file used utf-8 without the apropriate "use utf8;".
+# when the source file used utf-8 without the appropriate "use utf8;".
 # This fails if the byte string is actually a Latin 1 encoded string, but it
 # was always so and cannot be fixed without breaking the binary data case.
 # -- Stepan Kasal <skasal@redhat.com>