From a48efc7deb4a85420310bbeb458d32d864591fe8 Mon Sep 17 00:00:00 2001 From: Jonathan Kulp Date: Fri, 27 Feb 2009 07:21:09 -0600 Subject: [PATCH] fixed sectioning --- Documentation/devel/compiling.itexi | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/Documentation/devel/compiling.itexi b/Documentation/devel/compiling.itexi index 05d2963e1e..49b69fa867 100644 --- a/Documentation/devel/compiling.itexi +++ b/Documentation/devel/compiling.itexi @@ -35,7 +35,7 @@ the @uref{Compiling-from-source.html,documentation in English}. @end menu @node Downloading source code -@subsection Downloading source code +@section Downloading source code Download source @@ -62,7 +62,7 @@ For information on packaging, see @uref{http://lilypond.org/devel}. @node Requirements -@subsection Requirements +@section Requirements @unnumberedsubsubsec Compilation @@ -160,7 +160,7 @@ and the patch from @node Building LilyPond -@subsection Building LilyPond +@section Building LilyPond @unnumberedsubsubsec Compiling @@ -227,7 +227,7 @@ line, or in @file{local.make} at top of the build tree. @node Building documentation -@subsection Building documentation +@section Building documentation This requires a successful compile of LilyPond, or using an external LilyPond binary. @@ -238,7 +238,7 @@ LilyPond binary. @end menu @node Commands for building documentation -@unnumberedsubsubsec Commands for building documentation +@unnumberedsubsec Commands for building documentation The documentation is built by issuing @@ -329,7 +329,7 @@ touch input/lsr/*.ly @node Building documentation without compiling LilyPond -@unnumberedsubsubsec Building documentation without compiling LilyPond +@unnumberedsubsec Building documentation without compiling LilyPond The documentation can be built locally without compiling LilyPond binary, if LilyPond is already installed on your system. @@ -378,7 +378,7 @@ exec /sw/bin/pngtopnm "$@" @node Testing LilyPond -@subsection Testing LilyPond +@section Testing LilyPond @html @@ -424,7 +424,7 @@ For checking the coverage of the test suite, do the following @node Problems -@subsection Problems +@section Problems For help and questions use @email{lilypond-user@@gnu.org}. Send bug reports to @email{bug-lilypond@@gnu.org}. -- 2.39.2