It took me a few hours to learn enough in git to replicate my experience in svn; sure, it takes longer than that to learn some of the other features, but the only time that is actually lost is the time spent relearning what one already knows.
(I'm not being flippant -- I hear this from people all the time, and it really makes no sense to me. If you're just going to set up a single central repository, why wouldn't you use the proven, capable tool for that workflow? Git is rather poorly documented, and works with only a tiny fraction of the professional tools that support SVN.)
My point is that the only time you lose is the time you spend relearning what you can already do with SVN: all time spent learning new things isn't lost time at all.
When it comes to documentation, not only is the reference manual excellent in the usual way of Unix reference manuals, but I also know of six tutorial Git books, several of which are free online: the Git User's Manual, the Git Community Book, Git Magic, Pragmatic Version Control Using Git, Pro Git, and Git Internals.
As I said in another comment (now deleted), I'm using Subversion on a project for the first time in years, and I constantly find myself wishing the project was using Git.