Merge branch 'master' of git://git.savannah.gnu.org/lilypond.git

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

diff --git a/Documentation/usage/suggestions.itely b/Documentation/usage/suggestions.itely
index 8f5bae0b08d6c4a3b5e7cdb1c3a09065154230e6..8b3314257a5997e1a5c8c3ad59fd01936c8c96be 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.13.36"
+@c \version "2.14.0"
 
 @node Suggestions for writing files
 @chapter Suggestions for writing files
@@ -261,7 +261,7 @@ 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
+@file{ballad.pdf} and @file{ballad.midi} from @file{ballad.ly} by
 running Lilypond.
 
 There are times when it is a good idea to create a @code{Makefile}
@@ -320,13 +320,13 @@ Symphony/
 `-- symphonyDefs.ily
 @end example
 
-The @file{@/.ly} files in the @file{Scores} and
-@file{Parts} directories get their notes from @file{@/.ily}
+The @file{.ly} files in the @file{Scores} and
+@file{Parts} directories get their notes from @file{.ily}
 files in the @file{Notes} directory:
 
 @example
 %%% top of file "symphony-cello.ly"
-\include ../definitions.ily
+\include ../symphonyDefs.ily
 \include ../Notes/cello.ily
 @end example