EAR-environment-variables.md

@@ -81,7 +81,7 @@ export EAR_REPORT_ADD=my_report_plugin.so:my_report_plugin2.so
 srun -n 10 my_mpi_app
 ```
 
-For more information, see [Report plug-ins](https://gitlab.bsc.es/ear_team/ear/-/wikis/Report) section.
+For more information, see [Report plug-ins](https://gitlab.bsc.es/ear_team/ear_private/-/wikis/Report) section.
 
 ## Extended GPU metrics
 
@@ -171,7 +171,7 @@ the chance for a user to [fix it](#ear_max_imcfreq-and-ear_min_imcfreq) during a
 
 ### EAR\_SET\_IMCFREQ
 
-Enables/disables EAR's [eUFS](Home#publications) feature.
+Enables/disables EAR's [eUFS](https://gitlab.bsc.es/ear_team/ear/-/wikis/Home#publications) feature.
 Type `ear-info` to see whehter eUFS is enabled by default.
 
 You can control eUFS' maximum permitted time penalty by exporting `EAR_POLICY_IMC_TH`,
@@ -364,7 +364,7 @@ Moreover, this is the only way to set different priorities over different thread
 ## EAR\_MIN\_CPUFREQ
 
 This variable can only be set by **authorized users**, and modifies the minimum CPU frequency the EAR Library can set.
-The [EAR configuration](https://gitlab.bsc.es/ear_team/ear/-/wikis/Configuration) file has a field called `cpu_max_pstate` which sets this limits on the tag it is configured.
+The [EAR configuration](https://gitlab.bsc.es/ear_team/ear_private/-/wikis/Configuration) file has a field called `cpu_max_pstate` which sets this limits on the tag it is configured.
 Authorized users can modify this limit at submission time by using this environment to test, for example, the best value for the `ear.conf` field.
 
 ## Disabling EAR's affinity masks usage
@@ -510,7 +510,7 @@ srun -n 10 --ear=on ./mpi_app
 
 ## REPORT_EARL_EVENTS
 
-Use this variable (i.e., `export REPORT_EARL_EVENTS=1`) to make EARL send internal events to the [Database](https://gitlab.bsc.es/ear_team/ear/-/wikis/EAR-Database).
+Use this variable (i.e., `export REPORT_EARL_EVENTS=1`) to make EARL send internal events to the [Database](https://gitlab.bsc.es/ear_team/ear_private/-/wikis/EAR-Database).
 These events are useful to have more information about Library's behaviour, like
 when DynAIS **(REFERENCE DYNAIS)** is turned off, the computational phase EAR is guessing the application is on
 or the status of the applied policy **(REF POLICIES)**.