From: Shawn M Moore <sartak@gmail.com>
Date: Tue, 8 Apr 2008 12:08:38 +0000 (+0000)
Subject: Moose's class type constraints aren't limited to Moose-based objects
X-Git-Tag: 0_55~240
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=76c9c428695400c8fc0fa957f0e7dfdda3319604;p=gitmo%2FMoose.git

Moose's class type constraints aren't limited to Moose-based objects
---

diff --git a/lib/Moose/Cookbook/Recipe2.pod b/lib/Moose/Cookbook/Recipe2.pod
index e52c4c0..dc4b5dc 100644
--- a/lib/Moose/Cookbook/Recipe2.pod
+++ b/lib/Moose/Cookbook/Recipe2.pod
@@ -86,8 +86,8 @@ Up until now, we have only had C<Int> type constraints, which
 (as I said in the first recipe) is a builtin type constraint 
 that Moose provides for you. The C<BankAccount> type constraint 
 is new, and was actually defined the moment we created the 
-B<BankAccount> class itself. In fact, for every Moose class that 
-you define, a corresponding type constraint will be created. This
+B<BankAccount> class itself. In fact, for every class in 
+your program, a corresponding type constraint will be created. This
 means that in the first recipe, both C<Point> and C<Point3D> type
 constraints were created, and in this recipe, both C<BankAccount>
 and C<CheckingAccount> type constraints were created. Moose does