diff --git a/README.md b/README.md
index 14cc205b..d400836e 100644
--- a/README.md
+++ b/README.md
@@ -1448,31 +1448,31 @@ Optionally, use the scripts from [gem5.TnT](https://github.com/tukl-msd/gem5.TnT
 In order to understand the SystemC coupling with gem5 it is recommended to
 read the documentation in the gem5 repository *util/tlm/README* and [12].
 
-The main steps for building gem5 with SystemC are:
+The main steps for building gem5 and libgem5 follow:
 
 ``` bash
 scons build/ARM/gem5.opt
-scons --with-cxx-config --without-python build/ARM/libgem5_opt.so
-cd util/tlm
+```
+
+``` bash
+scons --with-cxx-config --without-python --without-tcmalloc build/ARM/libgem5_opt.so
 ```
 
 For MacOS:
 
 ``` bash
-scons build/ARM/gem5.opt
-scons --with-cxx-config --without-python build/ARM/libgem5_opt.dylib
-cd util/tlm
+scons --with-cxx-config --without-python --without-tcmalloc build/ARM/libgem5_opt.dylib
 ```
 
-In order to use gem5 with DRAMSys set the **GEM5** environment variable to the path
-to gem5, for example in the QtCreator under Projects > Build & Run > Build
-Environment:
+In order to use gem5 with DRAMSys set the **GEM5** environment variable to the
+path to gem5, for example in the *QtCreator under Projects > Build
+& Run > Build Environment*:
 
 ```
 GEM5=/path/to/gem5/
 ```
 
-optionally, export environment variables in your **~/.bashrc** file or
+Optionally, export environment variables in your **~/.bashrc** file or
 equivalent and open a new terminal:
 
 ```
@@ -1491,7 +1491,7 @@ the corresponding build target **gem5** for QtCreator.
 
 In order to run gem5 with DRAMSys it is mandatory to run gem5 first without
 DRAMSys and generate a configuration file **config.ini** which will be the
-value of the second parameter to DRAMSys_gem5.
+value of the second parameter passed to DRAMSys_gem5.
 
 ### DRAMSys with gem5 traffic generator
 
@@ -1544,7 +1544,7 @@ Then the simulation can be started with:
 ```
 
 Lets run the simulation for some seconds and then stop the simulation with
-ctrl+c.  Observe the output of the simulation in the trace analyzer. The trace
+**CTRL-C**.  Observe the output of the simulation in the trace analyzer. The trace
 database file is stored in the gem5 directory in the building directory.
 
 ### Boot Linux with gem5 and DRAMSys
@@ -1602,22 +1602,20 @@ The simconfig should be changed in order to support storage and address offsets:
 Then start DRAMSys_gem5 with the following command:
 
 ``` bash
-./DRAMSys_gem5 /Users/myzinsky/EMS/Programming/dram.vp.system/DRAMSys/library/resources/simulations/ddr3-example.xml config.ini
+./DRAMSys_gem5 ../../DRAMSys/library/resources/simulations/ddr3-example.xml config.ini
 ```
 
 For further sophisticated address mappings or scenarios checkout the file DRAMSys/gem5/main.cpp
 
 ### DRAMSys with gem5 Elastic Traces
 
-For understanding elastic traces and their generation, study the gem5 wiki
-(http://gem5.org/TraceCPU) and the paper [13].  Some predefined configs are
-stored in dram.vp.system/DRAMSys/gem5/configs and the related python files are
-stored here: dram.vp.system/DRAMSys/gem5/examples
+For understanding elastic traces and their generation, study the [gem5 wiki](http://gem5.org/TraceCPU) and the paper [13].
+Some predefined configs are stored [here](DRAMSys/gem5/configs) and the related python files are stored [here](DRAMSys/gem5/examples).
 
 This is an example for running an elastic trace:
 
 ``` bash
-./DRAMSys_gem5 /path/to/dram.vp.system/DRAMSys/library/resources/simulations/ddr3-example.xml ../../DRAMSys/gem5/configs/singleElasticTraceReplay.ini
+./DRAMSys_gem5 ../../DRAMSys/library/resources/simulations/ddr3-example.xml ../../DRAMSys/gem5/configs/singleElasticTraceReplay.ini
 ```
 
 Note that the address offset is usually zero for elastic traces.
@@ -1633,7 +1631,7 @@ If two elastic traces should be used the main.cpp must be modified:
 Run the simulation with the following example:
 
 ```
-./DRAMSys_gem5 /path/to/dram.vp.system/DRAMSys/library/resources/simulations/ddr3-example.xml ../../DRAMSys/gem5/configs/dualElasticTraceReplay.ini
+./DRAMSys_gem5 ../../DRAMSys/library/resources/simulations/ddr3-example.xml ../../DRAMSys/gem5/configs/dualElasticTraceReplay.ini
 ```
 
 For more spophisticated setups, even with l2 caches the proper ini file should be created.