Updated README

Author: JoshyPHP

README.md

@@ -5,31 +5,41 @@
 
 ### Installation
 
-You can download the [latest release as a PHAR](https://github.com/s9e/RegexpBuilderCommand/releases/latest/download/build-regexp.phar), or install the command as a [Composer](https://getcomposer.org/download/) dependency:
+There are two ways to use this command. You can download the [latest release as a PHAR](https://github.com/s9e/RegexpBuilderCommand/releases/latest/download/build-regexp.phar):
+```
+$ wget -q https://github.com/s9e/RegexpBuilderCommand/releases/latest/download/build-regexp.phar
+$ chmod +x build-regexp.phar
+$ ./build-regexp.phar --version
+build-regexp 0.4.3
+```
 
-```bash
-composer require s9e/regexp-builder-command
+Or you can install the command as a [Composer](https://getcomposer.org/download/) dependency:
+
+```
+$ composer -q require s9e/regexp-builder-command
+$ vendor/bin/build-regexp --version
+build-regexp 0.4.3
 ```
 
 
 ### Usage
 
 Strings can be specified either directly in the command invocation or via an input file. The following shell example shows how to pass them in the command invocation as a space-separated list:
 ```
-$ ./vendor/bin/build-regexp foo bar baz
+$ ./build-regexp.phar foo bar baz
 (?:ba[rz]|foo)
 ```
 
 In the following example, we create a file with each value on its own line, then we pass the name of the file via the `infile` option:
 ```
 $ echo -e "one\ntwo\nthree" > strings.txt
-$ ./vendor/bin/build-regexp --infile strings.txt
+$ ./build-regexp.phar --infile strings.txt
 (?:one|t(?:hree|wo))
 ```
 
 By default, the result is output in the terminal directly. Alternatively, it can be saved to a file specified via the `outfile` option. In the following example, we save the result to a `out.txt` file before checking its content:
 ```
-$ ./vendor/bin/build-regexp --outfile out.txt foo bar baz
+$ ./build-regexp.phar --outfile out.txt foo bar baz
 $ cat out.txt
 (?:ba[rz]|foo)
 ```
@@ -46,16 +56,16 @@ Several presets are available to generate regexps for different engines. They de
 
 The following examples show the results of a few different presets with the Unicode characters U+1F601 and U+1F602 as input.
 ```
-$ ./vendor/bin/build-regexp --preset pcre "😁" "😂"
+$ ./build-regexp.phar --preset pcre "😁" "😂"
 \xF0\x9F\x98[\x81\x82]
 
-$ ./vendor/bin/build-regexp --preset javascript "😁" "😂"
+$ ./build-regexp.phar --preset javascript "😁" "😂"
 \uD83D[\uDE01\uDE02]
 
-$ ./vendor/bin/build-regexp --preset pcre --flags u "😁" "😂"
+$ ./build-regexp.phar --preset pcre --flags u "😁" "😂"
 [\x{1F601}\x{1F602}]
 
-$ ./vendor/bin/build-regexp --preset javascript --flags u "😁" "😂"
+$ ./build-regexp.phar --preset javascript --flags u "😁" "😂"
 [\u{1F601}\u{1F602}]
 ```