X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FTutorial%2FTesting.pod;fp=lib%2FCatalyst%2FManual%2FTutorial%2FTesting.pod;h=03061f8a31ca867a1d4bc789a73f4603c2f78e89;hp=25acec4152e03b48c9e147e9b371fcf92694ff00;hb=4b4d38842b2383a70a54bcadb493505950b469dd;hpb=636ba9f78f6ce788549fbfa7f1a1507d0579e978

diff --git a/lib/Catalyst/Manual/Tutorial/Testing.pod b/lib/Catalyst/Manual/Tutorial/Testing.pod
index 25acec4..03061f8 100644
--- a/lib/Catalyst/Manual/Tutorial/Testing.pod
+++ b/lib/Catalyst/Manual/Tutorial/Testing.pod
@@ -1,11 +1,11 @@
 =head1 NAME
 
-Catalyst::Manual::Tutorial::Testing - Catalyst Tutorial - Part 8: Testing
+Catalyst::Manual::Tutorial::Testing - Catalyst Tutorial - Chapter 8: Testing
 
 
 =head1 OVERVIEW
 
-This is B<Part 8 of 10> for the Catalyst tutorial.
+This is B<Chapter 8 of 10> for the Catalyst tutorial.
 
 L<Tutorial Overview|Catalyst::Manual::Tutorial>
 
@@ -56,12 +56,12 @@ L<Appendices|Catalyst::Manual::Tutorial::Appendices>
 
 =head1 DESCRIPTION
 
-You may have noticed that the Catalyst Helper scripts automatically
-create basic C<.t> test scripts under the C<t> directory.  This part of
-the tutorial briefly looks at how these tests can be used to not only
-ensure that your application is working correctly at the present time,
-but also provide automated regression testing as you upgrade various
-pieces of your application over time.
+You may have noticed that the Catalyst Helper scripts automatically 
+create basic C<.t> test scripts under the C<t> directory.  This 
+chapter of the tutorial briefly looks at how these tests can be used 
+to not only ensure that your application is working correctly at the 
+present time, but also provide automated regression testing as you 
+upgrade various pieces of your application over time.
 
 You can checkout the source code for this example from the catalyst
 subversion repository as per the instructions in
@@ -289,10 +289,10 @@ or
 
     $ DBIC_TRACE=0 CATALYST_DEBUG=0 prove --lib lib -v t/live_app01.t
 
-Experiment with the C<DBIC_TRACE>, C<CATALYST_DEBUG>
-and C<-v> settings.  If you find that there are errors, use the
-techniques discussed in the "Catalyst Debugging" section (Part 7) to
-isolate and fix any problems.
+Experiment with the C<DBIC_TRACE>, C<CATALYST_DEBUG> and C<-v> 
+settings.  If you find that there are errors, use the techniques 
+discussed in the "Catalyst Debugging" section (Chapter 7) to isolate 
+and fix any problems.
 
 If you want to run the test case under the Perl interactive debugger,
 try a command such as: