diff --git a/README.md b/README.md
index 668ef2b5d6c6fcea5811b33526d9768f4e366461..7c0587e7521137d2864da47be93b313875ad1ebc 100644
--- a/README.md
+++ b/README.md
@@ -1,3 +1,9 @@
+# SLURM
+
+Slurm is an open source, fault-tolerant, and highly scalable cluster management and job scheduling system for large and small Linux clusters.
+
+[[_TOC_]]
+
 # Scientific Computing
 
 In order to make great use of a super computer one needs to be able to tell it what should be done.
@@ -45,11 +51,11 @@ The hostname of the node running our test script. Of course that is a silly job.
 2. Submit the job with `sbatch`
 3. Check the Queue and Status of your job with `squeue`
 
-## Writing a job file
+# Writing a job file
 
 There are things to consider when writing a job
 
-## Interactive Session
+# Interactive Session
 
 It is possible to ask for an interactive session on any node. When your job runs you can always `ssh` to that node and maybe check things, although your file system is available everywhere, there is no need for that.
 
@@ -73,7 +79,7 @@ How to acquire each node exclusively
 srun -w jet05 --exclusive --pty bash -i
 ```
 
-## MPI
+# MPI
 
 How to submit an MPI batch job
 
@@ -97,3 +103,21 @@ Submit with
 ```bash
 sbatch mpiexample.sh
 ```
+
+# Useful things
+
+
+## Information on the Job
+```
+sacct -j <JOBID>
+
+# Memory Used
+sacct -j <JOBID> --format=JobID,JobName,ReqMem,MaxRSS,Elapsed
+```
+
+## Send an Email Notification of your job:
+ALL, BEGIN, END, FAIL
+```
+#SBATCH --mail-type=BEGIN    # first have to state the type of event to occur 
+#SBATCH --mail-user=<email@address.at>   # and then your email address
+```