Home.md

 *TODO decide style conventions, write design best practices and start adding examples*
 
 ### First Steps
+* [Eclipse configuration (TODO)](https://github.com/skyward-er/skyward-boardcore/wiki/Eclipse-configuration)
 * [SBS Quick Guide](https://github.com/skyward-er/skyward-boardcore/wiki/SBS-Quick-Guide)
 * [Writing a Driver](https://github.com/skyward-er/skyward-boardcore/wiki/Writing-a-driver)
-* [Eclipse configuration (TODO)](https://github.com/skyward-er/skyward-boardcore/wiki/Eclipse-configuration)
 * [Flashing on a Discovery board](https://github.com/skyward-er/skyward-boardcore/wiki/Flashing-on-a-Discovery-board)
 * [Flashing on a Stormtrooper (TODO)](https://github.com/skyward-er/skyward-boardcore/wiki/Flashing-on-a-Stormtrooper)
 
@@ -11,7 +11,7 @@
 * [Code style and naming conventions (TODO)]()
 * [Git rules (TODO)](): branching like [this](http://nvie.com/posts/a-successful-git-branching-model/), commit messages style
 
-* Best Practices: *general design rules that you should follow in order to write bomb-proof code*
+* [Design Rules and Best Practices]: *general design rules that you should follow in order to write bomb-proof code*
 	- [Terraneo's examples on multi threading (TODO)]()
 	- [NASA coding principles](http://pixelscommander.com/wp-content/uploads/2014/12/P10.pdf) (revisited)
 
@@ -27,7 +27,7 @@ Examples
 	- profiling della memoria
 
 * [Cheat Sheet](https://github.com/skyward-er/skyward-boardcore/wiki/Cheat-Sheet): *Things that made us say "If only I knew that before!" (or worse)*
-        - USART read/write in Miosix
+	- USART read/write in Miosix
 	- Add another usart to a board 
 	- Use right amount of stack (printf!)
 	- Chiamare una funzione di un oggetto in un thread (wrapper statico)
\ No newline at end of file