Added Success Story

[catagits/Catalyst-Runtime.git] / lib / Catalyst / Manual / Tutorial.pod

diff --git a/lib/Catalyst/Manual/Tutorial.pod b/lib/Catalyst/Manual/Tutorial.pod
index eb1af71..3fc66fe 100644 (file)
--- a/lib/Catalyst/Manual/Tutorial.pod
+++ b/lib/Catalyst/Manual/Tutorial.pod
@@ -195,9 +195,10 @@ this action registered the application will respond to all requests
 with the same message "Congratulations, My::App is on Catalyst!".
 
 As you see, the default action is defined as a Private action. 
-Most private actions are not directly available from a web url. The
-exceptions are the built-in actions, 'default','begin','end' and
-'auto'. The rest can only be reached by using C<forward>.
+Most private actions are not directly available from a web url. This
+also includes the built-in actions, 'default','begin','end' and
+'auto', although they will be called as part of some chains.  
+The rest can only be reached by using C<forward>.
 
 
 The call to the C<setup> method also triggers the second stage of 
@@ -250,14 +251,14 @@ script that Catalyst set up as part of the skeleton application:
 
     $ script/create.pl view TT TT
 
-this generates a view component named C<My::App::View::TT>, which you 
+this generates a view component named C<My::App::V::TT>, which you 
 might use by forwarding from your C<end> action:
 
     # In My::App or My::App::Controller::SomeController
 
     sub end : Private {
         my($self, $c) = @_;
-        $c->forward('My::App::View::TT');
+        $c->forward('My::App::V::TT');
     }
 
 The generated TT view component simply subclasses the