Updates to improve clarity of language

doc/scheduler-env.tex

@@ -91,6 +91,6 @@ \subsubsection{Environment Set Up}
 %fi
 %\end{verbatim}
 
-Note, if you are getting ``command not found'' error(s) when logging in, you
-probably have old Grid Engine environment commands. Remove them
-as per \xa{appdx:uge-to-slurm}.
+\textbf{Note:} If a ``command not found'' error appears after you log in to speed,
+your user account many have probably have defunct Grid Engine environment commands. 
+See \xa{appdx:uge-to-slurm} to learn how to prevent this error on login.

doc/scheduler-faq.tex

@@ -19,7 +19,7 @@ \subsubsection*{Udemy}
 
 There are a number of Udemy courses, including free ones, that will assist 
 you in learning Linux. Active Concordia faculty, staff and students have 
-access to Udemy courses such as \textbf{Linux Mastery: Master the Linux 
+access to Udemy courses. The course \textbf{Linux Mastery: Master the Linux 
 Command Line in 11.5 Hours} is a good starting point for beginners. Visit
 \url{https://www.concordia.ca/it/services/udemy.html} to learn how Concordians 
 may access Udemy.
@@ -33,7 +33,7 @@ \subsection{How to use the ``bash shell'' on Speed?}
 % ------------------------------------------------------------------------------
 \subsubsection{How do I set bash as my login shell?}
 
-In order to set your login shell to bash on Speed, your login shell on all GCS servers must be changed to bash.
+In order to set your default login shell to bash on Speed, your login shell on all GCS servers must be changed to bash.
 To make this change, create a ticket with the Service Desk (or email \texttt{help at concordia.ca}) to
 request that bash become your default login shell for your ENCS user account on all GCS servers.
 
@@ -48,20 +48,20 @@ \subsubsection{How do I move into a bash shell on Speed?}
 	bash
 \end{verbatim}	
 
-Note how the command prompt changed from \verb![speed-submit] [/home/a/a_user] >! to \verb!bash-4.4$! after entering the bash shell.
+\textbf{Note} how the command prompt changed from \verb![speed-submit] [/home/a/a_user] >! to \verb!bash-4.4$! after entering the bash shell.
 
 % ------------------------------------------------------------------------------
 \subsubsection{How do I use the bash shell in an interactive session on Speed?}
-% The language here is unclear. TODO Update for clarity and provide examples
-If you use one of the below commands (make sure job request settings such
-as memory, cores, etc are set), they will allocate your interactive
-job sessions with \tool{bash} as a shell on the compute nodes:
+
+Below are examples of how to use \tool{bash} as a shell in your interactive job sessions with
+ both the salloc and srun commands.
 
 \begin{itemize}
-	\item \texttt{salloc ... /encs/bin/bash}
-	\item \texttt{srun ... --pty /encs/bin/bash}
+	\item \texttt{salloc -ppt --mem=100G -N 1 -n 10 /encs/bin/bash}
+	\item \texttt{srun  --mem=50G -n 5 --pty /encs/bin/bash}
 \end{itemize}
 
+\textbf{Note:} Make sure the interactive job requests memory, cores, etc.
 % ------------------------------------------------------------------------------
 \subsubsection{How do I run scripts written in bash on Speed?}
 

doc/scheduler-tips.tex

@@ -9,11 +9,11 @@ \subsection{Tips/Tricks}
 to convert.
 
 \item
-Use \tool{rsync}, not \tool{scp}, when moving a lot of data around.
+Use \tool{rsync}, not \tool{scp}, when copying or moving large amounts of data.
 
 \item
-If you are going to move many many files between NFS-mounted storage and the 
-cluster, \tool{tar} everything up first. 
+Before moving a large amount of files between NFS-mounted storage and the 
+cluster, \tool{tar} up the files you plan to move first. 
 
 \item
 If you intend to use a different shell (e.g., \tool{bash}~\cite{aosa-book-vol1-bash}),
@@ -36,4 +36,4 @@ \subsection{Tips/Tricks}
 
 \item
 E-mail, \texttt{rt-ex-hpc AT encs.concordia.ca}, with any concerns/questions.
-\end{itemize}
+\end{itemize}