Update

Author: simonharrer

typist.md

@@ -1,6 +1,6 @@
 ## How to act as a typist
 
-The rest of the team develop software, using the typist as a smart voice-controlled input device.
+The rest of the team develop software, using the typist (a.k.a. the driver) as a smart voice-controlled input device.
 The typist shares the screen everybody is looking at.
 This means the typist has power. 
 [But with great power comes great responsibility.](https://en.wikipedia.org/wiki/With_great_power_comes_great_responsibility)
@@ -13,22 +13,22 @@ Meditate to the blinking of your cursor.
 Cherish this moment. 
 Fight the urge to join the discussion of the *rest of the team*.
 If it helps, just mute yourself.
-You know it will we over in a few minutes.
-But if you loose that fight, trigger a handover to the next typist.
+You know it will be over in a few minutes.
+But if you lose that fight, trigger a handover to the next typist.
 
 ### Be patient.
 You might become impatient when there are no commands.
-You can ask "what should I do next?" in those cases, but it's probably better to simply wait doing nothing instead.
-You will get commands at some point afterall.
+You can ask "what should I do next?" in those cases, but it's better to wait, doing nothing instead.
+You will get fresh commands at some point afterall.
 
-### Be slow.
-Slow down, so everybody in the *rest of the team* can follow what you are doing. 
-This includes moving your mouse cursor, changing windows, switching tabs, or pressing keyboard shortcuts.
-Make it easy to follow what and how you are doing things.
-So with you going slowly, the whole team can go fast.
+### Be deliberate.
+Make sure everybody in the *rest of the team* can follow what you are doing.
+Pause at appropriate moments.
+It's like stopping between sentences, or after commas, to ensure people catch up with the thoughts.
+It might feel like slowing down, but with that, the whole team can speed up.
 
 ### Be calm.
-Although the *rest of your team* should be patient with you, it sometimes happens that you might feel pressured from the *rest of your team* for following their commands too slow.
+Although the *rest of your team* should be patient with you, it sometimes happens that you might feel pressured from the *rest of your team* for following their commands too slowly.
 Just stay calm and tell them to slow down with their commands.
 Tell them to give you space and freedom to act and breath.
 It's okay to stand your ground, even necessary.
@@ -46,17 +46,19 @@ Just ask the *rest of the team* what you should do.
 ### Be transparent.
 Be transparent of what you know so the *rest of the team* can guide you on your level of domain, technical, and system knowledge.
 If you get a command you don't understand, make this immediately clear to the *rest of the team* so they can readjust their commands.
-This is important for if you're new to the craft or the team.
+This is important if you're new to the craft or the team.
 
 ### Be attentive.
 Listen closely what the *rest of the team* discuss.
 Be ready to support them anytime.
 Don't distract yourself with email, Twitter or Slack.
 
-### Be disciplined.
+### Be giving.
 Rotation is key to the success of working together.
 Make sure to hand over to the next typist on time.
 Don't go for the famous last words of "let me finish this real quick".
+Don't hog.
+Just let it go.
 
 ### Be prepared.
 Try to be prepared so when your time as a typist comes, you can immediately implement the commands from the *rest of the team*.