Updates from Maria comments and used NEKTUTORIAL definition

basics/helmholtz/basics-helmholtz.tex

@@ -74,8 +74,7 @@ Prepare for the tutorial. Make sure that you have:
    a directory \inlsh{basics-helmholtz} with subdirectories
    called \inlsh{tutorial} and \inlsh{complete}.
    
-   We will refer to the \inlsh{tutorial} directory
-as \inlsh{\$NEKTUTORIAL}.
+   We will refer to the \inlsh{tutorial} directory as \inlsh{\$NEKTUTORIAL}.
 
 The tutorial folder contains: 
 \begin{itemize}
@@ -167,7 +166,8 @@ mesh file that \inltt{NekMesh} will generate, for
 instance \inlsh{Helm\_mesh.xml}. The command line for this step is
 %
 \begin{tutorialtask}
-Convert the .meh file into a Nektar++ input by calling
+Convert the .msh file into a Nektar++ input from within the
+\$NEKTUTORIAL directory by calling
 \tutorialcommand{\$NEK/NekMesh Helm\_mesh.msh  Helm\_mesh.xml}
 or 
 \tutorialcommand{\$NEK/NekMesh Helm\_mesh.msh  Helm\_mesh.xml:xml:uncompress}
@@ -244,7 +244,7 @@ format, \inlsh{Helm\_mesh.xml}, we can visualise the mesh.  This
 step can be done by using the following Nektar++ built-in
 post-processing routine:
 %
-\begin{tutorialtask} Convert the .xml file into a .vtu format by calling
+\begin{tutorialtask} Convert the .xml file into a .vtu format within the \$NEKTUTORIAL directory by calling
 \tutorialcommand{\$NEK/FieldConvert Helm\_mesh.xml  Helm\_mesh.vtu}
 Alternatively a tecplot .dat file can be created by changing the extension of the second file, i.e. 
 \tutorialcommand{\$NEK/FieldConvert Helm\_mesh.xml  Helm\_mesh.dat}
@@ -404,8 +404,9 @@ Gmsh. For additional details on the \inltt{EXPANSIONS} tag refer to
 the \href{http://www.nektar.info/downloads/8}{User-Guide}.
 
 \begin{tutorialtask}
-Generate the file \inlsh{Helm\_conditions.xml} with $\lambda=2.5$ or
-copy it from the \inlsh{completed} directory.
+Generate the file \inlsh{Helm\_conditions.xml} in the direcotry
+\$NEKTUTORIAL with $\lambda=2.5$ or copy it from the \inlsh{completed}
+directory.
 \end{tutorialtask}
 
 
@@ -417,7 +418,7 @@ boundary conditions,
 \inlsh{Helm\_conditions.xml}, we can run the solver by using the following command:
 %
 \begin{tutorialtask}
-Run the ADRSolver using the command: 
+Run the ADRSolver in the directory \$NEKTUTORIAL using the command:
 \tutorialcommand{\$NEK/ADRSolver Helm\_mesh.xml
     Helm\_conditions.xml}
 \end{tutorialtask}
@@ -474,7 +475,7 @@ the file in order to visualise the results. In order to do so, we can
 use the built-in post-processing routines within Nektar++.  In
 particular, we can use the following command
 %
-\begin{tutorialtask} Convert the .xml and .chk files into a .vtu format
+\begin{tutorialtask} In the \$NEKTUTORIAL directory convert the .xml and .chk files into a .vtu format
 by calling
 \tutorialcommand{\$NEK/FieldConvert
     Helm\_mesh.xml Helm\_conditions.xml Helm\_mesh.fld Helm\_mesh.vtu}