My issue with this style of verification is more that it normalises running commands right in the terminal. Commands that come from place you kind of trust. And poof at some point it will contain some nefarious code. Instead of using a package manager (the curl to bash variant) or running these commands in a container/vm.
I understand what you’re saying but in this case notice they don’t even mention terminal or command lines. You have to already understand enough context to know what they mean and at that point you should be able to interpret the command itself.
Then write and highlight exactly that! ( e.g. "Never copy or execute code you do not understand! This is only for people who already know what will happen! Confirm:")
Forget about teaching people bad patterns. It's annoying when others assume everyone experiencing something under the same context and considers the same things as them.
To be fair, just because you understand the code you see doesn't mean its safe to copy-paste. Many of these compromised sites will show something that appears to be a benign command but will be something entirely different when you copy them.
Not good to get people into the habit of copying and running code in their terminal.