manual fixes.

diff --git a/ChangeLog b/ChangeLog
index 9f8e5606301fd711c5e660113718cfa80dc51933..f6a0bae4f553a5a1aaa9f7c090ebcaf716091e72 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,4 +1,12 @@
 2004-09-16  Heikki Junes  <hjunes@cc.hut.fi>
+
+        *  Documentation/user/notation.itely: Capitalize only first letter.
+
+        *  Documentation/user/programming-interface.itely: Capitalize Scheme.
+
+        *  Documentation/user/lilypond-book.itely: use @refbugs.
+ 
+        *  THANKS: sort.
  
          *  input/mutopia/F.Schubert/morgenlied.ly,
          input/mutopia/J.S.Bach/baerenreiter-sarabande.ly,

diff --git a/Documentation/user/lilypond-book.itely b/Documentation/user/lilypond-book.itely
index 9602841c59167438ae8f54893b4beb9cbd5d491c..5c549ddc5137ddbce02dda30fb89ec3c045cadd3 100644 (file)
--- a/Documentation/user/lilypond-book.itely
+++ b/Documentation/user/lilypond-book.itely
@@ -516,7 +516,7 @@ For La@TeX{} input, the file to give to La@TeX{} has extension
 
 
 
-@section Bugs
+@refbugs
 
 The Texinfo command @code{pagesize} is not interpreted. Almost all
 La@TeX{} commands that change margins and line widths are ignored.

diff --git a/Documentation/user/notation.itely b/Documentation/user/notation.itely
index 9a86a620fb8f09046784bce66d47f7e2e180c3a5..ef766dd7eea725393a56fa8abd68896fb767f859 100644 (file)
--- a/Documentation/user/notation.itely
+++ b/Documentation/user/notation.itely
@@ -7512,7 +7512,7 @@ accurately.  Use @code{<g a>8 <e a>8} instead.
 
 
 @node Special fermatas
-@subsection Special Fermatas
+@subsection Special fermatas
 
 @cindex fermatas, special
 

diff --git a/Documentation/user/programming-interface.itely b/Documentation/user/programming-interface.itely
index 057d52db6640bb1cf20a2ffd6c48abe1a73c4792..6a2dae83c2a44ee0a7776081e281f57d73391f19 100644 (file)
--- a/Documentation/user/programming-interface.itely
+++ b/Documentation/user/programming-interface.itely
@@ -225,7 +225,7 @@ The syntax for @code{\applymusic} is
 @end example
 
 @noindent
-This means that the scheme function @var{func} is called with
+This means that the Scheme function @var{func} is called with
 @var{music} as its argument.  The return value of @var{func} is the
 result of the entire expression.  @var{func} may read and write music
 properties using the functions @code{ly:music-property} and
@@ -309,10 +309,10 @@ exporting LilyPond input to other formats
 @node Using LilyPond syntax inside Scheme
 @subsection Using LilyPond syntax inside Scheme
 
-Creating music expressions in scheme can be tedious, as they are
-heavily nested and the resulting scheme code is large. For some
+Creating music expressions in Scheme can be tedious, as they are
+heavily nested and the resulting Scheme code is large. For some
 simple tasks, this can be avoided, using LilyPond usual syntax inside
-scheme, with the dedicated @code{#@{ ... #@}} syntax.
+Scheme, with the dedicated @code{#@{ ... #@}} syntax.
 
 The following two expressions give equivalent music expressions:
 @example
@@ -325,9 +325,9 @@ The following two expressions give equivalent music expressions:
 
 The content of @code{#@{ ... #@}} is enclosed in an implicit @code{@{
 ... @}} block, which is parsed. The resulting music expression, a
-@code{SequentialMusic} music object, is then returned and usable in scheme.
+@code{SequentialMusic} music object, is then returned and usable in Scheme.
 
-Arbitrary scheme forms, including variables, can be used in @code{#@{ ... #@}}
+Arbitrary Scheme forms, including variables, can be used in @code{#@{ ... #@}}
 expressions with the @code{$} character (@code{$$} can be used to
 produce a single $ character). This makes the creation of simple
 functions straightforward. In the following example, a function
@@ -414,13 +414,13 @@ and a list of properties and other arguments, produce a Stencil
 object.
 
 @menu
-* Markup construction in scheme::  
+* Markup construction in Scheme::  
 * How markups work internally ::  
 * Markup command definition::   
 @end menu
 
-@node Markup construction in scheme
-@subsection Markup construction in scheme
+@node Markup construction in Scheme
+@subsection Markup construction in Scheme
 
 @cindex defining markup commands 
 
@@ -440,7 +440,7 @@ is equivalent to:
 
 @noindent
 This example exposes the main translation rules between regular
-LilyPond markup syntax and scheme markup syntax, which are summed up
+LilyPond markup syntax and Scheme markup syntax, which are summed up
 is this table:
 @multitable @columnfractions .5 .5
 @item @b{LilyPond} @tab @b{Scheme}