User-guide.md

@@ -101,8 +101,7 @@ You can read [here](https://www.intel.com/content/www/us/en/develop/documentatio
 For joining OpenMPI and EAR it is highly recommended to use SLURM's `srun` command.
 When using `mpirun`, as OpenMPI is not fully coordinated with the scheduler, EARL
 is not automatilly loaded on all nodes.
-Therefore EARL will be disabled and only [basic energy metrics](#jobs-executed-without-the-ear-library-basic-job-accounting)
-will be reported.
+Therefore EARL will be disabled and only basic energy metrics will be reported.
 To provide support for this workflow, EAR provides [`erun`](EAR-commands#erun) command.
 Read the corresponding [examples section](User-guide.md#openmpi-1) for more information about how to use this command.
 
@@ -200,7 +199,7 @@ mpirun -np 64 singularity exec $IMAGE $EAR_INSTALL_PATH/bin/erun \
     --program=$BENCH_PATH/bt-mz.D.64
 ```
 
-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.
+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`](https://gitlab.bsc.es/ear_team/ear/-/wikis/Report#sysfs-report-plugin) report plug-in.
 See [next section](#runtime-report-plug-ins) about report plug-ins.
 
 ## Using EARL through the COMPSs Framework 
@@ -244,11 +243,11 @@ 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`.
 
-Read [report plug-ins](Report) dedicated section for more information.
+Read [report plug-ins](https://gitlab.bsc.es/ear_team/ear/-/wikis/Report) dedicated section for more information.
 
 ## Other EARL events
 
-You can also request EAR to report **events** to the [Database](EAR-Databse).
+You can also request EAR to report **events** to the [Database](https://gitlab.bsc.es/ear_team/ear/-/wikis/EAR-Database).
 They show more details about EARL internal state and can be provided with `eacct` command.
 See how to enable [EAR events reporting](EAR-environment-variables#report_earl_events) and which kind of events EAR is reporting.
 
@@ -582,5 +581,5 @@ The core component of EAR at the user's job level is the EAR Library (EARL).
 The Library deals with job monitoring and is the component which implements and applies
 optimization policies based on monitored workload.
 
-**We highly recommend you** to read [EARL](EARL) documentation and also how energy policies work
+**We highly recommend you** to read [EARL](https://gitlab.bsc.es/ear_team/ear/-/wikis/Architecture#the-ear-library-job-manager) documentation and also how energy policies work
 in order to better understand what is doing the Library internally, so you will can explore easily all features (e.g., tunning variables, collecting data) EAR offers to the end-user so you will have more knowledge about how much resources your application consumes and how to correlate with its computational characteristics.