Added information about input normalization to the best practices doc (#220)

Author: MarcoMeter

docs/best-practices.md

@@ -15,9 +15,11 @@ complexity over time. This can either be done manually, or via Curriculum Learni
 ## States
 * States should include all variables relevant to allowing the agent to take the optimally informed decision.
 * Categorical state variables such as type of object (Sword, Shield, Bow) should be encoded in one-hot fashion (ie `3` -> `0, 0, 1`).
-* Rotation information on GameObjects should be recorded as `state.Add(transform.rotation.eulerAngles.y/180.0f-1.0f);` rather than `state.Add(transform.rotation.y);`. 
+* Besides encoding non-numeric values, all inputs should be normalized to be in the range 0 to +1 (or -1 to 1). For example rotation information on GameObjects should be recorded as `state.Add(transform.rotation.eulerAngles.y/180.0f-1.0f);` rather than `state.Add(transform.rotation.y);`. See the equation below for one approach of normaliztaion. 
 * Positional information of relevant GameObjects should be encoded in relative coordinates wherever possible. This is often relative to the agent position.
 
+![normalization](../images/normalization.png)
+
 ## Actions
 * When using continuous control, action values should be clipped to an appropriate range.
 * Be sure to set the action-space-size to the number of used actions, and not greater, as doing the latter can interfere with the efficency of the training process.