Doc: ensure two spaces after end of sentence.

[lilypond.git] / Documentation / notation / input.itely

diff --git a/Documentation/notation/input.itely b/Documentation/notation/input.itely
index 163d8c05a0a22e3f49a2ad49b2156b63ab10120a..1dd00e6c5cc5e749f9b0f1de6c2a780ef5b5c373 100644 (file)
--- a/Documentation/notation/input.itely
+++ b/Documentation/notation/input.itely
@@ -876,13 +876,13 @@ statements of their own.  By default, these second-level
 @code{\include} statements are not interpreted until they have
 been brought into the main file, so the file names they specify
 must all be relative to the directory containing the main file,
-not the directory containing the included file. However,
+not the directory containing the included file.  However,
 this behavior can be changed by passing the option
 @code{-drelative-includes} option at the command line
 (or by adding @code{#(ly:set-option 'relative-includes #t)}
-at the top of the main input file). With @code{relative-includes}
+at the top of the main input file).  With @code{relative-includes}
 set, the path for each @code{\include} command will be taken
-relative to the file containing that command. This behavior is
+relative to the file containing that command.  This behavior is
 recommended and it will become the default behavior in a future
 version of lilypond.
 
@@ -1453,21 +1453,15 @@ Here are a few sample bars of music set in LilyPond's Feta font:
 
 @subsubheading Installation Instructions for MacOS
 
-Download and extract the zip file.  Using @code{Terminal.app}, move
-the @code{lilyfonts} directory to
-@file{@var{INSTALLDIR}/LilyPond.app/Contents/Resources/share/lilypond/current}.
+Download and extract the zip file.  Copy the @code{lilyfonts}
+directory to @file{@var{SHARE_DIR}/lilypond/current}; for more
+information, see @rlearning{Other sources of information}.
 Move the existing @code{fonts} directory to @code{fonts_orig} and
 move the @code{lilyfonts} directory to @code{fonts}.  Simply move
 @code{fonts_orig} back to @code{fonts} to revert back to Feta.
 
-@subsubheading Installation Instructions for Windows
-
-Download and extract the zip file.  Using Explorer, copy the @code{lilyfonts}
-directory to
-@file{@var{INSTALLDIR}/LilyPond/usr/share/lilypond/current}. Rename
-the existing @code{fonts} directory to @code{fonts_orig} and
-rename the @code{lilyfonts} directory to @code{fonts}.  Simply rename
-@code{fonts_orig} back to @code{fonts} to revert back to Feta.
+@seealso
+Learning Manual: @rlearning{Other sources of information}.
 
 @knownissues
 
@@ -1522,7 +1516,7 @@ To create a MIDI output file from a LilyPond input file, add a
 
 If there is a @code{\midi} block in a @code{\score} with no
 @code{\layout} block, only MIDI output will be produced.  When
-notation is needed too, a @code{\layout} block must be also be
+notation is needed too, a @code{\layout} block must also be
 present.
 
 @example
@@ -1546,12 +1540,12 @@ with the @code{\tempo} command within the music notation.  These
 are reflected in tempo changes in the MIDI output.  This command
 will normally result in the metronome mark being printed, but this
 can be suppressed, see @ref{Metronome marks}.  An alternative way
-of specifying the inital or overall MIDI tempo is described below,
+of specifying the initial or overall MIDI tempo is described below,
 see @ref{MIDI block}.
 
 Due to some limitations on Windows, the default extension for
-MIDI files on Windows is @code{.mid}. Other operating systems still
-use the extension @code{.midi}. If a different extension is preferred,
+MIDI files on Windows is @code{.mid}.  Other operating systems still
+use the extension @code{.midi}.  If a different extension is preferred,
 insert the following line at the top-level of the input file,
 before the start of any @code{\book}, @code{\bookpart} or @code{\score} blocks:
 
@@ -1725,7 +1719,7 @@ The following items of notation are reflected in the MIDI output:
 
 @itemize
 @item Pitches
-@item Microtones (See @ref{Accidentals}. Rendering needs a
+@item Microtones (See @ref{Accidentals}.  Rendering needs a
 player that supports pitch bend.)
 @item Chords entered as chord names
 @item Rhythms entered as note durations, including tuplets