Man pages are the UNIX traditional way of distributing documentation about programs. The term "man page" itself is short for "manual page", as they correspond to the pages of the printed manual; the man pages "sections" (1 for commands, 2 for system calls, etc.) correspond to sections in the full UNIX manual. Support is still there if you want to print a man page to paper, although this is rarely done these days, and the sheer number of man pages make it just impossible to bind them all into a single book.
In the early '90s, the GNU project decided that "man" documentation system was outdated, and wrote the info command to replace it: info has basic hyperlinking features and a simpler markup language to use (compared to the "troff" system used for man pages). In addition, GNU advocates against the use of man pages at all and contends that complex software systems should have complete and comprehensive documentation rather than just a set of short man pages.
There are actually other documentation systems in use, besides man and info: GNOME and KDE have their own, HTML-based system, etc.
In the end, the form in which you get documentation depends on the internal policies of the project that provided the software in the first place -- there is no globally accepted standard.
Flat is better than nested.
info info
andman info
.man info
shows colorful examples. I am more visual person, using the same color across makes me sleepy. The man syntax with a little color makes it understandable quickly.info xyz
orinfo info
. Any thing to tweak