Added a description of Presentation Model to Manual/Terminology.pod

[maypole.git] / lib / Maypole.pm

diff --git a/lib/Maypole.pm b/lib/Maypole.pm
index b5de0c51ad4fb11ee52960f9e158dfbc9cc632fd..8fead4d2a16ffad298370e5c63130eb05ec6753f 100644 (file)
--- a/lib/Maypole.pm
+++ b/lib/Maypole.pm
@@ -76,8 +76,8 @@ application. This is the C<BeerDB> package used as an example in the manual.
 
 This needs to first use L<Maypole::Application> which will make your package
 inherit from the appropriate platform driver such as C<Apache::MVC> or
-C<CGI::Maypole>. Then, the driver calls C<setup>.  This sets up the model classes and
-configures your application. The default model class for Maypole uses
+C<CGI::Maypole>. Then, the driver calls C<setup>. This sets up the model classes
+and configures your application. The default model class for Maypole uses
 L<Class::DBI> to map a database to classes, but this can be changed by altering
 configuration (B<before> calling setup.)
 
@@ -210,7 +210,7 @@ __PACKAGE__->init_done(0);
 
 As a framework, Maypole provides a number of B<hooks> - methods that are
 intended to be overridden. Some of these methods come with useful default
-behaviour, others do nothing by default. Likely hooks include:
+behaviour, others do nothing by default. Hooks include:
 
     Class methods
     -------------
@@ -757,6 +757,7 @@ sub call_exception
     return $self->exception($error);
 }
 
+
 =item exception
 
 This method is called if any exceptions are raised during the authentication or
@@ -818,11 +819,11 @@ sub parse_path
     $self->$_(undef) for qw/action table args/;
     
     $self->preprocess_path;
-
     $self->path || $self->path('frontpage');
-    
+
     my @pi = grep {length} split '/', $self->path;
-    
+
+
     $self->table  || $self->table(shift @pi);
     $self->action || $self->action( shift @pi or 'index' );
     $self->args   || $self->args(\@pi);