Further update docs and README

Author: robertrossmann

README.md

@@ -29,6 +29,13 @@ This package can be installed via npm:
 
 Once the ruleset is installed, you must create your own *.eslintrc.{js,json,yml}* configuration file in your project's root and include those rulesets that you want to use. See the [examples](examples) directory for, well... examples.
 
+> **WARNING:** The order in which various configuration files are loaded **DOES MATTER**. The recommended load order is the following:
+>
+> - One of the versioned configurations for the chosen environment, ie. *environments/nodejs/v6*
+> - The best practices configuration file (if it exists), ie. *environments/nodejs/best-practices*
+> - The optional configuration file (if it exists), ie. *environments/nodejs/optional*
+> - Coding style ruleset, ie. *coding-styles/base*
+
 ## Structure
 
 The ESLint rules are semantically grouped into various categories for easy composition.

examples/README.md

@@ -1,10 +1,10 @@
 # Project configuration examples
 
-To use these rulesets, you must have an *.eslintrc* configuration file present in your project root. In this file, you then include those rulesets which you would like to use in your project.
+To use these rulesets, you must have an *.eslintrc.{js,json,yml}* configuration file present in your project root. In this file, you then include those rulesets which you would like to use in your project.
 
-The path to the ruleset must start with `eslint-config-javascript` (this ruleset's package name). Optionally, ESLint allows to drop the `eslint-config` to keep it short. The rest of the path is an actual folder/file in this repository. Extensions can be omitted. For detailed explanation, see ESLint's [shareable configs][shareable-configs].
+Your `extends` entry must always start with `@strv/javascript`. The rest of the path is an actual folder/file in this repository. Extensions **should** be omitted. For detailed explanation, see ESLint's [shareable configs][shareable-configs].
 
-Your configuration file can either be json, classic Node.js module, or YAML file.
+Your configuration file can either be json, classic Node.js module, or YAML file. It is recommended **not** to use json, because sometimes you might want to include some comment as to why you are doing this or that, which is not possible with json.
 
 ```js
 // .eslintrc.js