Fix typos in the English manual.

[lilypond.git] / Documentation / usage / suggestions.itely

diff --git a/Documentation/usage/suggestions.itely b/Documentation/usage/suggestions.itely
index d101821c021349f14987110e6b961ae7833a9b60..74833b69606b0524be65bc4589f96b5727831e6d 100644 (file)
--- a/Documentation/usage/suggestions.itely
+++ b/Documentation/usage/suggestions.itely
@@ -4,7 +4,8 @@
     Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
 
     When revising a translation, copy the HEAD committish of the
-    version that you are working on.  See TRANSLATION for details.
+    version that you are working on.  For details, see the Contributors'
+    Guide, node Updating translation committishes..
 @end ignore
 
 @c \version "2.12.0"
@@ -41,11 +42,11 @@ structured in order to be easier (or harder) to update.
 @end itemize
 
 @menu
-* General suggestions::         
-* Typesetting existing music::  
-* Large projects::              
-* Troubleshooting::             
-* Make and Makefiles::          
+* General suggestions::
+* Typesetting existing music::
+* Large projects::
+* Troubleshooting::
+* Make and Makefiles::
 @end menu
 
 
@@ -283,7 +284,7 @@ The commands to define rules in a makefile differ
 according to platform; for instance the various forms of Linux and
 MacOS use @code{bash}, while Windows uses @code{cmd}. Note that on
 MacOS X, you need to configure the system to use the command-line
-intepreter. Here are some example makefiles, with versions for both
+interpreter. Here are some example makefiles, with versions for both
 Linux/MacOS and Windows.
 
 The first example is for an orchestral work in four