Typos: Lilypond -> LilyPond, explicite -> explicit, fix docstring

Author: msp0

Documentation/es/user/lilypond-book.itely

@@ -318,7 +318,7 @@ salida de LilyPond.
 En @LaTeX{}, defina @code{\betweenLilyPondSystem} de tal forma que la
 la inclusión de otros sistemas se dé por terminada una vez que se ha
 alcanzado el número deseado de sistemas requeridos.  Puesto que
-@code{\betweenLilypondSystem} se llama en primer lugar @emph{después}
+@code{\betweenLilyPondSystem} se llama en primer lugar @emph{después}
 del primer sistema, incluir solamente el primer sistema es algo
 trivial.
 

Documentation/ja/user/lilypond-book.itely

@@ -317,7 +317,7 @@ output.
 
 In @LaTeX{}, define @code{\betweenLilyPondSystem} in such a way that
 inclusion of other systems is terminated once the required number of
-systems are included.  Since @code{\betweenLilypondSystem} is first
+systems are included.  Since @code{\betweenLilyPondSystem} is first
 called @emph{after} the first system, including only the first system
 is trivial.
 

Documentation/user/ancient.itely

@@ -1492,7 +1492,7 @@ shows the code fragment that produces this ligature, using
 @tab
 @b{Output}
 @tab
-@b{Lilypond@*
+@b{LilyPond@*
 code}
 
 @c TODO: \layout block is identical in all of the below examples.

Documentation/user/lilypond-book.itely

@@ -306,7 +306,7 @@ output.
 
 In @LaTeX{}, define @code{\betweenLilyPondSystem} in such a way that
 inclusion of other systems is terminated once the required number of
-systems are included.  Since @code{\betweenLilypondSystem} is first
+systems are included.  Since @code{\betweenLilyPondSystem} is first
 called @emph{after} the first system, including only the first system
 is trivial.
 

Documentation/user/lilypond.tely

@@ -157,7 +157,7 @@ of this and other documentation.
 * Specialist notation::            Notation which is only used for
     specific purposes.
 * General input and output::       General information about
-    lilypond input and output.
+    LilyPond input and output.
 * Spacing issues::                 Display of output on paper.
 * Changing defaults::              Tuning output.
 * Interfaces for programmers::     Expert usage.

Documentation/user/rhythms.itely

@@ -2644,7 +2644,7 @@ set directions.  Hence, when introducing layout tweaks to
 override the special settings, they should be placed inside
 the grace expression. The overrides should also be reverted
 inside the grace expression. Here, the grace note's default stem
-direction is overriden and then reverted.
+direction is overridden and then reverted.
 
 @lilypond[quote,verbatim,relative=2]
 \new Voice {

Documentation/user/text.itely

@@ -958,7 +958,7 @@ include external image files converted to the
 Encapsulated PostScript format (@emph{eps}), or
 to directly embed graphics into the input file,
 using native PostScript code.  In such a case, it
-may be useful to explicitely specify the size of the
+may be useful to explicitly specify the size of the
 drawing, as demonstrated below:
 
 @lilypond[quote,verbatim,relative=1]

Documentation/user/tweaks.itely

@@ -1808,7 +1808,7 @@ notes of a chord, as shown:
 @end lilypond
 
 @noindent
-but this may be overriden to manually force all or any of the
+but this may be overridden to manually force all or any of the
 individual fingering numbers above or below:
 
 @cindex fingering example

Documentation/user/vocal.itely

@@ -161,7 +161,7 @@ issue to consider when working with vocal music:
 song texts must be interpreted as text, not notes.  For example, the
 input@tie{}@code{d} should be interpreted as a one letter syllable,
 not the note@tie{}D.
-Therefore, a special lyric mode has to be used, either explicitely
+Therefore, a special lyric mode has to be used, either explicitly
 or using some abbreviated methods.
 
 Lyrics are entered in a special input mode, which can be introduced

elisp/lilypond-mode.el

@@ -32,7 +32,7 @@
   "File prefix for commands on buffer or region.")
 
 (defvar LilyPond-master-file nil
-  "Master file that Lilypond will be run on.")
+  "Master file that LilyPond will be run on.")
 
 ;; FIXME: find ``\score'' in buffers / make settable?
 (defun LilyPond-get-master-file ()
@@ -756,7 +756,7 @@ command."
   (define-key LilyPond-mode-map "\C-cb" 'LilyPond-what-beat)
   (define-key LilyPond-mode-map "\C-cf" 'font-lock-fontify-buffer)
   (define-key LilyPond-mode-map "\C-ci" 'LilyPond-insert-tag-current)
-  ;; the following will should be overriden by Lilypond Quick Insert Mode
+  ;; the following will should be overridden by LilyPond Quick Insert Mode
   (define-key LilyPond-mode-map "\C-cq" 'LilyPond-quick-insert-mode)
   (define-key LilyPond-mode-map "\C-c;" 'LilyPond-comment-region)
   (define-key LilyPond-mode-map ")" 'LilyPond-electric-close-paren)

flower/include/international.hh

@@ -15,7 +15,7 @@
 
 /**
    Internationalisation: _i ("to be translated") gets an entry in the POT file
-   gettext () must be invoked explicitely to do the actual "translation".
+   gettext () must be invoked explicitly to do the actual "translation".
    See flower/getopt-long.cc.
 */
 #define _i(sz) sz

flower/include/interval.hh

@@ -14,7 +14,7 @@
 
 /* A T interval.  This represents the closed interval [left,right].
    No invariants.  T must be a totally ordered ring (with division, anyway ..)
-   At instantiation, the function infinity () has to be defined explicitely. */
+   At instantiation, the function infinity () has to be defined explicitly. */
 template<class T>
 struct Interval_t : public Drul_array<T>
 {

input/manual/unfretted-headword.ly

@@ -16,7 +16,7 @@
 
 %% Here by, I, the composer, agree that this extract of my composition
 %% be in the public domain and can be part of, used and presented in
-%% the Lilypond Documention Project.
+%% the LilyPond Documention Project.
 
 %% Statement Date: Octber the 9th, 2008
 

lily/main.cc

@@ -128,7 +128,7 @@ static Getopt_long *option_parser = 0;
 
 /* Internationalisation kludge in two steps:
  * use _i () to get entry in POT file
- * call gettext () explicitely for actual "translation"  */
+ * call gettext () explicitly for actual "translation"  */
 
 static Long_option_init options_static[]
 = {

lily/paper-column.cc

@@ -348,6 +348,7 @@ ADD_INTERFACE (Paper_column,
 	       " non-musical, to which musical and non-musical objects are"
 	       " attached respectively.  The spacing engine determines the"
 	       " X@tie{}positions of these objects.\n"
+	       "\n"
 	       "They are numbered, the first (leftmost) is column@tie{}0."
 	       "  Numbering happens before line breaking, and columns are not"
 	       " renumbered after line breaking.  Since many columns go"

lilypond-texi2html.init

@@ -1,7 +1,7 @@
 #!/usr/bin/env perl
 # -*- coding: utf-8; -*-
 
-### texi2html customization script for Lilypond
+### texi2html customization script for LilyPond
 ### Author: Reinhold Kainhofer <[email protected]>, 2008.
 ###         Some code parts copied from texi2html and adapted. These functions
 ###         were written mainly by Patrice Dumas

ly/bagpipe.ly

@@ -1,5 +1,5 @@
 %{
-  Bagpipe music settings for Lilypond.
+  Bagpipe music settings for LilyPond.
   This file builds on work by Andrew McNabb (http://www.mcnabbs.org/andrew/)
   
   Substantial changes and additions made by 

ly/predefined-guitar-ninth-fretboards.ly

@@ -2,7 +2,7 @@
 %
 %  Add ninth chords to to predefined fret diagrams for standard guitar tunings
 %
-%  This is part of the Lilypond distribution files
+%  This is part of the LilyPond distribution files
 %
 %  Copyright 2008--2009 by Jonathan Kulp
 %

python/convertrules.py

@@ -2218,7 +2218,7 @@ def conv (str):
 	stderr_write ('\n')
 	stderr_write (_ ('''
 Auto beam settings must now specify each interesting moment in a measure
-explicitely; 1/4 is no longer multiplied to cover moments 1/2 and 3/4 too.
+explicitly; 1/4 is no longer multiplied to cover moments 1/2 and 3/4 too.
 '''))
 	stderr_write (UPDATE_MANUALLY)
 	stderr_write ('\n')

python/musicexp.py

@@ -753,7 +753,7 @@ def print_ly (self, printer):
         # TODO: maybe set line-width instead of right-margin?
         self.print_length_field (printer, "right-margin", self.right_margin)
         # TODO: What's the corresponding setting for system_left_margin and
-        #        system_right_margin in Lilypond?
+        #        system_right_margin in LilyPond?
         self.print_length_field (printer, "between-system-space", self.system_distance)
         self.print_length_field (printer, "page-top-space", self.top_system_distance)
 

scm/define-grob-properties.scm

@@ -725,7 +725,7 @@ rest?")
      (stencils ,list? "Multiple stencils, used as intermediate
 value.")
      (strict-grace-spacing ,boolean? "If set, main notes are spaced
-normally, then grace notes are put left of the musical columns fot the
+normally, then grace notes are put left of the musical columns for the
 main notes.")
      (strict-note-spacing ,boolean? "If set, unbroken columns with
 non-musical material (clefs, bar lines, etc.) are not spaced

scripts/musicxml2ly.py

@@ -1338,7 +1338,7 @@ def musicxml_words_to_lily_event (words):
     # TODO: How should I best convert the font-family attribute?
 
     # TODO: How can I represent the underline, overline and line-through
-    #       attributes in Lilypond? Values of these attributes indicate
+    #       attributes in LilyPond? Values of these attributes indicate
     #       the number of lines
 
     return event
@@ -1710,7 +1710,7 @@ def musicxml_harmony_to_lily_chordname (n):
             ev.bass = musicxml_chordpitch_to_lily (bass)
         inversion = n.get_maybe_exist_named_child ('inversion')
         if inversion:
-            # TODO: Lilypond does not support inversions, does it?
+            # TODO: LilyPond does not support inversions, does it?
 
             # Mail from Carl Sorensen on lilypond-devel, June 11, 2008:
             # 4. LilyPond supports the first inversion in the form of added