Release commit for 5.9013

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

diff --git a/lib/Catalyst/Manual/About.pod b/lib/Catalyst/Manual/About.pod
index d3dc0d6..1072ddf 100644 (file)
--- a/lib/Catalyst/Manual/About.pod
+++ b/lib/Catalyst/Manual/About.pod
@@ -185,7 +185,7 @@ L<AxKit>, which is designed for use with XML running under mod_perl;
 L<Maypole>--upon which Catalyst was originally based--designed for the
 easy development of powerful web databases; L<Jifty>, which does a great
 deal of automation in helping to set up web sites with many complex
-features; and Ruby on Rails (see L<http://www.rubyonrails.org>), written
+features; and Ruby on Rails (see L<https://rubyonrails.org>), written
 of course in Ruby and among the most popular web development systems. It
 is not the purpose of this document to criticize or even briefly
 evaluate these other frameworks; they may be useful for you and if so we
@@ -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.