Bug #99956 for Constant-Export-Lazy: [PATCH] Pod and typo fixes

See attachment.

diff -rup Constant-Export-Lazy-0.08-dr6wPt-orig/lib/Constant/Export/Lazy.pm Constant-Export-Lazy-0.08-dr6wPt/lib/Constant/Export/Lazy.pm --- Constant-Export-Lazy-0.08-dr6wPt-orig/lib/Constant/Export/Lazy.pm 2014-08-29 03:57:43.000000000 -0700 +++ Constant-Export-Lazy-0.08-dr6wPt/lib/Constant/Export/Lazy.pm 2014-11-01 09:36:34.000000000 -0700 @@ -401,7 +401,7 @@ Constant::Export::Lazy - Utility to writ =head1 SYNOPSIS -These increasing verbose example of a C<My::Constants> package that +This increasingly verbose example of a C<My::Constants> package that you can write using C<Constant::Export::Lazy> demonstrates most of our major features (from F<t/lib/My/Constants.pm> in the source distro): @@ -782,7 +782,7 @@ without having to port them all over to the same time. This allows you to do so incrementally. For convenience we also support calling these foreign subroutines with -C<<$ctx->call($name)>>. This is handy because when migrating an +C<< $ctx->call($name) >>. This is handy because when migrating an existing package you can already start calling existing constants with our interface, and then when you migrate those constants over you won't have to change any of the old code. @@ -811,11 +811,11 @@ subroutine to override this constant, an and just call L</call> to fleshen it. You can also get the value of L</call> by doing -C<<$ctx->call($name)>>. We have some magic around override ensuring +C<< $ctx->call($name) >>. We have some magic around override ensuring that we only B<get> the value, we don't actually intern it in the symbol table. -This means that calling C<<$ctx->call($name)>> multiple times in the +This means that calling C<< $ctx->call($name) >> multiple times in the scope of an override subroutine is the only way to get C<Constant::Export::Lazy> to call a L</call> subroutine multiple times. We otherwise guarantee that these subs are only called once (as @@ -847,8 +847,8 @@ use. This is a reference that you can provide for your own use, we don't care what's in it. It'll be accessible via the L<context object|Constant::Export::Lazy/"CONTEXT OBJECT">'s C<stash> method -(i.e. C<<<my $stash = $ctx->stash> for L</call>, C</override> and -C</after> calls relevant to its scope, i.e. global if you define it +(i.e. C<< my $stash = $ctx->stash >>) for L</call>, L</override> and +L</after> calls relevant to its scope, i.e. global if you define it globally, otherwise local if it's defined locally. =head3 private_name_munger