If the others are bolded, why not this one?

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

diff --git a/lib/Catalyst/Manual/About.pod b/lib/Catalyst/Manual/About.pod
index 805bf8d..5300e79 100644 (file)
--- a/lib/Catalyst/Manual/About.pod
+++ b/lib/Catalyst/Manual/About.pod
@@ -226,7 +226,7 @@ View. In Catalyst applications the View is usually a small module, just
 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.
@@ -303,15 +303,17 @@ others it's just a matter of personal preference (perhaps your template,
 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