Update building_software.md

Closes #93 (closed)

doc.zih.tu-dresden.de/docs/software/building_software.md

 # Building Software
 
 While it is possible to do short compilations on the login nodes, it is generally considered good
-practice to use a job for that, especially when using many parallel make processes. Note that
-starting on December 6th 2016, the `/projects` filesystem will be mounted read-only on all compute
+practice to use a job for that, especially when using many parallel make processes. Since 2016, 
+the `/projects` filesystem is mounted read-only on all compute
 nodes in order to prevent users from doing large I/O there (which is what the `/scratch` is for).
-In consequence, you cannot compile in `/projects` within a job anymore. If you wish to install
+In consequence, you cannot compile in `/projects` within a job. If you wish to install
 software for your project group anyway, you can use a build directory in the `/scratch` filesystem
-instead:
+instead.
 
 Every sane build system should allow you to keep your source code tree and your build directory
 separate, some even demand them to be different directories. Plus, you can set your installation
@@ -17,16 +17,16 @@ For instance, when using CMake and keeping your source in `/projects`, you could
 
 ```console
 # save path to your source directory:
-marie@login$ export SRCDIR=/projects/p_myproject/mysource
+marie@login$ export SRCDIR=/projects/p_marie/mysource
 
 # create a build directory in /scratch:
-marie@login$ mkdir /scratch/p_myproject/mysoftware_build
+marie@login$ mkdir /scratch/p_marie/mysoftware_build
 
 # change to build directory within /scratch:
-marie@login$ cd /scratch/p_myproject/mysoftware_build
+marie@login$ cd /scratch/p_marie/mysoftware_build
 
 # create Makefiles:
-marie@login$ cmake -DCMAKE_INSTALL_PREFIX=/projects/p_myproject/mysoftware $SRCDIR
+marie@login$ cmake -DCMAKE_INSTALL_PREFIX=/projects/p_marie/mysoftware $SRCDIR
 
 # build in a job:
 marie@login$ srun --mem-per-cpu=1500 --cpus-per-task=12 --pty make -j 12