X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fnotation%2Fnotation-appendices.itely;h=2ee583b1d5c589563804086ecaa6d6a13bdb0a12;hb=7ba0a22641cb0c7f5949d66a06d1e2e1fd0b3033;hp=0669a5933e35c637147f27b3eeb5cf3409d634b4;hpb=0960af56b761197555446c7ce36c36abf88fac03;p=lilypond.git

diff --git a/Documentation/notation/notation-appendices.itely b/Documentation/notation/notation-appendices.itely
index 0669a5933e..2ee583b1d5 100644
--- a/Documentation/notation/notation-appendices.itely
+++ b/Documentation/notation/notation-appendices.itely
@@ -1040,7 +1040,7 @@ or in the source code.
 
 An association list or @strong{alist} for short is a Scheme pair
 which associates a value with a key: @w{@code{(key . value)}}.  For
-example, in @file{scm/@/lily@/.scm}, the alist
+example, in @file{scm/lily.scm}, the alist
 @w{@qq{type-p-name-alist}} associates certain type predicates
 (e.g.@tie{}@code{ly:music?}) with names (e.g.@tie{}@qq{music}) so
 that type-check failures can be reported with a console message that
@@ -1181,10 +1181,10 @@ Internals Reference:
 A @strong{lexer} is a program which converts a sequence of
 characters into a sequence of tokens, a process called lexical
 analysis.  The LilyPond lexer converts the stream obtained from an
-input @file{@/.ly} file into a tokenized stream more suited to the
+input @file{.ly} file into a tokenized stream more suited to the
 next stage of processing - parsing, for which see @ref{parser}.
 The LilyPond lexer is built with Flex from the lexer file
-@file{lily/@/lexer@/.ll} which contains the lexical rules.  This file
+@file{lily/lexer.ll} which contains the lexical rules.  This file
 is part of the source code and is not included in the LilyPond
 binary installation.
 
@@ -1233,7 +1233,7 @@ tree of tokens whose root is the grammar's start symbol.  If this
 cannot be achieved the file is invalid and an appropriate error
 message is produced.  The syntactic groupings and the rules for
 constructing the groupings from their parts for the LilyPond syntax
-are defined in @file{lily/@/parser@/.yy} and shown in Backus Normal Form
+are defined in @file{lily/parser.yy} and shown in Backus Normal Form
 (BNF) in @ref{LilyPond grammar}.  This file is used to build the
 parser during the program build by the parser generator, Bison.  It
 is part of the source code and is not included in the LilyPond
@@ -1263,7 +1263,7 @@ These are variables defined directly in Scheme.  Their direct
 use by users is strongly discouraged, because their scoping
 semantics can be confusing.
 
-When the value of such a variable is changed in a @file{@/.ly} file,
+When the value of such a variable is changed in a @file{.ly} file,
 the change is global, and unless explicitly reverted, the new value
 will persist to the end of the file, affecting subsequent
 @code{\score} blocks as well as external files added with the
@@ -1322,7 +1322,7 @@ smobs are created from C++ objects through macros.  There are two
 types of smob objects: simple smobs, intended for simple immutable
 objects like numbers, and complex smobs, used for objects with
 identities.  If you have access to the LilyPond sources, more
-information can be found in @file{lily/@/includes/@/smob@/.hh}.
+information can be found in @file{lily/includes/smob.hh}.
 
 @node stencil
 @unnumberedsubsec stencil