EAR-Database.md

@@ -174,12 +174,12 @@ If no GPUs were being used but now are present, use the previous query plus the
 
 ## Database tables description
 
-EAR's database contains several tables, as described [here](EAR-Database.md#tables). Each table contains different information, as described here:
+EAR's database contains several tables, as described [here](#tables). Each table contains different information, as described here:
 
 ### Jobs
 
-* <span dir="">id: Job id given by the scheduler (for example SLURM_JOBID).</span>
-* <span dir="">step_id: step id given by the scheduler.</span>
+* <span dir="">id: Job id given by the scheduler (for example SLURM\_JOBID).</span>
+* <span dir="">step\_id: step id given by the scheduler.</span>
 * user_id: the linux username that executed the job.
 * app_id: the application/job name as given by the scheduler (not necessarily the executable’s name)
 * start_time: timestamp of the job’s\[.step\] start