The Bash man page does not contain a complete description of Bash, only a brief summary. "man <builtin>" provides a generic builtins page usually, since the builtins can vary between shells so one man page can't cover all of the different shell behaviors. However, bash has a "help" command which will give you the bash-specific description of a given builtin.
Other than that, I usually find the HTML Bash documentation easier to read and navigate than the info, so I just use that instead.
And yes, the sudoers man page is pure evil.
Second to that is the 'example' where every single option possible is given, while at the same time not having a typical usage example. When there's 50 potential flags with arguments, I lose track of how to structure the command - it's somewhere in all those square brackets... somewhere...
Those who would give up essential liberty to purchase a little temporary safety deserve neither liberty nor safety. Benjamin Franklin, Historical Review of Pennsylvania, 1759
Trading long term independence for temporary efficiency never looked so good!
I've been thinking about this myself. I think there's good reason: Google (or a bunch of experts on hand) will often provide a better, more concise answer to your specific question than having to search and grok the manpages.
As extreme examples, I regularly ragequit the Bash manpage after trying to find the meaning of some keywords, and the Sudoers manpage is notorious with presenting the syntax as EBNF without examples!
(a pity GNU Info never fixed their interface, the idea's good)