More links and some rewording

ResearchComputing · Oct 26, 2018 · 791a915 · 791a915
1 parent 32f53bc
commit 791a915
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/access/blanca.md b/docs/access/blanca.md
@@ -21,7 +21,7 @@ All jobs are run through a batch/queue system.  Interactive jobs on compute node
 
 Blanca uses a separate instance of the Slurm scheduling system from the other RC compute resources.  You can use Blanca’s Slurm instance by loading a special module on a login node: “module load slurm/blanca”.
 
-More details about how to use Slurm can be found [here](https://github.com/ResearchComputing/Research-Computing-User-Tutorials/wiki/Job-Submissions).
+More details about how to use Slurm can be found [here](../running-jobs/submission.html).
 
 ### QoS
 
@@ -124,7 +124,7 @@ Note that the interactive job won't start until the resources that it needs are
 ### Important notes
 
 1. To see what modules are available, start an interactive job on a compute node and use `module avail` or `module spider` on it.
-2. /home, /projects, and /work (PetaLibrary Active) are available on all Blanca nodes.  Scratch I/O can be written to /rc_scratch, which should offer much better performance than /projects.  All Blanca nodes also have at least 850 GB of scratch space on a local disk, /local/scratch.  For more info on the different RC storage spaces, please review https://www.colorado.edu/rc/resources/filesystemstorage
+2. /home, /projects, and /work (PetaLibrary Active) are available on all Blanca nodes.  Scratch I/O can be written to /rc_scratch, which should offer much better performance than /projects.  All Blanca nodes also have at least 850 GB of scratch space on a local disk, /local/scratch.  For more info on the different RC storage spaces, [please see our page on storage.](https://www.colorado.edu/rc/resources/filesystemstorage)
 3. There are no dedicated Blanca compile nodes.  To build software that will run on Blanca, start an interactive job on a node like the one on which you expect your jobs to run, and compile your software there.  Do not compile on the login nodes!
 4. Multi-node MPI jobs that do a lot of inter-process communication do not run well on most Blanca nodes because there is no high-performance low-latency inter-node network except on blanca-ccn.