User-guide.md

@@ -201,16 +201,17 @@ mpirun -np 64 singularity exec $IMAGE $EAR_INSTALL_PATH/bin/erun \
 ```
 
 Note that the example exports `APPTAINERENV_EAR_REPORT_ADD` to set the environment variable [`EAR_REPORT_ADD`](EAR-environment-variables#report-plug-ins) to load [`sysfs`](Report#sysfs-report-plugin) report plug-in.
+See [next section](#runtime-report-plug-ins) about report plug-ins.
 
 # Retrieving EAR data
 
 As a job accounting and monitoring tool, EARL collects some metrics that you can
-get to see or know your applications behaviour.
+get to see or know your applications workload.
 The Library is doted with several modules and options to be able to provide different
 kind of information.
 
-As a very simple hint of your application workload, you can enable EARL verbosity (e.g., `--ear-verbose=1`) to get loop data at runtime.
-The information is shown at _stderr_ by default.
+As a very simple hint of your application workload, you can enable EARL verbosity (i.e., `--ear-verbose=1`) to get loop data at runtime.
+**The information is shown at _stderr_ by default.**
 Read how to set up verbosity at [submission time](ear-job-submission-flags) and
 [verbosity environment variables](EAR-environment-variables#verbosity) provided
 for a more advanced tunning of this EAR feature.
@@ -231,8 +232,7 @@ You can load this plug-in in two ways:
 1. By setting [`--ear-user-db`](#ear-job-submission-flags) flag at submission time.
 2. [Loading directly the report plug-in](EAR-environment-variables#ear_report_add) through an environment variable: `export EAR_REPORT_ADD=csv_ts.so`.
 
-> Contact with [ear-support@bsc.es](mailto:ear-support@bsc.es) for more information
-about report plug-ins.
+Read [report plug-ins](Report) dedicated section for more information.
 
 ## Other EARL events
 
@@ -274,7 +274,7 @@ with runtime collected metrics (loops node signatures).
 Read [`eacct`'s section](EAR-commands#ear-job-accounting-eacct) in the commands page to know which metrics are reported,
 as data generated by this flag is the same as the reported (and retrieved later by the command) to the Database.
 
-Verbose messages are placed by default in _stderr_.
+Verbose messages are placed by default at _stderr_.
 For jobs with multiple nodes, `ear-verbose` option can result in lots of messages
 mixed at _stderr_.
 We recommend to split up SLURM's output (or error) file per-node.