diff --git a/documentation/docs/fullsimlight/fsl/fslDemo.mov b/documentation/docs/fullsimlight/fsl/fslDemo.mov
new file mode 100644
index 0000000000000000000000000000000000000000..8824532d7c1a22b4ab774bb1d14703223ef142d0
Binary files /dev/null and b/documentation/docs/fullsimlight/fsl/fslDemo.mov differ
diff --git a/documentation/docs/fullsimlight/fsl/fsl_gmclashDemo.mov b/documentation/docs/fullsimlight/fsl/fsl_gmclashDemo.mov
new file mode 100644
index 0000000000000000000000000000000000000000..8c5da98ebcd2f174899e67540dc17d5b03c781a6
Binary files /dev/null and b/documentation/docs/fullsimlight/fsl/fsl_gmclashDemo.mov differ
diff --git a/documentation/docs/fullsimlight/fsl/index.md b/documentation/docs/fullsimlight/fsl/index.md
index 8e842685904ee679a8fdf86a8749e53354b55be7..197ed9a95141ffec2193c6b63cffe6c9b1ddb8bc 100644
--- a/documentation/docs/fullsimlight/fsl/index.md
+++ b/documentation/docs/fullsimlight/fsl/index.md
@@ -1,24 +1,30 @@
-# fsl
+# FullSimLight GUI: fsl
 
-fsl is a GUI for FullSimLight introduced in GeoModel release 4.3.0. It allows users to configure their simulations in FullSimLight easily and without conflicts by providing a series of tabs which offer various configuration options. It can be ran from the command line through the fsl command.
+`fsl` is a GUI for `fullSimLight` introduced in `GeoModel` release `4.3.0`. It allows users to configure their simulations in `fullSimLight` easily and without conflicts by providing a series of tabs which offer various configuration options. It can be ran from the command line through the `fsl` command.
 
 ```bash
 ./fsl
 ```
 
- Compatibility of the simulation is ensured by the fsl interface by enabling and disabling options based on the selections made. Once the user has configured the simulation to their desire, they can save the configuration in a json file that can be used to run FullSimLight through the -c flag. 
+ Compatibility of the simulation is ensured by the `fsl` interface by enabling and disabling options based on the selections made. Once the user has configured the simulation to their desire, they can save the configuration in a json file that can be used to run `fullSimLight` through the `-c` flag. 
  
 ```bash
 ./fullSimLight -c /path/to/config.json
 ```
  
-Alternatively the user can run FullSimLight at any time within fsl itself with the current configuration. fsl also allows users to load in previously saved configurations through the **Open Configuration** option. 
-One can also load in a configuration by running fsl with the -c flag.
+Alternatively, the user can run `fullSimLight` at any time within `fsl` itself with the current configuration. `fsl` also allows users to load in previously saved configurations through the `Open Configuration` option. 
+One can also load in a configuration by running `fsl` with the `-c` flag.
 
 ```bash
 ./fsl -c /path/to/config.json
 ```
 
+!!! Tip "Watch!"
+
+    Watch the following video for a quick demo on how to configure and launch `fullSimLight` with its GUI `fsl`! 
+
+    <video src="../fsl/fslDemo.mov" width="720" height="540" controls></video>
+
 
 ## Main Tab
 
@@ -36,9 +42,15 @@ The main tab allows configuration of the following parameters:
 - Physics List
 - Number of Threads
 - Number of Events
-- G4UI Verbosity Commands
+- `G4UI` Verbosity Commands
+
+It also contains the view button which shows the current configuration on the main display. The user can also run `fullSimLight` in the main display at any time with the current configuration by clicking on the `fullSimLight` button in the main tab. `fsl` provides similar buttons to run `gmex` and `gmclash` once a geometry input has been selected through the interface.
+
+!!! Tip "Watch!"
 
-It also contains the view button which shows the current configuration on the main display. The user can also run FullSimLight in the main display at any time with the current configuration by clicking on the FullSimLight button in the main tab. fsl provides similar buttons to run gmex and gmclash once a geometry input has been selected through the interface.
+    Watch the following video for a demo on how to easily run clash detection and visualize the clashing point together with the 3D geometry directly within `fsl`! 
+
+    <video src="../fsl/fsl_gmclashDemo.mov" width="720" height="540" controls></video>
 
 
 ## Generator Tab
@@ -54,28 +66,28 @@ It also contains the view button which shows the current configuration on the ma
 The generator tab shown above contains a list of event generators that can be selected for event generation. The options provided are:
 
 - Particle Gun
-- Pythia
-- HepMC3 File
+- `Pythia`
+- `HepMC3` File
 - Generator Plugin
 
 ### 1. Particle Gun
 
-To use a Geant4 particle gun, the user must specify the particle type and the momentum vector.
+To use a `Geant4` particle gun, the user must specify the particle type and the momentum vector.
 
 ### 2. Pythia
 
-To use Pythia one can select one of the pre-customized options which are
+To use `Pythia` one can select one of the pre-customized options which are
 
 - ttbar
 - higgs
 - minbias
 
 Details about the default options can be found in the `PythiaPrimaryGeneratorAction` [class](https://gitlab.cern.ch/GeoModelDev/GeoModel/-/blob/main/FullSimLight/src/PythiaPrimaryGeneratorAction.cc). 
-Alternatively one can also provide a custom Pythia configuration input file. 
+Alternatively one can also provide a custom `Pythia` configuration input file. 
 
 ### 3. HepMC3 File
 
-HepMC3 files containing events can be used in FullSimLight in both the standard Asciiv3 format (introduced in HepMC3) as well as the old Ascii format (used in HepMC and HepMC2).
+`HepMC3` files containing events can be used in `fullSimLight` in both the standard `Asciiv3` format (introduced in `HepMC3`) as well as the old `Ascii` format (used in `HepMC` and `HepMC2`).
 
 ### 4. Generator Plugin
 
@@ -91,7 +103,7 @@ In order to generate events one can also specify a plugin. Visit the [Plugin Sup
    urlFix=False) 
 }}
 
-To set a Magnetic Field, there are two options
+To set a Magnetic Field, there are two options:
 
 - Fixed Axial
 - Magnetic Field Plugin
@@ -103,7 +115,13 @@ Sets a constant Magnetic field in the z-direction at the specified magnitude.
 
 ### 2. Magnetic Field Plugin
 
-In order to generate a Magnetic Field one can also specify a plugin. Visit the [Plugin Support page](https://geomodel.web.cern.ch/home/fullsimlight/plugin-support/) for more details. A custom ATLAS Magnetic Field Plugin comes with the GeoModel package ready to use. This is automatically contained in the atlas-conf.json configuration file provided by GeoModel. ***Warning: This Plugin requires the ATLAS Magnetic Field Map to be installed in a standard location. This Map is available to all ATLAS users on request.***
+In order to generate a Magnetic Field one can also specify a plugin. Visit the [Plugin Support page](https://geomodel.web.cern.ch/home/fullsimlight/plugin-support/) for more details. 
+
+A custom ATLAS Magnetic Field Plugin comes with the `GeoModel` package ready to use with the ATLAS Extensions package. This is automatically contained in the `atlas-conf.json` configuration file provided by GeoModel. 
+
+!!! Warning
+ 
+    This Plugin requires the ATLAS Magnetic Field Map to be installed in a standard location. For more info visit the [Atlas Extensions](https://geomodel.web.cern.ch/home/fullsimlight/atlas-extensions/) page.
 
 
 ## Regions Tab
@@ -116,7 +134,7 @@ In order to generate a Magnetic Field one can also specify a plugin. Visit the [
    urlFix=False) 
 }}
 
-Geant4 regions can be added through the regions tab in FSL as shown above. For each region one must specify 
+`Geant4` regions can be added through the regions tab in `fsl` as shown above. For each region one must specify 
 
 - Region name
 - Root Logical Volumes
@@ -125,7 +143,7 @@ Geant4 regions can be added through the regions tab in FSL as shown above. For e
 - Positron cut (GeV)
 - Gamma cut (GeV)
 
-A list of ATLAS specific regions comes in the atlas-conf.json configuration file provided by GeoModel.
+A list of ATLAS specific regions comes in the `atlas-conf.json` configuration file provided by GeoModel.
 
 ## Sensitive Detectors Tab
 
@@ -137,7 +155,7 @@ A list of ATLAS specific regions comes in the atlas-conf.json configuration file
    urlFix=False) 
 }}
 
-In order to add Geant4 Sensitive Detectors one can create plugins which can then be added to the simulation through the menu shown above. Visit the [Plugin Support page](https://geomodel.web.cern.ch/home/fullsimlight/plugin-support/) for more details.
+In order to add `Geant4` Sensitive Detectors one can create plugins which can then be added to the simulation through the menu shown above. Visit the [Plugin Support page](https://geomodel.web.cern.ch/home/fullsimlight/plugin-support/) for more details.
 
 
 ## User Actions Tab
@@ -150,4 +168,4 @@ In order to add Geant4 Sensitive Detectors one can create plugins which can then
    urlFix=False) 
 }}
 
-In order to add Geant4 User Actions one can create plugins which can then be added to the simulation through the menu shown above. Visit the [Plugin Support page](https://geomodel.web.cern.ch/home/fullsimlight/plugin-support/) for more details.
+In order to add `Geant4` User Actions one can create plugins which can then be added to the simulation through the menu shown above. Visit the [Plugin Support page](https://geomodel.web.cern.ch/home/fullsimlight/plugin-support/) for more details.
diff --git a/documentation/docs/fullsimlight/fullsimlight/index.md b/documentation/docs/fullsimlight/fullsimlight/index.md
index 4a73278ae360f9a568a831ffb670995d25adb72c..5467a5e4521c77ba93ddda05cd1c15246f4b9340 100644
--- a/documentation/docs/fullsimlight/fullsimlight/index.md
+++ b/documentation/docs/fullsimlight/fullsimlight/index.md
@@ -1,47 +1,68 @@
 # FullSimLight
 
-FullSimLight package consists of different tools based on [Geant4](https://geant4.web.cern.ch) toolkit, that can be run on multiple geometries: 
+FullSimLight package consists of different tools based on the [Geant4](https://geant4.web.cern.ch) toolkit, that can be run on multiple geometries. It contains: 
 
-- **fullSimLight**: a light particle transport simulation (geometry, transport in magnetic field and basic physics scoring)
+- **fullSimLight**: a light `Geant4` particle transport simulation (geometry, transport in magnetic field and basic physics scoring)
 - **fsl**: GUI for fullSimLight configuration
 - **gmclash**: a tool that runs clash detection on your input geometry, producing a json file report
 - **gmgeantino**: a tool to generate geantino maps from your input geometry
 - **gmmasscalc**: a tool to compute the mass of a given piece of detector geometry
 - **gm2gdml**: a tool to convert geometries and dump them in gdml format.
 
-For instructions on how to build FullSimLight, please refer to the [Build FullSimLight ](https://geomodel.web.cern.ch/home/dev/build_fullsimlight/) page.
+For instructions on how to install FullSimLight from development kits please refer to the [Install library and tools section](https://geomodel.web.cern.ch/home/start/install/). If you are a developer and want to build FullSimLight from source code, please refer to the [Build FullSimLight ](https://geomodel.web.cern.ch/home/dev/build_fullsimlight/) page.
 For information on the specific tool please refer to the relevant section.
 
 ## FullSimLight: an experiment agnostic simulation tool
 
-`fullSimLight` is an experiment agnostic simulation tool that allows to easily run `Geant4` simulations by supporting multiple detector description formats (.gdml, plugins .dylib/.so,.db). It provides extended functionality by allowing the user to customise their simulation adding Geant4 User Actions, Sensitive Detectors, Physics Lists, Particle generators, etc. A built-in visualization for `fullSimLight` output is available in gmex (the interactive 3D geometry visualization tool which is part of GeoModel). As an example the following figures can be seen. 
+`fullSimLight` is an experiment agnostic simulation tool that allows to easily run `Geant4` simulations by supporting multiple detector description formats (.gdml, plugins .dylib/.so,.db). It provides extended functionality by allowing the user to customise their simulation adding customized `Geant4` User Actions, Sensitive Detectors, specialised Physics Lists, custom particle generators, etc. These flexibility is provided through the mechanism of plugins which come in the form of shared libraries (.dylib or .so) containing user custom code. 
+
+A built-in visualization for `fullSimLight` output is available in [gmex](https://geomodel.web.cern.ch/home/components/geomodelvisualization/gmex/) (the interactive 3D geometry visualization tool which is part of GeoModel). HITS steps and tracks generated with `fullSimLight` can be fed into `gmex`and consequently visualised. As an example the following figures can be seen. Figure 1 shows a HITS steps display of events transported with `fullSimLight` in the full ATLAS detector.
 
 {{ imgutils_image_caption('StepDisplay.png', 
    alt='StepDisplay', 
-   cap='Figure 1: Steps Display of primaries transported with fullSimLight in the full ATLAS detector.',
+   cap='Figure 1: Steps display of events transported with fullSimLight in the full ATLAS detector.',
    urlFix=False) 
 }}
 
+Figure 2 shows a HITS tracks display of events transported with `fullSimLight` in the full ATLAS detector.
+
 {{ imgutils_image_caption('TrackDisplay.png', 
    alt='TrackDisplay', 
-   cap='Figure 2: Track Display of primaries transported with fullSimLight in the full ATLAS detector.',
+   cap='Figure 2: Track display of primaries transported with fullSimLight in the full ATLAS detector.',
    urlFix=False) 
 }}
 
 
+## FullSimLight: run and main components
 
-## FullSimLight: run and options
 
+`fullSimLight` can be built and used both with sequential and multithreaded `Geant4` builds. In case of multithreaded installation of `Geant4`, the application will run in proper multithreaded mode. You can find the executables under the `build/bin` directory and/or under the `<path-to-install>/bin` dir. 
 
-`fullSimLight` can be built and used both with sequential and multithreaded `Geant4` builds. In case of multithreaded Geant4 toolkit, the applications will run in proper multithreaded mode. You can find the executables under the build/bin directory and/or under the *<  path-to-install > /bin* dir. 
+!!! note
 
-NB: Before running fullSimLight make sure to source the *geant4.sh* file to set correctly all the Geant4 environment variables. 
+    Before running fullSimLight make sure to source the *geant4.sh* file to set correctly all the Geant4 environment variables. 
+   
+    ```
+    source <path_to_geant4_install_dir>/bin/geant4.sh
+    ```
 
-```bash
-source <path_to_geant4_install_dir>/bin/geant4.sh
-```
 
-To run `fullSimLight` you can specify a json configuration file (generated with `fsl`) with the -c flag or use the following command line parameters. Run the executable with the --help option to see the available options:
+`fullSimLight` can be configured in multiple ways (using `fsl` generated json configuration files or the `Geant4` macro files) and run either from the command line or within `fsl`.
+
+
+## Configure and run fullSimLigth with its GUI fsl
+
+`fullSimLight` can be very easily configured and run via `fsl`, both from within the GUI or from the command-line, passing a json configuration file with the `-c` flag. Watch the following video for a quick demo on how to configure and launch `fullSimLight` with its GUI `fsl`! 
+
+<video src="../fsl/fslDemo.mov" width="720" height="540" controls></video>
+
+For details on how to configure your simulation with `fsl` GUI, please refer to the [fsl page](https://geomodel.web.cern.ch/home/fullsimlight/fsl).
+
+## Run fullSimLigth from the command line
+
+Alternatively, `fullSimLight` can be executed via command line using the basic available flags. The only mandatory parameter necessary for starting a simulation is the geometry file. It can be specified inside the config file or with the `-g` flag.  
+
+Run the executable with the --help option to see the available options:
 
 ``` bash
 -c :   [OPTIONAL] : json configuration file generated with fsl
@@ -50,23 +71,21 @@ To run `fullSimLight` you can specify a json configuration file (generated with
 -o :   flag  ==> run the geometry overlap check (default: FALSE)
 -f :   physics list name (default: FTFP_BERT) 
 -P :   [OPTIONAL] :use Pythia primary generator [config. available: ttbar/higgs/minbias or use a Pythia command input file]
--p :   [OPTIONAL] :flag  ==> run the application in performance mode i.e. no user actions 
-   :   -     ==> run the application in NON performance mode i.e. with user actions (default) 
 ``` 
+Please refer to the [Command line examples](#command-line-examples) section for some examples that illustrate the different possibilities.
 
-## Parameters configuration via fsl (suggested) 
-For details on how to configure your simulation with `fsl` GUI, please refer to the [fsl page](https://geomodel.web.cern.ch/home/fullsimlight/fsl).
-
+### Parameters configuration via Geant4 macro (disfauvored)
 
-## Parameters configuration via Geant4 macro (deprecated)
+`fullSimLight` and in general `Geant4` based simulations, need a `Geant4` macro to inject some input parameters. The default macro used by `fullSimLight` is called `macro.g4` and it should  be found under the `<install-path>/share/FullSimLight` directory. The macro can be edited to change some parameters, i.e the `Geant4` verbosity, the number of threads, or to tune the simulation. The most relevant macro commands are explained in the sections [Particle gun](#particle-gun) and [Magnetic field](#magnetic-field).
 
-`fullSimLight` and in general Geant4 based simulations, need a Geant4 macro to read some input parameters. The default macro used by fullSimLight is called 'macro.g4' and it should  be found under the *<  install-path > /share/FullSimLight* directory. The macro can be edited to change some parameters, i.e the verbosity, the number of threads, or to tune the simulation. The most relevant macro commands are explained in section [Particle gun](#particle-gun) and [Magnetic field](#magnetic-field)
+Please note that this option is deprecated, as it doesn't allow full flexibility, and we suggest to configure your simulation via `fsl`.
 
 
 ## Detector Construction
 
-The supported geometry formats are SQLite (.db), GDML (.gdml) and plugins that build from scratch a GeoModel geometry (.dylib/.so). An example of geometry plugins can be found in the [GeoModelExamples folder](https://gitlab.cern.ch/GeoModelDev/GeoModel/-/tree/main/GeoModelExamples/KitchenSinkPlugin). 
-Use the -g flag to specify the name of the input geometry file. 
+The supported geometry formats are SQLite (.db), GDML (.gdml) and plugins compiled as shared libraries (.dylib/.so) that contains the C++ code that builds from scratch a GeoModel geometry. An example of geometry plugin can be found in the GeoModelExamples folder and it is the so-called [KitchenSinkPlugin](https://gitlab.cern.ch/GeoModelDev/GeoModel/-/tree/main/GeoModelExamples/KitchenSinkPlugin).
+
+Use the `-g` flag to specify the name of the input geometry file.
 
 ### ATLAS Geometry Files
 
@@ -74,14 +93,15 @@ If you are interested in running with the ATLAS geometry files, please refer to
 
 ## Event generation
 
-`fullSimLight` uses by default the `Geant4` particle gun as primary generator, but it supports also
-input events from the [Pythia generator](http://home.thep.lu.se/Pythia/), [HepMC3](https://gitlab.cern.ch/hepmc/HepMC3) formats or custom generators plugins.
+`fullSimLight` uses by default the `Geant4` particle gun as primary generator. In addition, it supports also
+input events from the [Pythia](http://home.thep.lu.se/Pythia/) generator, [HepMC3](https://gitlab.cern.ch/hepmc/HepMC3) formats or custom event generators plugins.
 
 
 ### Particle gun
  
- The particle gun used by default  will generate primary particles
- at the (0,0,0) position with the following options:
+The particle gun can be tuned either via `fsl` or by editing the `Geant4` macro file. The default configuration of the `macro.g4` file will generate 10 GeV primary particles (randomly chosen between e-,e+ and gammas) at the (0,0,0) position with isotropic momentum direction. 
+
+Following are the UI commands that can be used to tune the `fullSimLight` particle gun.
 
 #### Number of primaries per event:
 The number of primary particles per event can be set through the macro
@@ -120,24 +140,53 @@ By default, i.e. if it is not specified by the above command, the type will be r
 
 ### Pythia generator
  
- `fullSimLight` supports Pythia as primary particles generator. In order to use Pythia, the user should have it installed in their system and if Pythia is found `fullSimLight` will be compiled with the support on. There are three different default options available when using the -P or --pythia flag (i.e. *ttbar*, *higgs* and *minbias*):
+ `fullSimLight` supports `Pythia` as primary particles generator. In order to use `Pythia`, the user should have it installed in their system and if `Pythia` is found `fullSimLight` will be compiled with its support activated. 
  
-  ``` bash
- -P :   generate events with Pythia [config. available: ttbar/higgs/minbias or use ascii input file]
- ``` 
+ In order to specify that `fullSimLight` has o run with `Pythia` event, the `-P` or `--pythia` flag has to be used.
+ Three different default options are available to run with `Pythia` events: `ttbar`, `higgs` and `minbias`:
  
- Alternatively the user can plug their own Pythia configuration file to simulate the desired events. 
- For example, in order to simulate the default *ttbar* events, the command to be run is the following:
+``` bash
+ -P :   generate events with Pythia [config. available: ttbar/higgs/minbias or use ascii input file]
+``` 
+
+The default configurations are currently defined as follows:
+``` bash
+
+static const char *pythia_minbias[] = {
+  "HardQCD:all = on",
+  "Beams:eCM = 13000.0",
+  "PhaseSpace:pTHatMin = 20.0",
+};
+
+static const char *pythia_higgs[] = {
+  "HiggsSM:all = on",
+  "Beams:eCM = 13000.0",
+  "PhaseSpace:pTHatMin = 20.0",
+};
+
+static const char *pythia_ttbar[] = {
+  "Top:gg2ttbar = on",
+  "Top:qqbar2ttbar = on",
+  "Beams:eCM = 13000.0",
+  "PhaseSpace:pTHatMin = 20.0",
+};
+
+```
+For example, in order to simulate the default *ttbar* events, the command to be run is the following:
  
- ``` bash
+```bash
+
 ./fullSimLight -m ../share/FullSimLight/pythia.g4 -P ttbar -g mygeometry.db 
- ``` 
+
+```  
  
- The number of events that the user wants to simulate must be specified in the Geant4 macro file. A specific *pythia.g4* macro file can be found in the *<  path-to-install >/share/FullSimLight* directory, that should be used when simulating Pythia events and can be edited according to the user needs. 
+Alternatively, the user can plug their own Pythia configuration file to simulate the desired events. 
+ 
+ The number of events that the user wants to simulate must be specified in a `Geant4` macro file. A specific `pythia.g4` macro file can be found in the `<path-to-install>/share/FullSimLight` directory. It should be used when simulating `Pythia` events and can be edited according to the user needs. 
  
 ### HepMC3 events input
 
-`fullSimLight` supports reading events in HepMC3 format both the standard Asciiv3 format (introduced in HepMC3) as well as the old Ascii format (used in HepMC and HepMC2). This option is only available when configuring fullSimLight with FSL and the json configuration file. Please refer to the [FSL section](https://geomodel.web.cern.ch/home/fullsimlight/fsl/) for more info. 
+`fullSimLight` supports reading events in `HepMC3` format both the standard Asciiv3 format (introduced in `HepMC3`) as well as the old `Ascii` format (used in `HepMC` and `HepMC2`). This option is only available when configuring `fullSimLight` with `fsl` and the json configuration file. Please refer to the [FSL](https://geomodel.web.cern.ch/home/fullsimlight/fsl/) section for more info. 
 
 ## Magnetic field
  
@@ -187,10 +236,10 @@ If you are interested in running with the ATLAS magnetic field map, please refer
 
 ## Physics List
 
- The Physics List can be specified as an input argument with the -f flag
- (e.g. -f FTFP_BERT). Notice that the name of the Geant4 built in Physics List
+ The Physics List can be specified as an input argument with the `-f` flag
+ (e.g. `-f FTFP_BERT_ATL`). Notice that the name of the `Geant4` built in Physics List
  must be in upper case, exactly as the corresponding header file. By default,
- i.e. if the Physics List name is not provided as an input argument, the FTFP_BERT
+ i.e. if the Physics List name is not provided as an input argument, the `FTFP_BERT`
  Physics List will be used.  
 
 ## Scoring
@@ -200,50 +249,79 @@ particle type: mean energy deposit, mean charged and neutral step lengths,
 mean number of steps made by charged and neutral particles, mean number of
 secondary e-, e+ and gamma particles. The result is reported at the end of
 each event for each primary particle that was transported in the given event.
+
 At the end of the simulation a final report is printed showing the run time,
 the primary generator and magnetic field settings used during the run, the
 total number of events and primary particles transported and the per-primary
 type simulation statistics of the above-mentioned quantities.
 
-The simulation can be executed in "performance" mode by providing the -p
-input flag. No any user actions are created in this case beyond the
-only one RunAction (only for the Master-thread in case of MT) that will
-start and stop a timer at the beginning and the end of the simulation
-(initialization time won't be included). Therefore, there is no scoring
-in this case.
+Please see the following output as an example:
+ 
+``` bash
+=======================================================================================  
+   Run terminated:                                                                         
+     Number of events transported    = 10
+     Time:  User=0.020000s Real=0.021719s Sys=0.000000s [Cpu=92.1%]
+  =======================================================================================  
+ 
+ ==================================   Run summary   ===================================== 
 
-## Examples
+    Number of events  = 10
+ 
+ ---------------------------------------------------------------------------------------- 
 
-`fullSimLight` can be very easily configured and run via `fsl`, both from within the GUI or from the command-line, passing the configuration file with the -c flag. Alternatively, `fullSimLight` can be executed via command line using the basic available flags. The only mandatory parameter necessary for starting a simulation is the geometry file (can be specified inside the config file or with the -g flag). Following are some examples that illustrates the different possibilities. 
+  Mean energy deposit per event = 0.01572 +- 0.01243 [GeV]
 
-If you have created your custom configuration file <myconfig.json> with fsl, you can simply run fullSimLight as follows:
+  Mean track length (charged) per event = 67.77 +- 43.66 [cm]
+  Mean track length (neutral) per event = 154.9 +- 113.1 [cm]
+
+  Number of steps (charged) per event = 303.2 +- 215.3
+  Number of steps (neutral) per event = 348.3 +- 255.9
+
+  Number of secondaries per event : 
+     Gammas    =  5.3 +- 4.649
+     Electrons =  11.4 +- 9.78
+     Positrons =  0.3 +- 0.4583
+```
+
+
+<!--The simulation can be executed in "performance" mode by providing the -p-->
+<!--input flag. No any user actions are created in this case beyond the-->
+<!--only one RunAction (only for the Master-thread in case of MT) that will-->
+<!--start and stop a timer at the beginning and the end of the simulation-->
+<!--(initialization time won't be included). Therefore, there is no scoring-->
+<!--in this case.-->
+
+
+
+## Command line examples
+
+If you have created your custom configuration file `myconfig.json` with `fsl`, you can simply run fullSimLight as it follows:
 
 ``` bash
 ./fullSimLight -c myconfig.json  
 ``` 
 This is the best and more complete way of configuring `fullSimLight` because it allows you to customize also the use of plugins and to use all the different primary particles generation methods.
 
-As an alternative to using the json configuration file, one can use the available command line options and a classical geant4 macro to configure fullsimlight. 
+As an alternative to using the json configuration file, one can use the available command line options and a classical geant4 macro to configure `fullSimLight`. 
 
-During the installation a default macro file *<macro.g4>* will be installed in your *< install-path >/share/FullSimLight* directory. So the macro file doesn't need to be specified if you intend to use the default one.
+During the installation of FullSimLight a default macro file `macro.g4` will be installed in your `<install-path >/share/FullSimLight` directory. The macro file doesn't need to be specified if you intend to use the default one.
 
-To execute the application using the default < macro.g4 >  macro file, with the default FTFP_BERT
-Physics List, not in performance mode and building the detector from < mygeometry.db > file:
+To execute the application using the default `macro.g4`  macro file, with the default FTFP_BERT
+Physics List, building the detector from `mygeometry.db` file:
 
 ``` bash
 ./fullSimLight -g mygeometry.db
 ```
 
-To execute the application using the default <  macro.g4 >  macro file and building the detector with a geometry described in one of the [GeoModelPlugins repo](https://gitlab.cern.ch/atlas/geomodelatlas/GeoModelATLAS/-/tree/master/GeoModelPlugins?ref_type=heads), i.e.  *PixelPlugin* :
+To execute the application using the default `macro.g4`  macro file and building the detector with a geometry described in one of the [GeoModelPlugins repo](https://gitlab.cern.ch/atlas/geomodelatlas/GeoModelATLAS/-/tree/master/GeoModelPlugins?ref_type=heads), i.e.  `PixelPlugin` :
 
 ``` bash
 ./fullSimLight  -g libPixePlugin.1.0.0.dylib/.so
 ```
 
-To execute the application using a custom <mymacro.g4> macro file, with the ATLAS FTFP_BERT_ATL Physics List, in performance mode and building the detector from the <mygeometry.db>  file :
+To execute the application using a custom `mymacro.g4` macro file, with the ATLAS `FTFP_BERT_ATL` Physics List, with `Pythia` ttbar as primary events and building the detector from the `mygeometry.db`  file :
 
 ``` bash
-./fullSimLight -m mymacro.g4 -f FTFP_BERT_ATL -p -g mygeometry.db 
-``` s
-
-Please note that the last option is deprecated, as it doesn't allow full flexibility, and we suggest to configure your simulation via `fsl`.
+./fullSimLight -m mymacro.g4 -f FTFP_BERT_ATL -P ttbar -g mygeometry.db 
+```