what-to-help.markdown

@@ -6,7 +6,9 @@ If you feel you are a kernel hacker, its great!
 But even if you think you have not enough technical skill to deal directly with the kernel code,
 there are some task as much important you may do!
 
+
 ## 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,6 +19,7 @@ More informations to be ready are available in the wiki : [Resources about kerne
 
 
 ## 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,6 +28,7 @@ would like to improve it *indirectly*, by testing and [reporting bugs](bug-repor
 
 
 ## 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,6 +38,7 @@ many things to correct in the documentation, in this wiki, and maybe elsewhere!
 
 
 ## 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).