. d better coaching docs

Co-Authored-By: 4dsherwood <4dsherwood@users.noreply.github.com>
Co-Authored-By: Trillium Smith <trillium@trilliumsmith.com>
Co-Authored-By: Llewellyn Falco <llewellyn.falco@gmail.com>
Co-Authored-By: reyr-dev <236299828+reyr-dev@users.noreply.github.com>
Co-Authored-By: Susan Fung <38925660+susanfung@users.noreply.github.com>

Author: 6 people

internal_documentation/Responsibilities of a coach.md

@@ -2,6 +2,14 @@
 
 *Work in questions, not commands.*
 
+## Reward good behavior
+
+If you see good behavior, acknowledge it. This reinforces the behavior.
+These are small things. 
+Don't break flow.
+Close to the moments.
+Lot's of tiny tiny mentions over large things at the end.
+
 ## Flow
 
 Keep the group moving forward:
@@ -14,3 +22,15 @@ Keep the group moving forward:
 ## Cohesion
 
 Keep the group together:
+
+## Questions vs Commands
+When you are introducing or re-enforcing process, commands are good.
+When you are getting the group in sync, questions are good.
+
+### Examples of Commands
+- *"<Typer>, please summerize"* at end of rotation, and they aren't moving on, or if skip it.
+- *"No thinking at the keyboard"* when the typer is doing too much.
+- *"Rotate"* when the timer went off but people didn't.
+
+### Examples of Questions
+- *"Would you like to use your turn for questions"* - When someone is fearful of speaking