X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FMoose%2FCookbook%2FRecipe5.pod;h=f0bac8ac692ca96f36a8b85c8c528de7508b70fc;hb=1344fd47a7ef94f27fb6535ce07a5c910716e326;hp=7f1c4682bea4534032f0ae8e0b452db6762a755e;hpb=6aa9f38562f133aff6d25854805572f2e7690898;p=gitmo%2FMoose.git

diff --git a/lib/Moose/Cookbook/Recipe5.pod b/lib/Moose/Cookbook/Recipe5.pod
index 7f1c468..f0bac8a 100644
--- a/lib/Moose/Cookbook/Recipe5.pod
+++ b/lib/Moose/Cookbook/Recipe5.pod
@@ -162,7 +162,7 @@ and pass it to the B<URI> constructor along with the default
 
 And of course, our coercions do nothing unless they are told to, 
 like so:
-                                                  
+
   has 'base' => (is => 'rw', isa => 'Uri', coerce => 1);
   has 'uri'  => (is => 'rw', isa => 'Uri', coerce => 1);
 
@@ -170,7 +170,7 @@ As you can see, re-using the coercion allows us to enforce a
 consistent and very flexible API across multiple accessors.
 
 =head1 CONCLUSION
-    
+
 This recipe illustrated the power of coercions to build a more 
 flexible and open API for your accessors, while still retaining 
 all the safety that comes from using Moose's type constraints. 
@@ -188,7 +188,7 @@ Stevan Little E<lt>stevan@iinteractive.comE<gt>
 
 =head1 COPYRIGHT AND LICENSE
 
-Copyright 2006, 2007 by Infinity Interactive, Inc.
+Copyright 2006-2008 by Infinity Interactive, Inc.
 
 L<http://www.iinteractive.com>