Advanced-Usage.md

-This page describes the advanced configuration options of the testsuite.
+This page describes the advanced configuration options of the testsuite and the various types of execution.
 
 ## Configuration
 
@@ -66,11 +66,11 @@ Use the default, unless you are working with a fork of alya
 ##### alya git repository url (https)
 Use the default, unless you are working with a fork of alya
 
-##### _Code coverage revision_
+##### Code coverage revision
 
 Type the revision used as a reference to do the code coverage. Type `master` or press enter for the last master commit.
 
-##### _MN login_
+##### MN login
 
 Type one the marenostrum login node among:
 
@@ -80,7 +80,7 @@ Type one the marenostrum login node among:
 
 If you press enter without typing anything, the default value `mn2.bsc.es` will be automatically selected.
 
-##### _P9 login_
+##### P9 login
 
 Same as for marenostrum, but this one for the p9 cluster. Chose between:
 
@@ -94,60 +94,42 @@ Note that you don't have access to p9 by default. We recommend you to ask the su
 
 Type the path on Marenostrum GPFS where the testsuite will be executed and the data generated. If the path does not exists, it will be created. By default, the path is `/gpfs/projects/bsc21/bscxxxxx/ts/name_of_your_machine`
 
-##### _Build job queue/Test job queue_
+##### Build job queue/Test job queue
 
 Here, you can define the queue for the build jobs (resp. the test jobs). Use bsc_case if possible, and debug only if you have a few jobs to run or if marenostrum is overloaded.
 
-### Partial configuration
-
-If you want to change a particular setting, you can run `./configure` using one of these options. Note that you can specify an option argument directly in the command line, or let it empty to enable the interactive mode.
-
-*  `-a  | --all                           ` Configure the main options
-*  `-r  | --re                            ` Reconfigure the main options
-*  `-A  | --ALL                           ` Configure all the options
-*  `-u  | --git-user         [git-user]   ` Set up the git user (gitlab/https user)
-*  `-e  | --email            [email]      ` Change the email
-*  `-as | --alya-svn         [path]       ` Set up alya svn repository path on mn
-*  `-ab | --alya-branch      [svn-branch] ` Select alya svn branch
-*  `-c  | --cc-ref           [git-commit] ` Define code coverage reference commit
-*  `-p  | --path             [path]       ` Change server path
-*  `-b  | --builds           [builds]     ` Change the set of builds
-*  `-bq | --build-queue      [queue]      ` Change the build queue
-*  `-tq | --test-queue       [queue]      ` Change the tests queue
-*  `-h  | --help                          ` Show this information
-
 ## Advanced runs
 
 ### Run only the builds
 
-```
+```sh
 ./ts build
 ```
 
 ### Run only the tests
 
-```
+```sh
 ./ts test
 ```
 You need to compile the builds in a previous step.
 
 ### Run only the code coverage
 
-```
+```sh
 ./ts cc
 ```
 You need to compile the builds and run the tests in previous steps. Only work with intel compiler builds.
 
 ### Send the report email
 
-```
+```sh
 ./ts email
 ```
 You need to compile the builds, run the tests and the code coverage in previous steps.
 
 ### Transmit the full report by email
 
-```
+```sh
 ./ts send jean.pierre@mail.com
 ```
 
@@ -157,10 +139,9 @@ The receiver will get a message with instructions about how to download the repo
 
 You can add the following options to `./ts tests` and `./ts all` using the following syntax:
 
-```
+```sh
 ./ts all --option argument1 argument2
 ```
 
-
-*  `-d  | --dirs [list of directories separated by space]         ` run only the tests included in these subdirectories. The root is `alya-tests`, so for a directoryt located in `alya-tests/example` you should specify `-d example`
+*  `-d  | --dirs [list of directories separated by space]         ` run only the tests included in these subdirectories
 *  `-t  | --tests [list of tests separated by space]              ` run only the tests included in this list.