FAQs.md

 [[_TOC_]]
 
-# EAR general questions
+## EAR general questions
 
 **Q: What is EAR?**
 
@@ -34,7 +34,7 @@ Depending on the programming model, EARL offers different features. Also, the ap
 
 EAR does not provide metrics at thread level at this moment. For hybrid applications, EAR will provide metrics for each MPI process. You can run OpenMP apps with EARL, but you'll get process metrics too.
 
-# Using EAR flags with SLURM plug-in
+## Using EAR flags with SLURM plug-in
 
 **Q: How to see EAR configuration and metrics at runtime?**
 
@@ -139,7 +139,7 @@ SLURM_EAR_TRACE_PLUGIN$EAR_INSTALL_PATH/lib/plugins/tracer/tracer_paraver.so
 SLURM_EAR_TRACE_PATH=TRACES_PARAVER/
 ```
 
-# Using additional MPI profiling libraries/tools
+## Using additional MPI profiling libraries/tools
 
 EAR uses the `LD_PRELOAD` mechanism to be loaded and the PMPI API for
 a transparent loading. In order to be compatible with other profiling libraries
@@ -147,7 +147,7 @@ EAR is not replacing the MPI symbols, it just calls the next symbol in the list.
 So it is compatible with other tools or profiling libraries. In case of conflict, the
 EARL can be disabled by setting `--ear=off` flag at submission time.
 
-# Jobs executed without the EAR Library: Basic Job accounting
+## Jobs executed without the EAR Library: Basic Job accounting
 
 For applications not executed with the EARL loaded (e.g., `srun` is not used or
 programming models or applications not loaded by default with EARL), EAR provides a default monitoring.
@@ -171,7 +171,7 @@ DC node energy includes the CPU and GPU energy if there are.
 These metrics are reported per node, Job and Step IDs, so they can be seen per
 job and job and step when using `eacct` command.
 
-# Troubleshooting
+## Troubleshooting
 
 
 **User asks for application metrics with `eacct` command and no information appears in some of the columns in the output.**