OTB-Continuous-Integration-platform.md

@@ -60,7 +60,7 @@ have more value for the developer:
 
 Note: the artifacts are kept only 24h on the Gitlab server
 
-## Q: Why some features are disabled when I push from my OTB fork?
+### Q: Why some features are disabled when I push from my OTB fork?
 
 First, you need an access to the Runners from main repository. You
 can request it when doing your first merge request. During code review, someone
@@ -91,7 +91,7 @@ project page. In the left sidebar, go to `Settings -> CI/CD -> Variables`. Then
 add a new variable with the token name and token value. For security reasons,
 it is advised to mask these variables.
 
-## Q: Can I get Docker build environments?
+### Q: Can I get Docker build environments?
 
 Yes, for Linux builds, we use Docker images to compile and test OTB. They are stored in a 
 [registry](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb-build-env/container_registry).
@@ -105,14 +105,14 @@ If you want to get one of these images, login to the registry with your Gitlab a
   docker pull registry.orfeo-toolbox.org/orfeotoolbox/otb-build-env/...
 ```
 
-## Q: What about baseline files?
+### Q: What about baseline files?
 
 They are now stored in the main OTB repository, under
 `Data` folder. You can update them with a plain commit on your feature branch.
 Note that the data files are tracked with [Git LFS](https://git-lfs.github.com/)
 , so you need to install this extension.
 
-## Q: How do I get a test result back from CI?
+### Q: How do I get a test result back from CI?
 
 You have a failing test and you want to analyse the output. Here is how you can do it: