Counterpoint: if you are giving a user instructions (how tos, support interactions etc) then having the buttons, and concepts clearly marked out is really helpf

Counterpoint: if you are giving a user instructions (how tos, support interactions etc) then having the buttons, and concepts clearly marked out is really helpful. E.g. if support tells a customer "click on your account" - then what does that mean? account is a generic abstract thing, how does one click on that? The customer must deduce that support is referring to one particular button on one particular place. Or support must say "the button labeled 'account' on the top right hand corner of the screen". If there is a unique name, then saying "click on 'Your Account"' is simpler. It's even more critical when support needs to explain something abstract to a customer. Like, imagine explaining the difference between the temporary and EBS storage of a EC2 instance without any of the capitalized feature names.