Doc: add subheadings to CG "Regtests"

diff --git a/Documentation/contributor/regressions.itexi b/Documentation/contributor/regressions.itexi
index e8df94609d5f05f7e471b8aa6051bd85f4b407f5..a6106cea939e862f2df923c32b7211422694731e 100644 (file)
--- a/Documentation/contributor/regressions.itexi
+++ b/Documentation/contributor/regressions.itexi
@@ -38,6 +38,15 @@ of different versions to see when bugs appeared.
 
 @TODO: To be checked and completed -vv
 
 
 @TODO: To be checked and completed -vv
 

+Regression tests (@qq{regtests}) are available in two ways: either
+in a compiled form, for instance on the website, or as source code
+that needs to be compiled locally, using the most recent LilyPond
+binary as possible.  The latter is recommended, although more
+technically involved.
+
+
+@subheading Precompiled regtests
+

 The easiest way to see the @q{current} regtest output (meaning,
 the ouput of the latest stable or development version) is
 to look at the precompiled regtest
 The easiest way to see the @q{current} regtest output (meaning,
 the ouput of the latest stable or development version) is
 to look at the precompiled regtest


@@ -51,6 +60,9 @@ features, bugfixes... or new bugs that may have been introduced!
 Therefore, if you have an appropriate environment to build LilyPond
 yourself, it is recommended that you compile the software yourself.
 
 Therefore, if you have an appropriate environment to build LilyPond
 yourself, it is recommended that you compile the software yourself.
 

+
+@subheading Compiling regtests
+

 The first step is to download the latest available source code,
 as explained in @ref{Working with source code}.  Then you will need
 to build the LilyPond binary@footnote{Uninstalling the previous
 The first step is to download the latest available source code,
 as explained in @ref{Working with source code}.  Then you will need
 to build the LilyPond binary@footnote{Uninstalling the previous