Merge pull request #155 from yoshikazusawa/fix-small-fix-typos

fix some minor typos

lib/Eval/TypeTiny.pm

@@ -492,7 +492,7 @@ Boolean indicating whether Eval::TypeTiny has support for lexical subs.
 
 Returns a string indicating what implementation of C<< alias => 1 >> is
 being used. Eval::TypeTiny will automatically choose the best implementation.
-This constant can be matched against the C<< IMPLEMENTAION_* >> constants.
+This constant can be matched against the C<< IMPLEMENTATION_* >> constants.
 
 =item C<< IMPLEMENTATION_NATIVE >>
 

lib/Type/Params.pm

@@ -578,7 +578,7 @@ You can think of C<add_numbers> above as a function which takes named
 parameters from the outside, but receives positional parameters on the
 inside.
 
-You can use an arrayref to specify the order the paramaters will be
+You can use an arrayref to specify the order the parameters will be
 returned in. (By default they are returned in the order they were defined
 in.)
 
@@ -679,7 +679,7 @@ Usually the default will be fine.
 
 =head4 C<< package >> B<Str>
 
-The package of the sub whose paramaters we're supposed to be checking.
+The package of the sub whose parameters we're supposed to be checking.
 As well as showing up in stack traces, it's used by C<dwim_type> if you
 provide any type constraints as strings.
 
@@ -689,7 +689,7 @@ provide it.
 
 =head4 C<< subname >> B<Str>
 
-The name of the sub whose paramaters we're supposed to be checking.
+The name of the sub whose parameters we're supposed to be checking.
 
 The default is probably fine, but if you're wrapping C<signature> so that
 you can check signatures on behalf of another package, you may need to

lib/Type/Tiny/ConstrainedObject.pm

@@ -130,7 +130,7 @@ __END__
 
 =head1 NAME
 
-Type::Tiny::ConstrainedObject - shared behavour for Type::Tiny::Class, etc
+Type::Tiny::ConstrainedObject - shared behaviour for Type::Tiny::Class, etc
 
 =head1 STATUS
 

lib/Type/Tiny/Manual/AllTypes.pod

@@ -352,7 +352,7 @@ A string.
 
 B<< StrictNum >> in L<Types::Standard>
 
-A number; strict constaint.
+A number; strict constraint.
 
 =item *
 

lib/Type/Tiny/Manual/UsingWithMoo3.pod

@@ -251,7 +251,7 @@ So if you imagine the functions exported by Types::Standard are like this:
   );
   # ... and more
 
-Then "+" exports a horizonal group of those, and "-" exports a vertical group.
+Then "+" exports a horizontal group of those, and "-" exports a vertical group.
 
 =head2 Exporting Parameterized Types
 

lib/Types/Common/String.pm

@@ -400,7 +400,7 @@ but C<< "Hello,45" >> will fail.
 The ws parameter allows optional whitespace surrounding the delimiters,
 as well as optional leading and trailing whitespace.
 
-The type, min, max, and ws paramaters are optional.
+The type, min, max, and ws parameters are optional.
 
 Parameterized B<DelimitedStr> type constraints will automatically have a
 coercion from B<< ArrayRef[`type] >> which uses C<< join >> to join by the

lib/Types/Standard.pm

@@ -1097,7 +1097,7 @@ $meta->add_coercion(
 			my ( $self, $target, $re ) = @_;
 			ref( $re ) eq q(Regexp)
 				or _croak(
-				"Parameter to Split[`a] expected to be a regular expresssion; got $re" );
+				"Parameter to Split[`a] expected to be a regular expression; got $re" );
 			my $regexp_string = "$re";
 			$regexp_string =~ s/\\\//\\\\\//g;    # toothpicks
 			return ( Str(), qq{ [split /$regexp_string/, \$_] } );
@@ -1790,7 +1790,7 @@ C<looks_like_number>.
 
 =item C<PERL_TYPE_TINY_XS>
 
-If set to false, can be used to suppress the loading of XS implementions of
+If set to false, can be used to suppress the loading of XS implementations of
 some type constraints.
 
 =item C<PERL_ONLY>

lib/Types/Standard/Dict.pm

@@ -99,7 +99,7 @@ sub __inline_generator {
 	# i.e. Any, Item, Defined, Ref, or HashRef
 	my $slurpy_is_any = $slurpy && $_hash->is_a_type_of( $slurpy );
 
-	# Is slurpy a parameterized Map, or expressable as a parameterized Map?
+	# Is slurpy a parameterized Map, or expressible as a parameterized Map?
 	my $slurpy_is_map =
 		$slurpy
 		&& $slurpy->is_parameterized

t/20-modules/Error-TypeTiny/basic.t

@@ -32,7 +32,7 @@ my $e1 = exception { 'Error::TypeTiny'->throw() };
 
 is($e1->message, 'An exception has occurred', '$e1->message (default)');
 is($e1->context->{package}, 'main', '$e1->context->{main}');
-is($e1->context->{line}, '31', '$e1->contex1t->{line}');
+is($e1->context->{line}, '31', '$e1->context->{line}');
 is($e1->context->{file}, 'basic.t', '$e1->context->{file}');
 
 my $e2 = exception { 'Error::TypeTiny'->throw(message => 'oh dear') };

t/20-modules/Types-Standard/mxtmlb-alike.t

@@ -19,7 +19,7 @@ L<MooX::Types::MooseLike::Base>.
 
 =back
 
-Rather than checking they work directy, we check they are equivalent to
+Rather than checking they work directly, we check they are equivalent to
 known (and well-tested) type constraints generated using L<Type::Utils>.
 
 =head1 AUTHOR

t/30-external/Moose/native-attribute-traits.t

@@ -4,7 +4,7 @@
 
 =head1 PURPOSE
 
-Check type constraints and coercions work with L<Moose> native attibute
+Check type constraints and coercions work with L<Moose> native attribute
 traits.
 
 =head1 DEPENDENCIES

t/lib/BiggerLib.pm

@@ -7,7 +7,7 @@
 Type library used in several test cases.
 
 Defines types C<SmallInteger>, C<BigInteger> and C<Distance>.
-Defines classes C<Foo::Bar> and C<Foo::Baz> along with correponding
+Defines classes C<Foo::Bar> and C<Foo::Baz> along with corresponding
 C<FooBar> and C<FooBaz> class type constraints; defines role C<Quux>
 and the C<DoesQuux> role type constraint.