From: Jess Robinson <cpan@desert-island.me.uk>
Date: Tue, 4 Sep 2007 22:04:18 +0000 (+0000)
Subject: Typos and doc additions
X-Git-Tag: 0_26~28
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=c2a69ef1a5adb302bcb6ca0a2623f75f195d348e;p=gitmo%2FMoose.git

Typos and doc additions
---

diff --git a/lib/Moose.pm b/lib/Moose.pm
index 7aa481d..18f2a91 100644
--- a/lib/Moose.pm
+++ b/lib/Moose.pm
@@ -403,7 +403,7 @@ type checking for this attribute. Moose will perform the checks during class
 construction, and within any accessors. The C<$type_name> argument must be a 
 string. The string may be either a class name or a type defined using 
 Moose's type definition features. (Refer to L<Moose::Util::TypeConstraints>
-for information on how to define a new type).
+for information on how to define a new type, and how to retrieve type meta-data).
 
 =item I<coerce =E<gt> (1|0)>
 
diff --git a/lib/Moose/Util/TypeConstraints.pm b/lib/Moose/Util/TypeConstraints.pm
index 223b83f..ef2d9d8 100644
--- a/lib/Moose/Util/TypeConstraints.pm
+++ b/lib/Moose/Util/TypeConstraints.pm
@@ -369,7 +369,7 @@ B<NOTE:> The C<ClassName> type constraint is simply a subtype
 of string which responds true to C<isa('UNIVERSAL')>. This means
 that your class B<must> be loaded for this type constraint to 
 pass. I know this is not ideal for all, but it is a saner 
-restriction then most others. 
+restriction than most others. 
 
 =head2 Use with Other Constraint Modules
 
@@ -413,8 +413,9 @@ test file.
 
 =item B<find_type_constraint ($type_name)>
 
-This function can be used to locate a specific type constraint 
-meta-object. What you do with it from there is up to you :)
+This function can be used to locate a specific type constraint
+meta-object, of the class L<Moose::Meta::TypeConstraint> or a
+derivative. What you do with it from there is up to you :)
 
 =item B<create_type_constraint_union (@type_constraint_names)>
 
@@ -506,7 +507,7 @@ are shallow) will not likely need to use this.
 =head2 Type Coercion Constructors
 
 Type constraints can also contain type coercions as well. If you 
-ask your accessor too coerce, the Moose will run the type-coercion 
+ask your accessor to coerce, then Moose will run the type-coercion 
 code first, followed by the type constraint check. This feature 
 should be used carefully as it is very powerful and could easily 
 take off a limb if you are not careful.