X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=gitmo%2FMooseX-Types.git;a=blobdiff_plain;f=lib%2FMooseX%2FTypes.pm;fp=lib%2FMooseX%2FTypes.pm;h=62a7054d9a369d062850a5e9ae803b696f85ec16;hp=544d0e376bf6f2ed8c67cb020e546b7d25c5bcb2;hb=8bf27efd5d9f5df49e2977fc04a6abd4ea8a5aca;hpb=6bb4c4a19f35ed428a362de1fc14d00ce0c0c96d

diff --git a/lib/MooseX/Types.pm b/lib/MooseX/Types.pm
index 544d0e3..62a7054 100644
--- a/lib/MooseX/Types.pm
+++ b/lib/MooseX/Types.pm
@@ -18,6 +18,8 @@ use namespace::autoclean;
 use 5.008;
 my $UndefMsg = q{Action for type '%s' not yet defined in library '%s'};
 
+=pod
+
 =head1 SYNOPSIS
 
 =head2 Library Definition
@@ -119,7 +121,7 @@ my $UndefMsg = q{Action for type '%s' not yet defined in library '%s'};
 
 The type system provided by Moose effectively makes all of its builtin type
 global, as are any types you declare with Moose. This means that every module
-that declares a type named "PositiveInt" is sharing the same type object. This
+that declares a type named C<PositiveInt> is sharing the same type object. This
 can be a problem when different parts of the code base want to use the same
 name for different things.
 
@@ -424,7 +426,7 @@ sub type_export_generator {
 
 =head2 create_arged_type_constraint ($name, @args)
 
-Given a String $name with @args find the matching typeconstraint and parameterize
+Given a String $name with @args find the matching type constraint and parameterize
 it with @args.
 
 =cut
@@ -532,7 +534,7 @@ Due to this stringification, the following will NOT work as you might think:
 
   subtype StrOrArrayRef => as Str | ArrayRef;
 
-The 'StrOrArrayRef' will have its stringification activated this causes the
+The C<StrOrArrayRef> type will have its stringification activated -- this causes the
 subtype to not be created.  Since the bareword type constraints are not strings
 you really should not try to treat them that way.  You will have to use the ','
 operator instead.  The authors of this package realize that all the L<Moose>
@@ -564,7 +566,7 @@ targets. For example if you do:
   package Foo;
   use TypeAndSubExporter qw(MyStr);
 
-You'll get a '"MyStr" is not exported by the TypeAndSubExporter module' error.
+You'll get a C<< "MyStr" is not exported by the TypeAndSubExporter module >> error.
 It can be worked around by:
 
   - use Sub::Exporter -setup => { exports => [ qw(something) ] };