Merge pull request codeguy#477 from dericofilho/gh-pages

Adding php.tools as suggestion for tools to format source code

_posts/02-01-01-Code-Style-Guide.md

@@ -29,8 +29,11 @@ and applications that implement the components can have consistency even when wo
 You can use [PHP_CodeSniffer][phpcs] to check code against any one of these recommendations, and plugins for text editors 
 like [Sublime Text 2][st-cs] to be given real time feedback. 
 
-Use Fabien Potencier's [PHP Coding Standards Fixer][phpcsfixer] to automatically modify your code syntax so that it
-conforms to these standards, saving you from fixing each problem by hand.
+You can fix the code layout automatically by using one of the two possible tools. One is Fabien Potencier's
+[PHP Coding Standards Fixer][phpcsfixer] which has a very well tested codebase. It is bigger and slower, but very stable
+and used by some huge projects like Magento and Symfony. Another option is [php.tools][phptools], which is made popular
+by the [sublime-phpfmt][sublime-phpfmt] editor plugin. While being newer, it makes great improvements in performance,
+meaning real-time editor fixing is more fluid.
 
 English is preferred for all symbol names and code infrastructure. Comments may be written in any language easily readable 
 by all current and future parties who may be working on the codebase.
@@ -46,3 +49,5 @@ by all current and future parties who may be working on the codebase.
 [phpcs]: http://pear.php.net/package/PHP_CodeSniffer/
 [st-cs]: https://github.com/benmatselby/sublime-phpcs
 [phpcsfixer]: http://cs.sensiolabs.org/
+[phptools]: https://github.com/dericofilho/php.tools
+[sublime-phpfmt]: https://github.com/dericofilho/sublime-phpfmt