# HG changeset patch
# User vittorio.giovara@gmail.com
# Date 1361021538 0
# Node ID b85a981d439f7d50247b69a7bc9304cd194e69cb
# Parent  e0da7bf566b6aa99d1842b02dcb9984144f4f62f
typo and escapes

diff -r e0da7bf566b6 -r b85a981d439f TODO.wiki
--- a/TODO.wiki	Sat Feb 16 13:29:37 2013 +0000
+++ b/TODO.wiki	Sat Feb 16 13:32:18 2013 +0000
@@ -11,15 +11,15 @@
 
 = Easy Hacks =
 
-Just want to get your hands dirty? Pick one of your choise!
+Just want to get your hands dirty? Pick one of your choice!
 
-  * Perform some code cleanup, engine and frontend really need some! Grep for TODO and FIXME and you'll find plenty of examples. File loading, image flag handling and various little improvements just wait for you.
+  * Perform some code cleanup, engine and frontend really need some! `Grep` for TODO and FIXME and you'll find plenty of examples. File loading, image flag handling and various little improvements just wait for you.
   * Make our AI use any weapon of your choice. Check out the uAI`*`.pas files and see how the current weapons are handled.
-  * Write a simple shell script (bash, ruby, perl, python, awk...) to update the localization strings for iOS and propagate the diff to all the localized files. This task doesn't require coding or having an i-Device, just basic shell scripting.
-  * Make a cross-platform tool (for instance a script) that identifies new phrases in our mission, traning and gameplay scripts and adds them (marked untranslated) into our lua locaization files.
+  * Write a simple shell script (`bash`, `ruby`, `perl`, `python`, `awk`...) to update the localization strings for iOS and propagate the diff to all the localized files. This task doesn't require coding or having an i-Device, just basic shell scripting.
+  * Make a cross-platform tool (for instance a script) that identifies new phrases in our mission, training and gameplay scripts and adds them (marked untranslated) into our `Lua` localization files.
   * Drop a shadow effect to every widget in our frontend. This will help you: http://doc.qt.nokia.com/stable/qgraphicsdropshadoweffect.html
-  * Run valgrind on engine, report the  most used functions and optimize them so that performance increases.
-  * Use the Qt macro QtPrintable everywhere instead of looping through various string methods.
+  * Run `Valgrind` on engine, report the  most used functions and optimize them so that performance increases.
+  * Use the Qt macro `QtPrintable` everywhere instead of looping through various string methods.
   * Document compiler flags: just add a little comment near each flag explaining its use.
   * Document video flags, in video recording section.
 
@@ -33,7 +33,7 @@
 
 
 == Tools ==
-  * Refactor the frontend networking layer into library calls from hwengine, in a similar fashion to what's done on iOS and Android, using QT framebuffers.
+  * Refactor the frontend networking layer into library calls from hwengine, in a similar fashion to what's done on iOS and Android, using Qt framebuffers.
   * Create an easy-to-use theme editor, outlining all the necessary files for our themes.
   * Implement an handicap system allowing for increased difficulty on some teams instead of on the whole match.
   * If building server fails, try running the Cabal dependencies first.
@@ -46,7 +46,7 @@
   * Modify the drawn maps feature so that users can see a preview of what the admin is drawing.
   * Make the preferences that are modifiable from engine (eg. volume) update the ones specified in the frontend, using a new network message.
   * Rework the draw-map functions, adding different brush sizes, brush types and something new.
-  * Enable some commands while in frontend: for example /leave ( = /part  - for leaving room), /quit (disconnects from server), /exit (closes hedgewars), /addFriend, /removeFriend, /ignore, /unignore.
+  * Enable some commands while in frontend: for example `/leave` ( = `/part`  - for leaving room), `/quit` (disconnects from server), `/exit` (closes hedgewars), `/addFriend`, `/removeFriend`, `/ignore`, `/unignore`.
   * Add checkboxes for selecting the best rendering mode in addition to the Quality slider.
   * Lazy load previews, speed up frontend launch and compute previews only when necessary.
   * Rip out Fort mode, it's a game of its own and shouldn't be tied to the team preferences.
@@ -87,7 +87,7 @@
 == Various ==
 
   * Document the interaction of engine/frontend/server network protocol
-  * Document how the engine launches a game, from setting up the window, to updating the opengl renderer, from loading up contents, to cleaning up memory.
+  * Document how the engine launches a game, from setting up the window, to updating the OpenGL renderer, from loading up contents, to cleaning up memory.
   * Document the format of the demo and save files.