I'm glad that you pointed this out.
This is one of the reasons why you'll see a lot of commands being shared when offering advice or additional information for troubleshooting. Looks can get outdated or change frequently, and lengthy tutorials are tedious to follow. The command line also gives the assurance that you've done exactly what was asked, and didn't skip any steps. And, on top of that, in the event of any errors you can report back the output exactly instead of describing what you saw.
For reference, take a look at this little tutorial I wrote. The Issue #1 section is rather long and filled with boring text, and screenshots. At the end of that section, I left a couple of commands that will do the same thing.
Again, this is all a matter of preference. The command line is a tool like any other, effective at some tasks and not so much at others. One of the major downsides is that is not intuitive, you have to at least have some idea of what you want to do in order to search for the correct commands. In contrast, a graphical interface might allow you to explore its options visually, but it often needs more steps to complete and is harder to automate.