X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FActions.pod;h=41247c8e2c80961a32dc6a82e67333e2e100d64e;hp=1952b2b195cf5cc4b7fd4b6803b56245b197325a;hb=97e6fe8948b1a35ced7fd86e92936e7d724e4b98;hpb=bbddff000787154dd9130f45634da8ef06529d86

diff --git a/lib/Catalyst/Manual/Actions.pod b/lib/Catalyst/Manual/Actions.pod
index 1952b2b..41247c8 100644
--- a/lib/Catalyst/Manual/Actions.pod
+++ b/lib/Catalyst/Manual/Actions.pod
@@ -5,16 +5,17 @@ Catalyst::Manual::Actions - Catalyst Reusable Actions
 =head1 DESCRIPTION
 
 This section of the manual describes the reusable action system in
-Catalyst, how they work, descriptions of some existing ones, and how to
-write your own.  Reusable actions are attributes on Catalyst methods
-that allow you to decorate your method with functions running before or
-after the method call.  This can be used to implement commonly used
-action patterns, while still leaving you full freedom to customize them.
+Catalyst, how such actions work, descriptions of some existing ones, and
+how to write your own.  Reusable actions are attributes on Catalyst
+methods that allow you to decorate your method with functions running
+before or after the method call.  This can be used to implement commonly
+used action patterns, while still leaving you full freedom to customize
+them.
 
 =head1 USING ACTIONS
 
-This is pretty simple. It works just like the normal dispatch attributes
-you are used to, like Local or Private:
+This is pretty simple. Actions work just like the normal dispatch
+attributes you are used to, like Local or Private:
 
   sub Hello :Local :ActionClass('SayBefore') { 
 	$c->res->output( 'Hello '.$c->stash->{what} );
@@ -22,10 +23,11 @@ you are used to, like Local or Private:
 
 In this example, we expect the SayBefore action to magically populate
 stash with something relevant before C<Hello> is run.  In the next
-section we'll show you how to implement it. If you want it in another
-namespace than Catalyst::Action you can prefix the action name with a
-'+', for instance '+Foo::SayBefore', or if you just want it under your
-application namespace instead, use MyAction, like MyAction('SayBefore').
+section we'll show you how to implement it. If you want it in a
+namespace other than Catalyst::Action you can prefix the action name
+with a '+', for instance '+Foo::SayBefore', or if you just want it under
+your application namespace instead, use MyAction, like
+MyAction('SayBefore').
 
 =head1 WRITING YOUR OWN ACTIONS
 
@@ -44,7 +46,7 @@ the Action class:
     $c->stash->{what} = 'world';
   };
 
-  after 'extecute' => sub {
+  after 'execute' => sub {
       my ( $self, $controller, $c, $test ) = @_;
       $c->stash->{foo} = 'bar';
   };
@@ -55,7 +57,8 @@ Pretty simple, huh?
 
 =head1 ACTION ROLES
 
-You can only have one action class per action, which can be somewhat inflexible.
+You can only have one action class per action, which can be somewhat
+inflexible.
 
 The solution to this is to use L<Catalyst::Controller::ActionRole>, which
 would make the example above look like this:
@@ -68,7 +71,7 @@ would make the example above look like this:
     $c->stash->{what} = 'world';
   };
 
-  after 'extecute' => sub {
+  after 'execute' => sub {
       my ( $self, $controller, $c, $test ) = @_;
       $c->stash->{foo} = 'bar';
   };