From: Graham Percival <graham@percival-music.ca>
Date: Sun, 24 Dec 2006 11:43:25 +0000 (-0800)
Subject: Remove duplicate example.
X-Git-Tag: release/2.11.5-1~17^2^2~2
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=ab388c17b5471cdbab29d6801b60303dbf5d01f3;p=lilypond.git

Remove duplicate example.
---

diff --git a/Documentation/user/instrument-notation.itely b/Documentation/user/instrument-notation.itely
index 42e4348cc6..e7e1b1aa89 100644
--- a/Documentation/user/instrument-notation.itely
+++ b/Documentation/user/instrument-notation.itely
@@ -1287,25 +1287,16 @@ It is also possible to define melismata entirely in the lyrics. This
 can be done by entering @code{_} for every note that is part of the
 melisma.
 
-@lilypond[relative=1,verbatim,fragment]
+@lilypond[relative=1,verbatim,fragment,quote]
 { \set melismaBusyProperties = #'()
   c d( e) f f( e) e e  }
 \addlyrics
  { Ky -- _ _ ri __ _ _ _  e }
 @end lilypond
 
-In this case, you can also have ties and slurs in the melody, if you
+In this case, you can also have ties and slurs in the melody if you
 set @code{melismaBusyProperties}, as is done in the example above.
 
-@lilypond[relative=1,verbatim,fragment,quote]
-{
- \set melismaBusyProperties = #'()
-  c d( e) f f( e) e e
-}
-\addlyrics
- { Ky -- _ _ ri __ _ _ _  e }
-@end lilypond
-
 
 @node Lyrics independent of notes
 @subsubsection Lyrics independent of notes