LSR: Update.

[lilypond.git] / Documentation / snippets / adding-a-figured-bass-above-or-below-the-notes.ly

diff --git a/Documentation/snippets/adding-a-figured-bass-above-or-below-the-notes.ly b/Documentation/snippets/adding-a-figured-bass-above-or-below-the-notes.ly
index 9adfd97e0efb24d34adf2e53f7a401b5d4aaf4b6..362aca6a257c153db7c2d4a94f585747bb356e67 100644 (file)
--- a/Documentation/snippets/adding-a-figured-bass-above-or-below-the-notes.ly
+++ b/Documentation/snippets/adding-a-figured-bass-above-or-below-the-notes.ly
@@ -1,6 +1,7 @@
-%% Do not edit this file; it is auto-generated from LSR http://lsr.dsi.unimi.it
+%% Do not edit this file; it is automatically
+%% generated from LSR http://lsr.dsi.unimi.it
 %% This file is in the public domain.
-\version "2.13.1"
+\version "2.13.4"
 
 \header {
   lsrtags = "chords, ancient-notation, contexts-and-engravers"
@@ -21,7 +22,8 @@ truco se aplique a toda la partitura.
 
 "
   doctitlees = "Añadir un bajo cifrado encima o debajo de las notas"
-  
+
+
 %% Translation of GIT committish: 7eb450e8e6c935410b8f3212cb53e5a731f4f33f
   doctitlefr = "Ajout d'une basse chiffrée au-dessus ou au-dessous des notes"
 
@@ -34,7 +36,7 @@ in a @code{Staff} context). Choices are @code{#UP} (or @code{#1}),
 
 As you can see here, this property can be changed as many times as you
 wish. Use @code{\\once \\override} if you don't want the tweak to apply
-to the whole score. 
+to the whole score.
 
 "
   doctitle = "Adding a figured bass above or below the notes"