Nice. Now that we're getting all stackoverflowy in here, it would be worth mentioning two other handy tips.
Preventing typo mistakes with bash autocomplete is even better than correcting mistakes afterwards, it also makes typing so much faster.
It works with commands AND it also works for files inside the current working directory.
Hint: start typing your command and then hit TAB, voilà!
Note: if there are more than 1 command/file option that starts with the same chars you wrote, hit TAB twice and you will have all the options displayed in front of you, it comes in handy to remember fast instead of browsing documentation.
When I was typing the '#' I was thinking 'comment', not 'root shell'; in retrospect I can see how it might have been confusing, especially when my example used 'sudo'.
I was not criticizing your use of # at all. Using # to comment is perfectly fine I guess. Now that you mentioned it, it might be a bit confusing for newbies, but don't worry I don't think anyone would try to send the command 'Crap' over a super user session, although why the hell not? haha
Preventing typo mistakes with bash autocomplete is even better than correcting mistakes afterwards, it also makes typing so much faster. It works with commands AND it also works for files inside the current working directory.
Hint: start typing your command and then hit TAB, voilà! Note: if there are more than 1 command/file option that starts with the same chars you wrote, hit TAB twice and you will have all the options displayed in front of you, it comes in handy to remember fast instead of browsing documentation.
Command example:
$ git rem[TAB] ---> $ git remote
$ git remote a[TAB] ---> $ git remote add
File example:
$ git add i[TAB] --> $ git add index.js
Multiple options example (TAB twice):
$ git r[TAB,TAB]
(will give you the options:)
rebase relink replace revert reflog remote request-pull rm release repack reset
The result is NO TYPOS! ;)
--------------------------
It would also be worth remembering the unix convention of using $ for regular user prompt and # for super user prompt.
In other words:
$ <--- if this is your prompt you're working on a regular user session.
# <--- if this is your prompt you're working on a super user session and you don't need sudo.
Again, that is just a convention, your OS/distro could be different.