From: Ansgar Burchardt Date: Thu, 4 Feb 2010 13:25:28 +0000 (+0900) Subject: correct spelling errors X-Git-Tag: 0.21~1 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=gitmo%2FMooseX-Types-Structured.git;a=commitdiff_plain;h=67eec8f705f693670aba8d2810e30fcf59191f44 correct spelling errors Correct two spelling errors found by Debian's lintian QA tool. Signed-off-by: Ansgar Burchardt --- diff --git a/lib/MooseX/Meta/TypeConstraint/Structured.pm b/lib/MooseX/Meta/TypeConstraint/Structured.pm index 86f0e3c..a9aa0e5 100644 --- a/lib/MooseX/Meta/TypeConstraint/Structured.pm +++ b/lib/MooseX/Meta/TypeConstraint/Structured.pm @@ -267,7 +267,7 @@ sub is_subtype_of { =head2 type_constraints_equals -Checks to see if the internal type contraints are equal. +Checks to see if the internal type constraints are equal. =cut diff --git a/lib/MooseX/Types/Structured.pm b/lib/MooseX/Types/Structured.pm index 2303f17..31448c6 100644 --- a/lib/MooseX/Types/Structured.pm +++ b/lib/MooseX/Types/Structured.pm @@ -128,7 +128,7 @@ if you are not familiar with it. =head2 Comparing Parameterized types to Structured types Parameterized constraints are built into core Moose and you are probably already -familar with the type constraints 'HashRef' and 'ArrayRef'. Structured types +familiar with the type constraints 'HashRef' and 'ArrayRef'. Structured types have similar functionality, so their syntax is likewise similar. For example, you could define a parameterized constraint like: