Merge pull request #111 from ibuildingsnl/documentation-things-i-noticed

Documentation things I noticed

README.md

@@ -33,6 +33,8 @@ If you want, you can use the `--install-dir` option for `qa-tool-setup.php` to i
 should be installed. E.g., `php qa-tools-setup.php --install-dir=/usr/local/bin`. It is recommended you
 download QA tools to either your project directory or to some location that is in your [PATH][path].
 
+A specific version can be installed by specifying the `--version` option: `php qa-tools-setup.php --version=3.0.0-alpha2`. This is useful when installing unstable versions of QA Tools.
+
 To see all the options of the installer, run `php qa-tools-setup.php --help`.
 
 Read why we release the QA Tools as a Phar [here](docs/phar.md).

docs/release-process.md

@@ -32,7 +32,7 @@ on GitHub.
  0. Click *Draft a new release*.
  0. Select the tag you just published.
  0. Use the tag as release title.
- 0. If it's an unstable version, indicated by a stability label like `#.#.#-beta`, check the pre-release checkbox. This does not have any functional consequences for the self-updating process, but functions primarily as documentation.
+ 0. If it's an unstable version, indicated by a stability label like `#.#.#-beta`, tick the pre-release checkbox. Ticking this checkbox does not have any functional consequences for the self-updating process, but functions primarily as documentation.
  0. Copy this release's documented changes (see the change log) into the
     description field.
  0. Attach the Phar and its public key to the release. You find these in the `./build/release/`  directory.