diff --git a/README.md b/README.md
index da0d55b7..dc9a3ea3 100644
--- a/README.md
+++ b/README.md
@@ -1702,7 +1702,7 @@ An overview of the architcture being simulated is presented below:
 For more spophisticated setups, even with l2 caches the proper ini file should be created.
 If you need help please contact Matthias Jung.
 
-### DRAMSys + GEM5 Log Collector Script
+### DRAMSys + GEM5 Log Collector Scripts
 
 Users can profit of running multiple **DRAMSys + gem5 simulations**
 automatically with
@@ -1714,9 +1714,9 @@ syscall emulation (SE) mode** and
 Normally you will have to push your changes before running the scripts. This
 approach makes it easier to track back what exactly was tested by the scripts.
 
-In the scripts there are variables to tell **git** where to get the source
-code from (the repository URL), user name to be used by git (from your git
-account), **branch** (your working branch), etc. The variable are:
+The scripts provide variables that tell **git** where to get the source
+code from (repository URL), user name to be used (your git account),
+**branch** to checkout (your working branch), etc. They are:
 
 ```bash
 # Git info.
@@ -1729,16 +1729,17 @@ git_url_https="git.eit.uni-kl.de/ems/astdm/dram.sys.git"
 Open the script in QtCreator or another text editor of your choice and set the
 variables with values that fit your needs.
 
-Nevertheless, for some cases, you may want to have gem5 files out of the main
-repository (usually because they are too big to be added to the repository).
+Nevertheless, for some cases, you may want to have gem5 essential files out of
+the main repository (usually because they are too big to be added to the
+repository).
 
 For those cases uncomment and properly set the variable
 **external_inifile_path** in
-[gem5ilva_fs](DRAMSys/library/resources/scripts/DRAMSylva/gem5ilva.sh).
+[gem5ilva_fs](DRAMSys/library/resources/scripts/DRAMSylva/gem5ilva_fs.sh).
 
-This will allow you to use a gem5 **config.ini** file external to the
-repository. Note, however, that in this case it is up to you to keep track of
-your simulation files.
+This allows you to use a gem5 **config.ini** file external to the repository.
+Note, however, that in this case it is up to you to keep track of your
+simulation setup.
 
 **Hint:**
 [gem5.TnT](https://github.com/tukl-msd/gem5.TnT) provides convenience scripts