X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=lib%2FMaypole%2FManual%2FTerminology.pod;h=adc5dc85b64d017782b9db0d8d78d5d0d4739c0a;hb=1c8db728a3fb5adb4f0ea876ea1316457700edf8;hp=d7bf7f433e315a4d9f0827328df1e18438518517;hpb=f4a654d5fee1b79ced98bb6d71a4f3b4bf402ecd;p=maypole.git

diff --git a/lib/Maypole/Manual/Terminology.pod b/lib/Maypole/Manual/Terminology.pod
index d7bf7f4..adc5dc8 100644
--- a/lib/Maypole/Manual/Terminology.pod
+++ b/lib/Maypole/Manual/Terminology.pod
@@ -151,7 +151,7 @@ The functionality provided by the Maypole model class is more accurately
 described as a Presentation Model (see below). In complex Maypole applications,
 it is good practise to separate the domain model (the 'heart' of the
 application) into a separate class hierarchy (see
-L<Maypole::Manual::Inheritance).
+L<Maypole::Manual::Inheritance>).
 
 The distinction is relatively unimportant when using Maypole in 'default' mode - 
 i.e. using L<Maypole::Model::CDBI>, and allowing Maypole to autogenerate the 
@@ -179,6 +179,8 @@ point, the convenience of dropping new methods into the 'shared' classes will be
 outweighed by the heuristic advantage of separating different layers into
 separate class hierarchies.
 
+=back
+
 =head3 Presentation Model
 
 This pattern more accurately describes the role of the Maypole model.
@@ -196,8 +198,6 @@ queries the Presentation Model to retrieve these new values. In Maypole, this is
 the role of the C<vars()> method on L<Maypole::View::Base>, which transmits the
 new values to the templates.
 
-=back
-
 =head1 AUTHOR
 
 David Baird, C<< <cpan@riverside-cms.co.uk> >>