Fix a couple of real spelling errors, change a couple of spellings to en_US, as the...

diff --git a/lib/Catalyst/Delta.pod b/lib/Catalyst/Delta.pod
index 020d0e1..856b18e 100755 (executable)
--- a/lib/Catalyst/Delta.pod
+++ b/lib/Catalyst/Delta.pod
@@ -1,4 +1,4 @@
-=head1 Deltachanges from 5.7 to 5.8
+=head1 Delta changes from 5.7 to 5.8
 
 This is an overview of the user visible changes in 5.8.
 
@@ -78,7 +78,7 @@ L<IO::Handle>.
 
 Added code method as an alias for C<< $res->status >>
 
-=head2 Consequences of the Moose backend
+=head2 Consequences of the Moose back end
 
 =over
 
@@ -103,7 +103,7 @@ decouples action creation from attributes.
 
 There is a reasonable API in Catalyst::Controller for working with
 and registering actions, allowing a controller sub-class to replace
-subroutine attributes for action declerations with an alternate
+subroutine attributes for action declarations with an alternate
 syntax.
 
 =item *
@@ -124,7 +124,7 @@ Your application class is forced to become immutable at the end of compilation.
 
 =item *
 
-Don't ignore SIGCHLD while handling requests with the dev server, so that
+Don't ignore SIGCHLD while handling requests with the development server, so that
 system() and other ways of creating child processes work as expected.
 
 =item *

diff --git a/lib/Catalyst/Upgrading.pod b/lib/Catalyst/Upgrading.pod
index 8a99930..b19d5c0 100644 (file)
--- a/lib/Catalyst/Upgrading.pod
+++ b/lib/Catalyst/Upgrading.pod
@@ -57,7 +57,7 @@ Moose components which say:
 to use the constructor provided by Moose, whilst working (if you do some hacks
 with the C< BUILDARGS > method), will not work with Catalyst 5.80 as
 C<Catalyst::Component> inherits from C<Moose::Object>, and so C< @ISA > fails
-to linearise.
+to linearize.
 
 The fix for this is to not inherit directly from C<Moose::Object>
 yourself. Having components which do not inherit their constructor from
@@ -132,7 +132,7 @@ to use L<Sub::Name> to name the subroutine. Example:
     *$full_method_name = subname $full_method_name, sub { ... };
 
 Additionally, you can take advantage of Catalysts use of L<Class::MOP> and
-install the closure using the appropriate metaclass. Example:
+install the closure using the appropriate meta class. Example:
 
     use Class::MOP;
     my $metaclass = Moose::Meta::Class->initialize($package_name);
@@ -140,7 +140,7 @@ install the closure using the appropriate metaclass. Example:
 
 =head2 Hooking into application setup
 
-To execute code during application startup the following snippet in MyApp.pm
+To execute code during application start-up the following snippet in MyApp.pm
 used to work:
 
     sub setup {
@@ -300,7 +300,7 @@ to B<any> of the packages defined within that component.
 
 =head2 $c->plugin method
 
-Calling the plugin method is deprecated, and calling it at runtime is B<highly
+Calling the plugin method is deprecated, and calling it at run time is B<highly
 deprecated>.
 
 Instead you are recommended to use L< Catalyst::Model::Adaptor > or similar to