From 4b40b75cc58a804531be9af080515138ff5b607b Mon Sep 17 00:00:00 2001
From: Graham Percival <graham@percival-music.ca>
Date: Wed, 4 May 2005 03:59:59 +0000
Subject: [PATCH] Minor fixes.

---
 ChangeLog                             |  3 +-
 Documentation/user/introduction.itely | 64 ++++++++++++++++++++++-----
 Documentation/user/invoking.itely     |  9 ----
 3 files changed, 54 insertions(+), 22 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index d33d30548c..9b5cdca031 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -2,7 +2,8 @@
 
 	* Documentation/user/introduction.itely: updates "About this manual".
 
-	* Documentation/user/advanced-notation.itely: minor fixes.
+	* Documentation/user/advanced-notation.itely,
+	invoking.itely: minor fixes.
 
 2005-05-04  Han-Wen Nienhuys  <hanwen@xs4all.nl>
 
diff --git a/Documentation/user/introduction.itely b/Documentation/user/introduction.itely
index eac3d223a0..8eb1739442 100644
--- a/Documentation/user/introduction.itely
+++ b/Documentation/user/introduction.itely
@@ -648,35 +648,76 @@ The
 provides templates of LilyPond pieces.  Just cut and paste a
 template into a file, add notes, and you're done!
 
+@item
+@emph{@ref{Putting it all together}}
+demonstrates practical uses of LilyPond.
+
+@item
+@ifhtml
+The chapter
+@end ifhtml
+@emph{@ref{Running LilyPond}} shows how to run LilyPond and its helper
+programs.  In addition, this section explains how to upgrade input
+files from previous versions of LilyPond.
+
 @item
 @ifhtml
 The
 @end ifhtml
-@c @emph{@ref{Notation manual}} @c FIXME
-@emph{Notation manual}
-discusses topics grouped by notation construct.  Once you master the
-basics, this is the place to look up details.
+@emph{@ref{Basic notation}}
+@ifteml
+chapter
+@end ifhtml
+discusses topics grouped by notation construct.  This section gives
+details about basic notation that will be useful in almost any
+notation project.
 
 @item
 @ifhtml
 The
 @end ifhtml
-@emph{@ref{Changing defaults}}
-explains how to fine tune layout.
+@emph{@ref{Instrument-specific notation}}
+@ifteml
+chapter
+@end ifhtml
+discusses topics grouped by notation construct.  This section gives
+details about special notation that will only be useful for particular
+instrument (or vocal) groups.
 
 @item
 @ifhtml
-The chapter
+The
 @end ifhtml
-@emph{@ref{Running LilyPond}} shows how to run LilyPond and its helper
-programs.
+@emph{@ref{Advanced notation}}
+@ifteml
+chapter
+@end ifhtml
+discusses topics grouped by notation construct.  This section gives
+details about complicated or unusual notation.
+
+@item
+@ifhtml
+The
+@end ifhtml
+@emph{@ref{Global issues}}
+@ifhtml
+chapter
+@end ifhtml
+discusses issues which affect the whole lilypond file.
+
+@item
+@ifhtml
+The
+@end ifhtml
+@emph{@ref{Changing defaults}}
+explains how to fine tune layout.
 
 @item
 @ifhtml
 The chapter
 @end ifhtml
 @emph{@ref{LilyPond-book}} explains the details behind creating
-documents with in-line music examples (like this manual).
+documents with in-line music examples, like this manual.
 
 @item
 @ifhtml
@@ -685,8 +726,7 @@ The chapter
 @emph{@ref{Converting from other formats}}
 explains how to run the conversion programs.  These programs
 are supplied with the LilyPond package, and convert a variety of music
-formats to the @code{.ly} format.  In addition, this section explains
-how to upgrade input files from previous versions of LilyPond.
+formats to the @code{.ly} format.
 
 @item
 @ifhtml
diff --git a/Documentation/user/invoking.itely b/Documentation/user/invoking.itely
index dde919cbb0..b4157bde31 100644
--- a/Documentation/user/invoking.itely
+++ b/Documentation/user/invoking.itely
@@ -231,15 +231,6 @@ real root filesystem.  The entire content of the LilyPond installation
 (e.g., @file{/usr/share/lilypond})
 should be copied.
 
-@ignore
-FIXME:  fact-check; delete very soon.  -gp
-, and the content of the @file{fonts},
-@file{dvips} and @file{web2c} directories of the @TeX{} installation
-(usually under @file{/usr/share/texmf}) should be copied, too.  If your
-@TeX{} installation uses @file{ls-R} caches, copy also the cache inside the root
-of the installation.
-@end ignore
-
 If problems arise, the simplest way to trace them down is to run
 LilyPond using @command{strace}, which will allow you to determine which
 files are missing.
-- 
2.39.5