X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=blobdiff_plain;f=dgit-sponsorship.7.pod;h=3b8c3a8b3ad54a42e09a0150bae9f22be921052a;hp=67d064767eb200e5f25c87a12a96c8f7c50d890c;hb=256b64652ad59ecf74a75fb3337e39dfec8773f4;hpb=7b057ccd4fca9ada5be78a3a92513f7734d51aff

diff --git a/dgit-sponsorship.7.pod b/dgit-sponsorship.7.pod
index 67d06476..3b8c3a8b 100644
--- a/dgit-sponsorship.7.pod
+++ b/dgit-sponsorship.7.pod
@@ -59,7 +59,7 @@ options to dgit, or
 C<dgit --gbp> or C<dgit --dpm>,
 you must specify that in your handoff email - see below.
 
-=head1 GIT+ORIGS BASED HANDOFF
+=head2 git+origs based handoff
 
 The elements of the handoff consists of:
 
@@ -92,7 +92,9 @@ the elements above should be a in a single, signed, message.
 This could be an RFS submission
 against the sponsorship-requests pseudo-package.
 
-=head2 git branch
+=head3 git branch
+
+=over 4
 
 The sponsee should push their HEAD as a git branch
 to any suitable git server.
@@ -108,7 +110,11 @@ Instead, the sponsee should include the
 git commit id of their HEAD
 in their handover email.
 
-=head2 orig tarballs
+=back
+
+=head3 orig tarballs
+
+=over 4
 
 If there are any .origs that are not in the archive already,
 the sponsor will need them as part of the upload.
@@ -134,7 +140,11 @@ if they are small.
 The sponsee should quote sha256sums of the .origs in their
 handoff email.
 
-=head2 quilt options
+=back
+
+=head3 quilt options
+
+=over 4
 
 Some workflows involve git branches which are not natively
 dgit-compatible.