style guide: adding language to avoid dogma. Closes #50

docs/best-practices/documentation-style-guide.md

@@ -200,6 +200,13 @@ identify with genders outside of a binary framework.
 
 ### Tone and vocabulary
 
+Try to avoid constructions that tell people what they *should* do when multiple
+options exists. We want to recognize and respect that there is more than one
+way to approach being a user or developer. Preferring constructions that
+suggest ways that people can do things. We would like to to avoid language that
+gets proscriptive or feels intimidating from a reader's perspective, and we
+like having a guide that can be consumed by people in different ways.
+
 **For the *User* and *Administrator* Guides only:** We try and limit the
 content to tasks that the user can perform from the front end. This means that
 we don't go into detailed steps about installation or system administration