Doc updated

README.md

@@ -1026,8 +1026,9 @@ number of traces.
 
 ```bash
 traces="
-ddr3_example.stl
-mediabench-unepic_32.stl
+chstone-bf_32.stl
+chstone-jpeg_32.stl
+chstone-adpcm_32.stl
 "
 ```
 
@@ -1036,17 +1037,29 @@ The script runs one instance of DRAMSys for each of the files in the list.
 
 Set the variable **use_DRAMSyrup_to_generate_config_files** to **yes** in
 order to get all the essential simuation files auto generated from a
-description in JSON format loaded from
-[**configs.json**](DRAMSys/library/resources/scripts/DRAMSylva/configs.json).
+description in JSON format specified by the variable **json_file**. Several
+examples of JSON configuration files are provided in
+[**configs_json**](DRAMSys/library/resources/scripts/DRAMSylva/configs_json).
 **Note: this overrides sim_files**.
 
 ``` bash
 use_DRAMSyrup_to_generate_config_files="yes"
 ```
 
-+ Insert the desired simulation data in **configs.json**. Multiple arrays are
-  allowed and encouraged. Each array corresponds to a full simulation setup.
++ Insert the desired simulation data in a JSON file following any of the
+  examples provided, e.g.,
+  [**configs.json**](DRAMSys/library/resources/scripts/DRAMSylva/configs_json/configs.json).
+  Multiple arrays are allowed and encouraged. Each array corresponds to a full
+  simulation setup.
+
++ Assign your JSON file to the variable **json_file** in DRAMSylva.sh.
+
+``` bash
+json_file="configs.json"
+```
+
 + Commit and push your changes.
+
 + Run **DRAMSylva** as previously described. All generated files will be
   inside the output folder, so it will be possible to keep a perfect track of
   all simulations.