Moose::Cookbook::Recipe5:

* fixed a few whitespace-only lines.

diff --git a/lib/Moose/Cookbook/Recipe5.pod b/lib/Moose/Cookbook/Recipe5.pod
index 7f1c468..d8b8382 100644 (file)
--- 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.