diff --git a/content/submitting_jobs/creating_an_interactive_job.md b/content/submitting_jobs/creating_an_interactive_job.md
index 1100a049883b84672e113bfef47f3dbe5846e841..2d9025354c48daf4fb7cabc7aef5b08cd6cab874 100644
--- a/content/submitting_jobs/creating_an_interactive_job.md
+++ b/content/submitting_jobs/creating_an_interactive_job.md
@@ -15,19 +15,20 @@ Submitting an interactive job is done with the command `srun`.
 $ srun --pty $SHELL
 {{< /highlight >}}
 
-or to allocate 4 cores per node:
+or to allocate 4 cores per node for 3 hours:
 
 {{< highlight bash >}}
-$ srun --nodes=1 --ntasks-per-node=4 --mem-per-cpu=1024 --pty $SHELL
+$ srun --nodes=1 --ntasks-per-node=4 --mem-per-cpu=1024 --time=3:00:00 --pty $SHELL
 {{< /highlight >}}
 
 Submitting an interactive job is useful if you require extra resources
 to run some processing by hand.  It is also very useful to debug your
 processing.  
 
-And interactive job is scheduled onto a worker node just like a regular
+An interactive job is scheduled onto a worker node just like a regular
 job.  You can provide options to the interactive job just as you would a
-regular SLURM job.
+regular SLURM job. The default job runtime is 1 hour, and can be
+increased by including the `--time` argument.
 
 ### Priority for short jobs