gluing some other module into Catalyst; the display logic is written
within the template itself.
-The Controller is Catalyst itself. When a request is made to Catalyst,
+The B<Controller> is Catalyst itself. When a request is made to Catalyst,
it will be received by one of your Controller modules; this module
will figure out what the user is trying to do, gather the necessary
data from a Model, and send it to a View for display.
then generate an HTML page, which Catalyst will send to the user's
browser, using whatever web server you've configured.
-How does this help you?
+=head3 How does this help you?
In many ways. Suppose you have a small catalog now, and you're using a
lightweight database such as SQLite, or maybe just a text file. But
rather than your Controller, is the better place to decide what to
display if you get an empty result). Catalyst just gives you the tools.
-=head1 AUTHOR
-
-Jesse Sheidlower, C<jester@panix.com>
-
=head1 SEE ALSO
L<Catalyst>, L<Catalyst::Manual::Intro>
+=head1 AUTHORS
+
+Catalyst Contributors, see Catalyst.pm
+
=head1 COPYRIGHT
-This program is free software, you can redistribute it and/or modify it
-under the same terms as Perl itself.
+This library is free software. You can redistribute it and/or modify it under
+the same terms as Perl itself.
+
+=cut