fixed documentation referring to deprecated Catalyst::Base

[catagits/Catalyst-Manual.git] / lib / Catalyst / Manual / Intro.pod

diff --git a/lib/Catalyst/Manual/Intro.pod b/lib/Catalyst/Manual/Intro.pod
index b63d051..70ac4e1 100644 (file)
--- a/lib/Catalyst/Manual/Intro.pod
+++ b/lib/Catalyst/Manual/Intro.pod
@@ -216,14 +216,15 @@ means that this decision is entirely up to you, the programmer;
 Catalyst doesn't enforce anything. See L<Catalyst::Manual::About> for
 a general discussion of these issues.
 
-All components must inherit from L<Catalyst::Base>, which provides a
-simple class structure and some common class methods like C<config> and
-C<new> (constructor).
+Model, View and Controller components must inherit from L<Catalyst::Model>,
+L<Catalyst::View> and L<Catalyst::Model>, respectively. These, in turn, inherit
+from L<Catalyst::Component> which provides a simple class structure and some
+common class methods like C<config> and C<new> (constructor).
 
     package MyApp::Controller::Catalog;
 
     use strict;
-    use base 'Catalyst::Base';
+    use base 'Catalyst::Controller';
 
     __PACKAGE__->config( foo => 'bar' );
 
@@ -330,7 +331,7 @@ But first, we need a database.
 
     INSERT INTO foo (data) VALUES ('TEST!');
 
-    % sqlite /tmp/myapp.db < myapp.sql
+    % sqlite3 /tmp/myapp.db < myapp.sql
 
 Now we can create a DBIC::Schema model for this database.
 
@@ -1164,8 +1165,8 @@ IRC:
 
 Mailing lists:
 
-    http://lists.rawmode.org/mailman/listinfo/catalyst
-    http://lists.rawmode.org/mailman/listinfo/catalyst-dev
+    http://lists.scsys.co.uk/mailman/listinfo/catalyst
+    http://lists.scsys.co.uk/mailman/listinfo/catalyst-dev
 
 =head1 AUTHOR