Doc: cleanup @file{}, take 2: remove all @/ escaping sequences.

[lilypond.git] / Documentation / learning / fundamental.itely

diff --git a/Documentation/learning/fundamental.itely b/Documentation/learning/fundamental.itely
index 23f4ba4fbfeafaf3a535054a8fbed8e63837f0cf..8ee72ee770ad95f78b5f326671bc590aa1e2cb65 100644 (file)
--- a/Documentation/learning/fundamental.itely
+++ b/Documentation/learning/fundamental.itely
@@ -191,7 +191,7 @@ You may code multiple @code{\score} blocks.  Each will be
 treated as a separate score, but they will be all combined into
 a single output file.  A @code{\book} command is not necessary
 -- one will be implicitly created.  However, if you would like
-separate output files from one @code{.ly} file then the
+separate output files from one @file{.ly} file then the
 @code{\book} command should be used to separate the different
 sections: each @code{\book} block will produce a
 separate output file.
@@ -2845,10 +2845,10 @@ curious, have a look at @ruser{Overview of modifying properties}.
 In this case, we want to modify the @code{stretchability}
 sub-property only. Again, for the curious, you can find the
 default values for the staff-staff-spacing property
-in file @file{scm/@/define-grobs@/.scm} by looking up the definition
+in file @file{scm/define-grobs.scm} by looking up the definition
 of the @code{VerticalAxisGroup} grob.  The value for
 @code{stretchability} is taken from the definition of the
-@code{PianoStaff} context (in file @file{ly/@/engraver-init@/.ly})
+@code{PianoStaff} context (in file @file{ly/engraver-init.ly})
 so that the values are identical.
 
 @example
@@ -3078,7 +3078,7 @@ LilyPond input syntax changes (see
 you have a single definition (such as @code{\dolce}) for all your
 input files (see @ref{Style sheets}), then if the syntax changes, you
 only need to update your single @code{\dolce} definition,
-instead of making changes throughout every @code{.ly} file.
+instead of making changes throughout every @file{.ly} file.
 
 
 @node Scores and parts