Not sure these annoy any one but me, but I thought I'd throw them out there for @peternlewis to consider.
2 issues in the video:
First I drag a For Each action to a macro. When I do this the search bar in the action selector becomes selected (labeled 1 in the video) instead of the (labeled 2) text field in the For Each. So I begin typing a variable name and it goes into the search field. I do this A LOT.
Even if the text field in the For Each can't become the selected entry for text, can the search bar not be selected for text and nothing happen when I start typing? Much more annoying to have to delete or click the x after messing that up.
After adding my variable name for the loop iterator, I change the For Each to work on a lines collection and set it to use the lines in a variable (labeled 3). It guesses the variable name as the loop iterator variable, but this is never what I want to do. A better (but not 100%) guess is to use the last variable action before the loop was created.
This doesn't bug me nearly as much as the first one. Typing over with the correct variable isn't a big deal. But since I was doing the video for the first I figured I'd tag this one in as well.