X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FAbout.pod;h=1072ddf75289c5a62acb9701874d7a29d80347dd;hb=a18ada2a7c8fc02b6bbd5d2155a41b5a9b0d3662;hp=d3dc0d61c423b60bce755ece059349a3b9b83d28;hpb=bbddff000787154dd9130f45634da8ef06529d86;p=catagits%2FCatalyst-Manual.git diff --git a/lib/Catalyst/Manual/About.pod b/lib/Catalyst/Manual/About.pod index d3dc0d6..1072ddf 100644 --- a/lib/Catalyst/Manual/About.pod +++ b/lib/Catalyst/Manual/About.pod @@ -185,7 +185,7 @@ L, which is designed for use with XML running under mod_perl; L--upon which Catalyst was originally based--designed for the easy development of powerful web databases; L, which does a great deal of automation in helping to set up web sites with many complex -features; and Ruby on Rails (see L), written +features; and Ruby on Rails (see L), 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 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.