X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FTutorial%2FCatalystBasics.pod;h=13209c0cd5f49f1b423661dc6c85ab9889827259;hp=be04af1f034b20e0daca3317537d547b42c2f779;hb=779cf508642c2883ea3b86ce46fe6db230069ef7;hpb=45c7830fc2a9167e08203368ca11d6d13628c5fb

diff --git a/lib/Catalyst/Manual/Tutorial/CatalystBasics.pod b/lib/Catalyst/Manual/Tutorial/CatalystBasics.pod
index be04af1..13209c0 100644
--- a/lib/Catalyst/Manual/Tutorial/CatalystBasics.pod
+++ b/lib/Catalyst/Manual/Tutorial/CatalystBasics.pod
@@ -255,8 +255,8 @@ objects. (See L<Catalyst|Catalyst>,
 L<Catalyst::Response|Catalyst::Response>, and 
 L<Catalyst::Request|Catalyst::Request>) 
 
-C<$c->response->body> sets the HTTP response (see 
-L<Catalyst::Response|Catalyst::Response>), while C<$c->welcome_message> 
+C<$c-E<gt>response-E<gt>body> sets the HTTP response (see 
+L<Catalyst::Response|Catalyst::Response>), while C<$c-E<gt>welcome_message> 
 is a special method that returns the welcome message that you saw in 
 your browser.
 
@@ -325,7 +325,7 @@ method that it inherits from the C<Catalyst::View::TT class>.
 
 Template Toolkit is a very full featured template facility, with 
 excellent documentation at 
-L<http://template-tookit.org/>, 
+L<http://template-toolkit.org/>, 
 but since this is not a TT tutorial, we'll stick to only basic TT 
 usage here (and explore some of the more common TT features in later 
 parts of the tutorial).
@@ -350,13 +350,13 @@ C<lib/Hello/Controller/Root.pm> to the following:
         $c->stash->{template} = 'hello.tt';
     }
 
-This time, instead of doing C<$c->response->body()>, you are setting 
+This time, instead of doing C<$c-E<gt>response->body()>, you are setting 
 the value of the "template" hash key in the Catalyst "stash", an area 
 for putting information to share with other parts of your application. 
 The "template" key determines which template will be displayed at the 
 end of the method. Catalyst controllers have a default "end" action 
 for all methods which causes the first (or default) view to be 
-rendered (unless there's a C<$c->response->body()> statement). So your 
+rendered (unless there's a C<$c-E<gt>response->body()> statement). So your 
 template will be magically displayed at the end of your method.
 
 After saving the file, restart the development server, and look at