SUG: small addition (fix Stellarium#1275)

Author: gzotti

guide/ch_advanced_use.tex

@@ -142,11 +142,13 @@ \section{Directory Structure}
 \item[\file{skycultures/}] contains constellations, common star names and
   constellation artwork for Stellarium's many sky cultures. Each culture
   has its own sub-directory in the skycultures directory.
+\item[\file{scripts/}] contains your own scripts. These can be used to create
+  complex demonstrations (see ch.~\ref{ch:scripting}). 
 \item[\file{nebulae/}] contains data and image files for nebula textures.
   In the future Stellarium may be able to support multiple sets of nebula
   images and switch between them at runtime. This feature is not
   implemented for version~\StelVersion, although the directory structure is in
-  place - each set of nebula textures has its own sub-directory in the
+  place -- each set of nebula textures has its own sub-directory in the
   nebulae directory.
   %% TODO: Update this if no longer valid.
 \item[\file{stars/}] contains Stellarium's star catalogues. In the

guide/ch_scripting.tex

@@ -151,13 +151,16 @@ \section{Example: Retrograde motion of Mars}
 \end{figure}
 
 \subsection{Script header}
-Any ``complex'' script should contain a few lines in the first part 
-of the file, which contains important data for humans --- the 
-name of the script and its description --- and some rules for 
-Stellarium. You can even assign default shortcuts in the script header, 
-but make sure you assign a key not used elsewhere! The description 
-may cover several lines (until the end of the commented header) 
-and should therefore be the last entry of the header.
+Any ``complex'' script should contain a few lines in the first part of
+the file, which contains important data for humans --- the name of the
+script and its description --- and some rules for Stellarium. You can
+even assign default shortcuts in the script header, but make sure you
+assign a key not used elsewhere! The shortcuts are read during startup
+from all scripts in the \file{scripts} subdirectories of both program
+and user data directories (see section
+\ref{sec:FilesAndDirectories:DirectoryStructure}).  The description
+may cover several lines (until the end of the commented header) and
+should therefore be the last entry of the header.
 
 \begin{script}
 //