diff --git a/doc/scheduler-directives.tex b/doc/scheduler-directives.tex
index 5fbbcbc..7f88dd6 100644
--- a/doc/scheduler-directives.tex
+++ b/doc/scheduler-directives.tex
@@ -27,7 +27,6 @@ \subsubsection{Directives}
 \begin{verbatim}
 #SBATCH --job-name=<jobname>        ## or -J. Give the job a name 
 #SBATCH --mail-type=<type>          ## Set type of email notifications
-#SBATCH --mail-user=<YOUR_USERNAME>@encs.concordia.ca 
 #SBATCH --chdir=<directory>         ## or -D, Set working directory where output files will go 
 #SBATCH --nodes=1                   ## or -N, Node count required for the job
 #SBATCH --ntasks=1                  ## or -n, Number of tasks to be launched
@@ -38,7 +37,6 @@ \subsubsection{Directives}
 Replace the following to adjust the job script for your project(s)
 \begin{enumerate}
   \item \verb+<jobname>+ with a job name for the job
-  \item \verb+<YOUR_USERNAME>+ with your GCS username
   \item \verb+<directory>+ with the fullpath to your job's working directory, e.g., where your code,
 source files and where the standard output files will be written to. By default, \verb+--chdir+
 sets the current directory as the job's working directory 
@@ -53,7 +51,6 @@ \subsubsection{Directives}
 \begin{verbatim}
 #SBATCH -J tmpdir                   ## Job's name set to 'tmpdir'
 #SBATCH --mail-type=ALL             ## Receive all email type notifications
-#SBATCH --mail-user=a_user@encs.concordia.ca 
 #SBATCH -D ./                       ## Use current directory as working directory
 #SBATCH -N 1                        ## Node count required for the job
 #SBATCH -n 1                        ## Number of tasks to be launched
diff --git a/doc/scheduler-scripting.tex b/doc/scheduler-scripting.tex
index bc10e00..5d60426 100644
--- a/doc/scheduler-scripting.tex
+++ b/doc/scheduler-scripting.tex
@@ -264,12 +264,10 @@ \subsection{Common Job Management Commands Summary}
 \texttt{seff [job-ID]}: reports on the efficiency of a job's cpu and memory utilization. 
 Don't execute it on RUNNING jobs (only on completed/finished jobs), efficiency statistics may be misleading.
 
-If you define the following directives in your batch script, you will receive seff output in your email when your job is finished.
+If you define the following directive in your batch script, your ENCS email address will receive an email with seff output when your job is finished.
 \small
 \begin{verbatim}
 #SBATCH --mail-type=ALL        
-#SBATCH --mail-user=USER_NAME@encs.concordia.ca 
-## Replace USER_NAME with your encs username.
 \end{verbatim}
 \normalsize
 
diff --git a/doc/speed-manual.pdf b/doc/speed-manual.pdf
index c063e8a..0cf7c83 100644
Binary files a/doc/speed-manual.pdf and b/doc/speed-manual.pdf differ
diff --git a/doc/speed-manual.tex b/doc/speed-manual.tex
index 53473e7..2b7384c 100644
--- a/doc/speed-manual.tex
+++ b/doc/speed-manual.tex
@@ -343,7 +343,6 @@ \section{Job Management}
 Job instructions in a script start with \verb+#SBATCH+ prefix, for example:
 \begin{verbatim}
 #SBATCH --account=speed1 --mem=100M -t 600 -J job-name
-#SBATCH --gpus=2 --mail-type=ALL -t 600 --mail-user=YOUR_USERNAME
 \end{verbatim}
 %
 We use \tool{srun} for every complex compute step inside the script.