Reorganizing the page

What I did:
* Order the options alphabetically
* Promote each option to be a heading
* Some slight rewordings

TODO:
Get the `settings` keys out of the codeblock - maybe a bulleted list? - to allow HTML markup

Author: ThomasLandauer

docs/reference/Configuration.md

@@ -5,38 +5,80 @@ title: Configuration - Codeception - Documentation
 
 # Configuration
 
-## Global Configuration
+## Global Configuration: `codeception.yml`
 
-Configuration file `codeception.yml` is generated by `codecept bootstrap` command. It has preconfigured settings you can change.
+The global configuration file `codeception.yml` is generated by the `codecept bootstrap` command. Alphabetical list of options:
 
-Here are global options you can change inside configuration:
+### `actor_suffix`
 
-* `actor_suffix: Tester`: changes suffix for Actor classes. This defines a rule to generate new test suites. If you change `Tester` to `Ninja`, and generate new `api` test suite, you will get `ApiNinja` actor class.
-* `namespace`: set a namespace for tests. All new tests and support classes will be generated under that namespace. Allows to configure [multiple test setups for one runner](https://codeception.com/docs/08-Customization#Namespaces).
-* `include: []`: include additional Codeception configurations for [multiple applications setup](https://codeception.com/docs/08-Customization#Namespaces).
-* `paths` directories used by Codeception. Default values are:
+Sets the suffix for "Actor" classes. Default: `Tester`.  If you set it to `Ninja` and generate a new `api` test suite, you will get an `ApiNinja` actor class.
+
+### `bootstrap`
+
+Bootstrap script that will be executed before all suites. A script should be put into `tests` directory.
+
+### `coverage`
+
+[CodeCoverage](https://codeception.com/docs/11-Codecoverage#Configuration) settings.
+
+### `extends`
+
+Allows you to specify a file (relative to the `codeception.yml` file) that holds some already pre-defined values. This can be used to always use the same configuration for modules or whatever.
+
+### `extensions`
+
+Allows to enable and configure [Codeception extensions](https://codeception.com/docs/08-Customization#Extension), [Group Objects](https://codeception.com/docs/08-Customization#Group-Objects), and [Custom Commands](https://codeception.com/docs/08-Customization#Custom-Commands).
+
+### `gherkin`
+
+[Gherkin options](https://codeception.com/docs/07-BDD#Configuration).
+
+### `include`
+
+Include additional Codeception configurations for [multiple applications setup](https://codeception.com/docs/08-Customization#Namespaces).
+
+### `modules`
+
+Allows to create shared module configuration for all included suites.
 
 {% highlight yaml %}
+modules:
+    config:
+        Db:
+            dsn: ''
+            user: ''
+            password: ''
+            dump: tests/_data/dump.sql
+{% endhighlight %}
 
-paths:
-    # where the tests stored
-    tests: tests
+### `namespace`
+
+Sets the namespace under which all new tests and support classes will be generated. Allows to configure [multiple test setups for one runner](https://codeception.com/docs/08-Customization#Namespaces).
 
-    # directory for fixture data
-    data: tests/_data
+### `params`
 
-    # directory for support code
-    support: tests/_support
+Allows to pass [external parameters](https://codeception.com/docs/06-ModulesAndHelpers#Dynamic-Configuration-With-Parameters) into module configuration.
 
-    # directory for output
-    output: tests/_output
+### `paths`
 
-    # directory for environment configuration
-    envs: tests/_envs
+Directories used by Codeception. Default values:
 
+{% highlight yaml %}
+paths:
+    tests  : tests          # where the tests stored
+    data   : tests/_data    # directory for fixture data
+    support: tests/_support # directory for support code
+    output : tests/_output  # directory for output
+    envs   : tests/_envs    # directory for environment configuration
 {% endhighlight %}
 
-* `settings`: provide additional options for test runner. They may dramatically change the way Codeception is executed. For instance, take a note of `shuffle` option which allows to randomize tests execution order and `lint` option that toggles parsing a test file (using `php -l`) before loading it.
+### `reporters`
+
+Allows to [change default reporters](https://codeception.com/docs/08-Customization#Custom-Reporters) of Codeception
+
+### `settings`
+
+Provide additional options for the test runner. They may dramatically change the way Codeception is executed. For instance, take a note of `shuffle` option which allows to randomize tests execution order and `lint` option that toggles parsing a test file (using `php -l`) before loading it.
 
 {% highlight yaml %}
 
@@ -92,27 +134,6 @@ settings:
 
 {% endhighlight %}
 
-* `modules`: allows to create shared module configuration for all included suites.
-
-{% highlight yaml %}
-
-modules:
-    config:
-        Db:
-            dsn: ''
-            user: ''
-            password: ''
-            dump: tests/_data/dump.sql
-
-{% endhighlight %}
-* `extends`: allows you to specify a file (relative to the `codeception.yml` file) that holds some already pre-defined values. This can be used to always use the same configuration for modules or whatever.
-* `extensions`: allows to enable and configure [Codeception extensions](https://codeception.com/docs/08-Customization#Extension), [Group Objects](https://codeception.com/docs/08-Customization#Group-Objects), and [Custom Commands](https://codeception.com/docs/08-Customization#Custom-Commands).
-* `reporters`: allows to [change default reporters](https://codeception.com/docs/08-Customization#Custom-Reporters) of Codeception
-* `coverage`: [CodeCoverage](https://codeception.com/docs/11-Codecoverage#Configuration) settings.
-* `params`: allows to pass [external parameters](https://codeception.com/docs/06-ModulesAndHelpers#Dynamic-Configuration-With-Parameters) into module configuration.
-* `gherkin`: BDD-specific [Gherkin options](https://codeception.com/docs/07-BDD#Configuration).
-* `bootstrap`:  bootstrap script that will be executed before all suites. A script should be put into `tests` directory.
-
 ## Suite Configuration
 
 Each generated suite have its own configuration inside directory set by `paths: tests: ` configuration option in `codeception.yml`. Each suite configuration is named like `suitename.suite.yml`. It allows to enable and configure modules, and more.