Web-es: fix a couple of Spanish links.

[lilypond.git] / Documentation / usage / suggestions.itely

diff --git a/Documentation/usage/suggestions.itely b/Documentation/usage/suggestions.itely
index 263e12e6873af3f6911af86c5e93178c8d6cf60a..73de64e0f99f35b8350d32140826e1782b90c154 100644 (file)
--- a/Documentation/usage/suggestions.itely
+++ b/Documentation/usage/suggestions.itely
@@ -8,7 +8,7 @@
     Guide, node Updating translation committishes..
 @end ignore
 
-@c \version "2.16.0"
+@c \version "2.19.21"
 
 @node Suggestions for writing files
 @chapter Suggestions for writing files
@@ -99,8 +99,8 @@ indicators) will help avoid such problems.  For example;
 
 @example
 \new Staff @{
-  \relative g' @{
-    r4 g8 g c8 c4 d |
+  \relative @{
+    r4 g'8 g c8 c4 d |
     e4 r8 |
     % Ossia section
     <<
@@ -118,7 +118,7 @@ indicators) will help avoid such problems.  For example;
 is much easier to follow than;
 
 @example
-\new Staff @{ \relative g' @{ r4 g8 g c4 c8 d | e4 r8
+\new Staff @{ \relative @{ r4 g'8 g c4 c8 d | e4 r8
 % Ossia section
 << @{ f8 c c @} \new Staff @{ f8 f c @} >> r4 | @} @}
 @end example
@@ -205,8 +205,8 @@ the @code{violin} definition is extremely unlikely to change
 in a new version of LilyPond.
 
 @example
-violin = \relative c'' @{
-g4 c'8. e16
+violin = \relative @{
+g'4 c'8. e16
 @}
 @dots{}
 \score @{
@@ -227,8 +227,8 @@ need to do this once, and we can still avoid touching anything inside
 @example
 fthenp = _\markup@{
   \dynamic f \italic \small @{ 2nd @} \hspace #0.1 \dynamic p @}
-violin = \relative c'' @{
-g4\fthenp c'8. e16
+violin = \relative @{
+g'4\fthenp c'8. e16
 @}
 @end example
 
@@ -275,9 +275,9 @@ then comment out all of the bass music (but leave
 @code{\bass} in the @code{\score} uncommented.
 
 @example
-bass = \relative c' @{
+bass = \relative @{
 %@{
-  c4 c c c
+  c'4 c c c
   d d d d
 %@}
 @}
@@ -296,13 +296,13 @@ Another very useful debugging technique is constructing
 @cindex makefiles
 @cindex make
 
-Pretty well all the platforms Lilypond can run on support a software
+Pretty well all the platforms LilyPond can run on support a software
 facility called @code{make}.  This software reads a special file called a
 @code{Makefile} that defines what files depend on what others and what
 commands you need to give the operating system to produce one file from
 another.  For example the makefile would spell out how to produce
 @file{ballad.pdf} and @file{ballad.midi} from @file{ballad.ly} by
-running Lilypond.
+running LilyPond.
 
 There are times when it is a good idea to create a @code{Makefile}
 for your project, either for your own convenience or