LSR: Update.

[lilypond.git] / Documentation / snippets / inserting-score-fragments-above-a-staff,-as-markups.ly

diff --git a/Documentation/snippets/inserting-score-fragments-above-a-staff,-as-markups.ly b/Documentation/snippets/inserting-score-fragments-above-a-staff,-as-markups.ly
index 66f1a637812674e5e436203840e548820798b108..336062a245cc535690e79bffdb75470acc21a011 100644 (file)
--- a/Documentation/snippets/inserting-score-fragments-above-a-staff,-as-markups.ly
+++ b/Documentation/snippets/inserting-score-fragments-above-a-staff,-as-markups.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.10"
 
 \header {
   lsrtags = "staff-notation"
@@ -10,7 +11,7 @@ The @code{\\markup} command is quite versatile.  In this snippet, it
 contains a @code{\\score} block instead of texts or marks.
 
 "
-  doctitle = "Inserting score fragments above a staff, as markups"
+  doctitle = "Inserting score fragments above a staff as markups"
 } % begin verbatim
 
 tuning = \markup {