fixes.

[lilypond.git] / Documentation / topdocs / INSTALL.texi

diff --git a/Documentation/topdocs/INSTALL.texi b/Documentation/topdocs/INSTALL.texi
index 691dfbac45291a19f86675e9b2d6408e2276d8f5..af8762029886e8835268b6720a4d049cf445caa2 100644 (file)
--- a/Documentation/topdocs/INSTALL.texi
+++ b/Documentation/topdocs/INSTALL.texi
@@ -43,7 +43,7 @@ packages if these are available for your platform.
 @c Otoh, lilypond.org is not updated when release mail arrives
 @uref{ftp://ftp.lilypond.org/pub/LilyPond/} by FTP and
 @uref{http://www.lilypond.org/ftp/} by HTTP.
-@item @uref{ftp://sca.uwaterloo.ca/pub/} by FTP (Canadian mirror)
+@item @uref{ftp://sca.uwaterloo.ca/pub/} by FTP (Canadian mirror).
 @end itemize
 
 
@@ -119,7 +119,7 @@ on the FTP site.
 @end example
 @end itemize
 
-@subsection Font problems.
+@subsection Font problems
 
 If you are upgrading from a previous version of LilyPond, be sure to
 remove all old font files. These include @file{.pk} and @file{.tfm} files
@@ -168,7 +168,7 @@ distribution supports g++ 3.x and flex.  For workarounds, see
 lexer-gcc-3.0.patch and lexer-gcc-3.1.sh in the source directory.
 
 @item Bison (version 1.25 or newer).
-Check out @uref{http://www.gnu.org/software/bison/,the bison  webpage}
+Check out @uref{http://www.gnu.org/software/bison/,the bison webpage}.
 
 @item @TeX{}.
 
@@ -240,7 +240,7 @@ can also build it locally. This process requires a successful compile of
 lilypond. The documentation is built by issuing
 @example 
 
-  make web-doc
+  make web
  
 @end example 
 
@@ -364,12 +364,10 @@ augroup
 
 @subsection Red Hat Linux
 
-Red Hat 7.x i386 RPMS are available from
-@uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/}.  For running on
-a Red Hat system you need these packages: guile, tetex, tetex-latex,
-tetex-dvips, libstdc++, python, ghostscript.
 
-You can also compile them yourself.  A spec file is in
+You can compile RPMS yourself.  For running on a Red Hat system you
+need these packages: guile, tetex, tetex-latex, tetex-dvips,
+libstdc++, python, ghostscript.  A spec file is in
 @file{make/out/lilypond.redhat.spec}. This file is distributed along
 with the sources.  You can make the rpm by issuing
 @example 
@@ -386,16 +384,6 @@ addition to the those needed for running: glibc-devel, gcc-c++,
 libstdc++-devel, guile-devel, flex, bison, texinfo, groff, mftrace,
 netpbm-progs, autotrace, t1utils.
 
-
-
-@subsection LinuxPPC
-
-
-Some LinuxPPC RPMS should available from
-@uref{ftp://ftp.cs.uu.nl/pub/GNU/LilyPond/binaries/}.
-
-A LinuxPPC RPM can be made using the @file{lilypond.redhat.spec} file.
-
 @subsection SuSE
 
 Some SUSE RPMS should available from