More proofread for tutorial.

diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely
index 29b9d67a1ff1a4ead07c121e56e473c9038b92d2..d1b5eb467ce88abdbc56e770421370dd92925f59 100644 (file)
--- a/Documentation/user/tutorial.itely
+++ b/Documentation/user/tutorial.itely
@@ -135,7 +135,8 @@ Be warned that the first time you ever run LilyPond, it will take a minute
 or two because all of the system fonts have to be analyzed first.
 
 For future use of LilyPond, you should begin by selecting "New"
-or "Open".
+or "Open".  You must save your file before typesetting it.  If any errors
+occur in processing, please see the log window.
 
 @subsubheading Windows
 
@@ -152,7 +153,20 @@ codes that will confuse LilyPond.} and enter
 
 Save it on the desktop as @file{test.ly} and make sure that it is not
 called @file{test.ly.TXT}.  Double clicking @file{test.ly} will process
-the file and show the resulting PDF file.
+the file and show the resulting PDF file.  To edit an existing
+@file{.ly} file, right-click on it and select @qq{Edit source}.
+
+If you double-click in the LilyPond icon on the Desktop, it will open
+a simple text editor with an example file. Save it, for example, to
+@file{test.ly} on your Desktop, and then double-click on the file to
+process it.  After some seconds, you will get a file @file{test.pdf}
+on your desktop.  Double-click on this PDF file to view the typeset
+score.  An alternative method to process the @file{test.ly} file
+is to drag and drop it onto the LilyPond icon using your mouse pointer.
+
+Double-clicking the file does not only result in a PDF file, but also
+produces a @file{.log} file that contains some information on what LilyPond
+has done to the file.  If any errors occur, please examine this file.
 
 
 @subsubheading Unix