versions.md

@@ -24,14 +24,14 @@ The aim of this section is to provide useful **guidelines** about the features t
   *  The user can specify a `datetime` or `time` when the **experiment should start** by sending the `-st` flag (plus the right format) using the `autosubmit run` command.
   *  The user can specify an **experiment dependency** by sending the `-sa` (plus the right expid format) using the `autosubmit run` command. The experiment will start when the experiment specified in the `-sa` flag finishes.
   *  When the user quits Autosubmit by using the `CTRL+C` keys, Autosubmit will make sure all threads are finished correctly before closing.
-  *  Job lifecycle information is stored in an **external database** that will allow the user to see the historical information of the execution of the jobs in her experiment. This information is gathered in a way that does not interfere with the normal workflow, even if the information gathering fails or any of its components. Furthermore, threading is implemented to prevent unnecessary delays.
-  *  **Specific members** can now be configured to run by using the `autosubmit run` together with the `-rm` command. By setting this flag, Autosubmit will only run jobs belonging to the supplied members. Jobs that were running before this command was sent, will be monitored and properly completed.
+  *  Job lifecycle information is stored in an **external database** that will allow users to visualize job historical information. This information is gathered in a way that does not interfere with the normal workflow (even if the information gathering fails or any of its components). Furthermore, threading is implemented to prevent unnecessary delays.
+  *  **Specific members** can be selected to run by using the `-rm` flag with `autosubmit run`. Autosubmit will only run jobs belonging to the specified members. Jobs already running will be monitored and properly completed.
   *  The `git clone` operation (`Autosubmit create`) now implements a **backup procedure** that will prevent loss of information in case of wrong configuration or network error.
   *  There is an improvement of the **security**, now all commands that could change the workflow are locked by an owner-only mechanism. Ej: create, refresh and run. 
   *  Added `autosubmit dbfix expid` command that allows users to fix the `database malformed` error.
-  *  Custom shebang (header of the script templates) so it is possible to use Python or R templates with a specific Python/R version dependency.
+  *  Custom **shebang** (header of the script templates) so it is possible to use Python or R templates with a specific Python/R version dependency.
   * **Workflow updates:** only `create` and `run` commands can regenerate the configuration, workflow, and structure information. In the case of `run`, they will only be updated if a change is detected before the starting of the main run loop. 
-  * **Robustness:** AS will try to prevent as many errors as possible at the beginning of the run and will handle other delicate operations before run time. 
+  * Increased **robustness**. AS will try to prevent as many errors as possible at the beginning of the run and will handle other delicate operations before run time. 
   * Allows prioritizing a list of jobs to be run before the rest of the workflow. Via the use of the Two_step_start variable set in expdef.conf
   * Allows skipping jobs under the same section if their last on queuing member/chunks is higher than other on queuing/waiting/ready