Permalink
Browse files

Fix some bad POD links

  • Loading branch information...
1 parent a554d11 commit d3df9108597d6d3896980228b417fec9dc92c7f7 @autarch autarch committed Apr 3, 2013
Showing with 3 additions and 3 deletions.
  1. +1 −1 lib/DateTime/Format/Builder.pm
  2. +2 −2 lib/DateTime/Format/Builder/Parser.pm
@@ -679,7 +679,7 @@ present. I lied. There are actually three of them.
B<parsers> takes a hashref of methods and their parser
specifications. See the
-L<tutorial above|/"CREATING A CLASS"> for details.
+L<DateTime::Format::Builder::Tutorial> for details.
Note that if you define a subroutine of the same name as one
of the methods you define here, an error will be thrown.
@@ -114,7 +114,7 @@ my @callbacks = qw( on_match on_fail postprocess preprocess );
These parameters appear for all parser implementations.
These are primarily documented in
-L<the main docs|DateTime::Format::Builder/"SINGLE SPECIFICATIONS">.
+L<DateTime::Format::Builder>.
=over 4
@@ -261,7 +261,7 @@ returned (it is assumed to be appropriate).
The single specification (if not a coderef) can be either a
hashref or a hash. The keys and values must be as per the
-L<specification|/"SINGLE SPECIFICATIONS">.
+specification.
It is here that any arrays of callbacks are unified. It is
also here that any parser implementations are used. With

0 comments on commit d3df910

Please sign in to comment.