Fix pod header levels

On the next release this will fix the funky TOC display for the sqitch.org pages for these docs.
sqitchers · Mar 25, 2024 · 5522821 · 5522821
1 parent 8ee14fb
commit 5522821
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 2 deletions.
diff --git a/Changes b/Changes
@@ -1,6 +1,8 @@
 Revision history for Perl extension App::Sqitch
 
 1.4.2
+     - Fix improperly nested Pod headers that were incrementing two levels
+       relative to their parent headers.
 
 1.4.1  2024-02-04T16:35:32Z
      - Removed the quoting of the role and warehouse identifiers that was

diff --git a/lib/sqitch-configuration.pod b/lib/sqitch-configuration.pod
@@ -462,7 +462,7 @@ Want them all? Just query the targets and pass each in turn:
 The commands that accept a target name are identical to those that take
 an engine name or target URI, as described in L</Database Interactions>.
 
-=head3 Different Target, Different Plan
+=head2 Different Target, Different Plan
 
 What about a project that manages different -- but related -- schemas on the
 same engine? For example, say you have two plans for PostgreSQL, one for a

diff --git a/lib/sqitch-revert.pod b/lib/sqitch-revert.pod
@@ -25,7 +25,7 @@ The C<< <database> >> parameter specifies the database to which to connect,
 and may also be specified as the C<--target> option. It can be target name,
 a URI, an engine name, or plan file path.
 
-=head3 Attention Git Users
+=head2 Attention Git Users
 
 If you're a git user thinking this is like C<git revert>, it's not.
 C<sqitch revert> is more like time travel. It takes your database back to the