what-to-help.markdown

@@ -7,7 +7,8 @@ But even if you think you have not enough technical skill to deal directly with
 there are some task as much important you may do!
 
 
-## Hack the kernel
+Hack the kernel
+---------------
 This is the most evident kind of task : help us to improve the kernel code, to make it faster,
 smarter, more stable, or portable accross other hardware platforms.
 Of course, writing code for the kernel need to *master* at least the C language, and depending
@@ -17,7 +18,8 @@ of FiXos are really generics and do not deal at all with the hardware).
 More informations to be ready are available in the wiki : [Resources about kernel hacking](kernel-hacking) and [Some documentation of FiXos internals](fixos-internals).
 
 
-## Test it
+Test it
+---------------
 Writing a kernel which work well on a given platform is cool.
 Writing a kernel which work perfectly on **many** platforms is better!
 
@@ -25,7 +27,8 @@ If you think you have not enough time or skill to improve the kernel code direct
 would like to improve it *indirectly*, by testing and [reporting bugs](bug-reporting) to developers.
 
 
-## Improve documentation
+Improve documentation
+---------------
 Kernel documentation is *very* important, but at this time it really lacks.
 Helping us to create documentation, both for kernel and userspace hackers, and helping to correct and
 improve it is *not* less useful than writing code!
@@ -34,7 +37,8 @@ In addition, if English is your mother tongue and/or you feel confortable with i
 many things to correct in the documentation, in this wiki, and maybe elsewhere!
 
 
-## Hack the userspace!
+Hack the userspace!
+---------------
 Userspace is less delicate, and maybe more fun if you like to interract with the user instead of with the hardware.
 A kernel alone is as useless as a nice coffee cup without coffee (sorry, first analogy I found).