Description of problem:
[root@virt-247 ~]# pcs clsuter stop --all

Usage: pcs [-f file] [-h] [commands]...
Control and configure pacemaker and corosync.

Options:
    -h, --help  Display usage and exit.
    -f file     Perform actions on file instead of active CIB.
    --debug     Print all network traffic and external commands run.
    --version   Print pcs version information.

[... more text here ...]

The help does not actually help me. Message like "Invalid command. Use --help [command] to get detailed help" would be much more useful.

In this scenario I get bunch of unexpected text, have to scroll up to see if there was any error, none found, and then look through the command again to see the typo. Having only the short message would save me time. This is especially true for very long help texts (like pcs resource help).

I know we discussed it earlier that having detailed info (more "heuristics" involved in looking into what exactly was wrong and more detailed error message) would be beneficial, but even having the shorter version as described above would be a good start and could be much easier to do.

Version-Release number of selected component (if applicable):
pcs-0.9.152-8.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. make typo in pcs commands ("pcs clufter stop" for instance ;)) 
2.
3.

Actual results:
long help text, lots of reading, no exact error message, angry admins

Expected results:
short error message, message only and not the whole help (it's getting bigger with every release), admins cursing only about their typing :)

Additional info: