[Catalyst-commits] r6196 - trunk/Catalyst-Plugin-Session/lib/Catalyst/Plugin/Session

[islue at dev.catalyst.perl.org]

Author: islue
Date: 2007-03-24 19:40:30 +0000 (Sat, 24 Mar 2007)
New Revision: 6196

Modified:
   trunk/Catalyst-Plugin-Session/lib/Catalyst/Plugin/Session/Tutorial.pod
Log:
a typo and a link fixed

Modified: trunk/Catalyst-Plugin-Session/lib/Catalyst/Plugin/Session/Tutorial.pod
===================================================================
--- trunk/Catalyst-Plugin-Session/lib/Catalyst/Plugin/Session/Tutorial.pod	2007-03-24 16:58:54 UTC (rev 6195)
+++ trunk/Catalyst-Plugin-Session/lib/Catalyst/Plugin/Session/Tutorial.pod	2007-03-24 19:40:30 UTC (rev 6196)
@@ -35,7 +35,7 @@
 something the server asks the client to save somewhere, and resend every time a
 request is made.
 
-They way they work is that the server sends the C<Set-Cookie> header, with a
+The way they work is that the server sends the C<Set-Cookie> header, with a
 cookie name, a value, and some meta data (like when it expires, what paths it
 applies to, etc). The client saves this.
 
@@ -99,7 +99,7 @@
 This loads the session API, as well as the required backends of your choice.
 
 After the plugins are loaded they need to be configured. This is done according
-to L<Catalyst::Manual::Tutorial/Configuring>.
+to L<Catalyst::Manual::Cookbook/Configure_your_application>.
 
 Each backend plugin requires it's own configuration options (with most plugins
 providing sensible defaults). The session API itself also has configurable