Fix docs after rename of the executable files in bin/.

FAQ.md

@@ -37,8 +37,8 @@ Before v0.7, Predis used the one-big-file approach to distribute the library. As
 just one file for everything, this kind of solution is actually not that good. Predis now complies with the
 [PSR-0](http://groups.google.com/group/php-standards/web/psr-0-final-proposal) standard to play nice with
 the major recent frameworks and libraries, so it needs an autoloader function to be defined. If you still
-want to have just one file grouping all the classes for whatever reason, then the __bin/createSingleFile.php__
-script in the repository can generate it for you. There is also the __bin/createPhar.php__ script that
+want to have just one file grouping all the classes for whatever reason, then the __bin/create-single-file.php__
+script in the repository can generate it for you. There is also the __bin/create-phar.php__ script that
 generates a single [Phar archive](http://www.php.net/manual/en/intro.phar.php) of the whole library.
 
 

README.md

@@ -40,12 +40,12 @@ Predis\Autoloader::register();
 ```
 
 You can also create a single [Phar](http://www.php.net/manual/en/intro.phar.php) archive from the repository
-just by launching the `createPhar.php` script located in the `bin` directory. The generated Phar ships with
+just by launching the `create-phar.php` script located in the `bin` directory. The generated Phar ships with
 a stub that defines an autoloader function for Predis, so you just need to require the Phar archive in order
 to be able to use the library.
 
 Alternatively you can generate a single PHP file that holds every class, just like older versions of Predis,
-using the `createSingleFile.php` script located in the `bin` directory. In this way you can load Predis in
+using the `create-single-file.php` script located in the `bin` directory. In this way you can load Predis in
 your scripts simply by using functions such as `require` and `include`, but this practice is not encouraged.