Update typist.md

Author: simonharrer

typist.md

@@ -1,11 +1,11 @@
-## How to be a Great Typist / Driver
+## How to act as a typist
 
 ### Be reactive.
 If you don't get any commands, do nothing - just listen. 
 Move your hands away from mouse and keyboard. 
 Meditate to the blinking of your cursor. 
 Cherish this moment. 
-Fight the urge to "help" them by joining in the discussion, or even worse, doing stuff proactively.
+Fight the urge to "help" the *rest of the team* by joining in the discussion, or even worse, doing stuff proactively.
 If you really want to join the discussion, trigger a handover to the next typist.
 
 ### Be patient.
@@ -14,21 +14,26 @@ You can ask "what should I do next?" in those cases, but it's probably better to
 You will get commands at some point afterall.
 
 ### Be slow.
-Slow down, so everybody in the rest of the team can follow what you are doing. 
+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.
 
 ### Be calm.
-Resist pressure from the rest of your team.
+Resist pressure from the *rest of your team*.
 Stay calm even in then.
 Tell them to slow down with their commands.
 Tell them to give you space and freedom to act and breath.
 
 ### Be private.
 Disable any notifications.
-The rest of the team doesn't want to get a sneak preview of your instant messages or emails.
+The *rest of the team* doesn't want to get a sneak preview of your instant messages or emails.
 
-## How to be a Great Person in the Rest of the Team / Navigator
+## How to act in the rest of the team
+
+### Be intentional.
+Communicate the intent.
+Be clear about the why to the typist.
+A smart typist with system knowledge might already start implementing just with the why.
 
 ### Be concise of location.
 Communicate location using absolutes like file names, class names, or line numbers.
@@ -38,7 +43,4 @@ Avoid relative location like "move a little bit more up; no, that was too far, g
 It's not what you say, but how you say it.
 So say "Can you go to line 45, please?".
 
-### Be intentional.
-Communicate the intent.
-Be clear about the why to the typist.
-A smart typist with system knowledge might already start implementing just with the why.
+