Description: Fixes to the integrated POD documentation
 Without those fixes pod2man inserts a POD ERRORS section
 in the generated manual pages.
Author: Raphaël Hertzog <hertzog@debian.org>
Bug: https://rt.cpan.org/Public/Bug/Display.html?id=49853

--- a/Datum.pm
+++ b/Datum.pm
@@ -869,6 +869,8 @@ provides C<VERIFY>, a pre-condition that
 (i.e. never stripped by C<Carp::Datum::Strip>).  It can be used to protect
 the external interface of a module against abuse.
 
+=back
+
 =head2 Implementation
 
 With Carp::Datum, pre-conditions can be given using C<DREQUIRE> or C<VERIFY>.
@@ -885,8 +887,6 @@ Moreover, remember that a pre-condition 
 caller, whilst other assertion failures means a bug near the place of failure.
 If only for that, it's worth making the distinction.
 
-=back
-
 =head1 INTERFACE
 
 =head2 Control Flow
@@ -1103,8 +1103,6 @@ running. For instance, one can enforce a
 As an important note, the dynamic configuration is effective only when
 the global debug switch is turned on.
 
-=back
-
 =head1 LIMITATIONS
 
 It's not possible to insert tracing hooks like C<DFEATURE> or C<DVAL>
--- a/Datum/Cfg.pm
+++ b/Datum/Cfg.pm
@@ -602,6 +602,8 @@ Routine names are given by strings withi
 This would apply to all routines named "foo" or "bar", whatever their package,
 for instance C<main::foo> and C<x::bar>.
 
+=back
+
 =head2 Debugging and Tracing Flags
 
 Debugging (and tracing) flags can be specified only within syntactic I<BLOCK>
