X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FTutorial%2FAuthentication.pod;fp=lib%2FCatalyst%2FManual%2FTutorial%2FAuthentication.pod;h=5a87d9d90d612c1098944e40a6519e2f24cc1c51;hb=6395438e94034711cd5cb5f7646f868f045b1776;hp=b330fd70aec9185601f22a8e1f7b381d1fbe71f2;hpb=eb60cd8eed4bac9d15899706924c5c84fb07eab2;p=catagits%2FCatalyst-Runtime.git

diff --git a/lib/Catalyst/Manual/Tutorial/Authentication.pod b/lib/Catalyst/Manual/Tutorial/Authentication.pod
index b330fd7..5a87d9d 100644
--- a/lib/Catalyst/Manual/Tutorial/Authentication.pod
+++ b/lib/Catalyst/Manual/Tutorial/Authentication.pod
@@ -806,7 +806,8 @@ is cleared (unless reset).  Although C<flash> has nothing to do with
 authentication, it does leverage the same session plugins.  Now that
 those plugins are enabled, let's go back and improve the "delete
 and redirect with query parameters" code seen at the end of the
-C<BasicCRUD> part of the tutorial.
+L<Basic CRUD|Catalyst::Manual::Tutorial::BasicCRUD> part of the 
+tutorial.
 
 First, open C<lib/MyApp/Controller/Books.pm> and modify C<sub delete>
 to match the following:
@@ -831,8 +832,8 @@ to match the following:
         $c->response->redirect($c->uri_for('/books/list'));
     }
 
-Next, open C<root/lib/site/layout> update the TT code to pull from flash
-vs. the C<status_msg> query parameter:
+Next, open C<root/lib/site/layout> and update the TT code to pull from 
+flash vs. the C<status_msg> query parameter:
 
     <div id="header">[% PROCESS site/header %]</div>
     
@@ -849,12 +850,12 @@ vs. the C<status_msg> query parameter:
 
 Restart the development server and point your browser to 
 L<http://localhost:3000/books/url_create/Test/1/4> to create an extra
-book.  Click the "Return to list" link and delete this "Test" book.  
-The C<flash> mechanism should retain our "Book deleted" status message
-across the redirect.
+book.  Click the "Return to list" link and delete this "Test" book you
+just added.  The C<flash> mechanism should retain our "Book deleted" 
+status message across the redirect.
 
 B<NOTE:> While C<flash> will save information across multiple requests,
-it does get cleared the first time it is read.  In general, this is
+I<it does get cleared the first time it is read>.  In general, this is
 exactly what you want -- the C<flash> message will get displayed on
 the next screen where it's appropriate, but it won't "keep showing up"
 after that first time (unless you reset it).  Please refer to