lilypond-book robustness: ensure EOL at the end of @verbatim

[lilypond.git] / Documentation / es / user / specialist.itely

diff --git a/Documentation/es/user/specialist.itely b/Documentation/es/user/specialist.itely
index f2cd98e2e1f5ed517a4e0eb791e37510563358e2..23dfb3118a802972b0c498ba9791e78eb53b0e93 100644 (file)
--- a/Documentation/es/user/specialist.itely
+++ b/Documentation/es/user/specialist.itely
@@ -1,25 +1,29 @@
 @c -*- coding: utf-8; mode: texinfo; -*-
 @ignore
-    Translation of GIT committish: b9526773cf95ca29e3d3352c524718fc8e91c599
+    Translation of GIT committish: 41ef91786a08102d9b9a839f6a2f40cec263d723
 
     When revising a translation, copy the HEAD committish of the
     version that you are working on.  See TRANSLATION for details.
 @end ignore
 
-@c \version "2.11.38"
+@c \version "2.12.0"
 
-This chapter explains how to create musical notation for specific
-types of instrument or in specific styles.
+@node Specialist notation
+@chapter Specialist notation
+
+Este capítulo explica cómo crear notación musical para instrumentos de
+un tipo específico o dentro de estilos específicos.
 
 @menu
 * Vocal music::
-* Keyboard instruments::
+* Keyboard and other multi-staff instruments::
 * Unfretted string instruments::
 * Fretted string instruments::
 * Percussion::
 * Wind instruments::
 * Chord notation::
 * Ancient notation::
+* World music::
 @end menu
 
 @include vocal.itely
@@ -30,3 +34,4 @@ types of instrument or in specific styles.
 @include wind.itely
 @include chords.itely
 @include ancient.itely
+@include world.itely