From: James Lowe <james.lowe@datacore.com>
Date: Sat, 29 May 2010 14:27:02 +0000 (+0100)
Subject: Doc: Remove any '@' commands from @node sections
X-Git-Tag: release/2.13.23-1~29^2~6
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=c9358f9fadca7539ada68a8d9d6c3d0ffaf42037;p=lilypond.git

Doc: Remove any '@' commands from @node sections

Also edited an @ref{}
---

diff --git a/Documentation/contributor/regressions.itexi b/Documentation/contributor/regressions.itexi
index 25c106f2ea..178d3e4a4b 100644
--- a/Documentation/contributor/regressions.itexi
+++ b/Documentation/contributor/regressions.itexi
@@ -84,7 +84,7 @@ make test
 
 However, as there are many snippets to compile, if you have a multi-core
 machine it is highly recommended to use the @option{-j} option, as
-described in @ref{Saving time with the @option{-j} option}.  Another
+described in @ref{Saving time with the -j option}.  Another
 useful optimization is to set the @var{CPU_COUNT} variable; for a
 quad-core processor the complete command would look like
 
diff --git a/Documentation/included/compile.itexi b/Documentation/included/compile.itexi
index ea38bd7847..b3bfb7705f 100644
--- a/Documentation/included/compile.itexi
+++ b/Documentation/included/compile.itexi
@@ -12,7 +12,7 @@
 * Overview of compiling::
 * Requirements::
 * Getting the source code::
-* Configuring @command{make}::
+* Configuring make::
 * Compiling LilyPond::
 * Post-compilation options::
 * Problems::
@@ -276,17 +276,17 @@ download and install the free-software
 @uref{http://www.7-zip.org, 7zip archiver} to extract the tarball.
 
 
-@node Configuring @command{make}
+@node Configuring make
 @section Configuring @command{make}
 
 
 @menu
-* Running @command{./autogen.sh}::
-* Running @command{./configure}::
+* Running ./autogen.sh::
+* Running ./configure::
 @end menu
 
 
-@node Running @command{./autogen.sh}
+@node Running ./autogen.sh
 @subsection Running @command{./autogen.sh}
 
 After you unpack the tarball (or download the Git repository), the
@@ -311,7 +311,7 @@ configuration, such as @file{configure}, @file{README.txt}, etc.
 @end enumerate
 
 
-@node Running @command{./configure}
+@node Running ./configure
 @subsection Running @command{./configure}
 
 @menu
@@ -426,14 +426,14 @@ mkdir lily-build && cd lily-build
 
 
 @menu
-* Using @command{make}::
-* Saving time with the @option{-j} option::
+* Using make::
+* Saving time with the -j option::
 * Compiling for multiple platforms::
-* Useful @command{make} variables::
+* Useful make variables::
 @end menu
 
 
-@node Using @command{make}
+@node Using make
 @subsection Using @command{make}
 
 LilyPond is compiled with the @command{make} command.  Assuming
@@ -453,7 +453,7 @@ make help
 TODO: Describe what @command{make} actually does.
 
 
-@node Saving time with the @option{-j} option
+@node Saving time with the -j option
 @subsection Saving time with the @option{-j} option
 
 If your system has multiple CPUs, you can speed up compilation by
@@ -506,7 +506,7 @@ make conf=prof install
 @ref{Installing LilyPond from a local build}
 
 
-@node Useful @command{make} variables
+@node Useful make variables
 @subsection Useful @command{make} variables
 
 If a less verbose build output if desired, the variable
@@ -567,7 +567,7 @@ re-install.  See @ref{Configuring target directories}.
 @menu
 * Documentation editor's edit/compile cycle::
 * Building documentation::
-* Saving time with @code{CPU_COUNT}::
+* Saving time with CPU_COUNT::
 * AJAX search::
 * Installing documentation::
 * Building documentation without compiling::
@@ -683,7 +683,7 @@ indiscriminately---it is more efficient to @command{touch} only
 the affected files.
 
 
-@node Saving time with @code{CPU_COUNT}
+@node Saving time with CPU_COUNT
 @unnumberedsubsubsec Saving time with @code{CPU_COUNT}
 
 The most time consuming task for building the documentation is