Developers/contribute-to-Scilab.md

 _This page describes how to contribute to Scilab using_ [_Forking workflow_](https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html) and [_Merge requests_](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)_. You should previously have set up a Gitlab account and a_ [_Scilab repository_](Developers/setup-Scilab-repository).
 
+[[_TOC_]]
+
+# Create & configure your fork & your clone
+
 As a first step, ensure to work on a public fork named `$USER/scilab` by clicking the [Fork button](https://gitlab.com/scilab/scilab/-/forks/new). Be sure to have its visibility set to **Public**.
 
 Execute these lines to get your fork and add the Scilab git repository as a remote named "upstream". This remote will be used to follow activity on the development version.
@@ -10,6 +14,8 @@ cd scilab
 git remote add upstream git@gitlab.com:scilab/scilab.git
 ```
 
+# Make your changes available to others
+
 Before making your changes available to others, name them consistently as defined in [Gitlab flow](https://docs.gitlab.com/ee/topics/gitlab_flow.html). If possible include the module name `xcos-add-a-play-button` or issue number `fix-issue-1821`.
 
 ```
@@ -49,7 +55,9 @@ git push --force
 
 **Note:** Don't panic if you forgot to create a merge request! Try to navigate in the GitLab web interface and you will probably be able to create a merge request from Branches, Merge requests or other views.
 
-Best practice to keep your fork clean:
+# Keep your fork clean
+
+Best practice to keep your fork clean and up-to-date:
 
 - Never commit/push to 6.1 branch
 - Regularly rebase your fork: