Try this: http://www.gitguys.com/
Also, you need to remember that GIT is designed to be self contained locally and you "push" and "pull" changes to/from public repos. My biggest problem when shifting from SVN to GIT was that all your changes are made LOCALLY to your local repository and not to the common shared repository. That means your commit is only on your local system in that directory tree and no place else. Now if you want to have a shared repository and work with others, you have to carefully think about the way you want changes to get "pushed" to the public repo so others can "pull" them.
Things can get pretty complex with GIT too, where you pull from one repo, branch, do your work and commit, then push to another repo. But it's this flexibility that gives you lots of control over how your development process works and how your source configuration management solution supports that.
Personally I suggest the CLI interface to GIT for a number of reasons. First, it's portable. If GIT runs on that system, the CLI will be there. Second, it helps you to keep track of what's going on with GIT because you are forced to type in things, instead of just letting the GUI do it for you. I also have the TortoiseGit GUI installed on my windows system, but I rarely use it for anything but the most simple steps.
I suggest you start by hammering out how you want your software development process to work, then hammer out what GIT commands you need by using the above web page. Try a number of scenarios with multiple developers and make sure you know how to make GIT work in that environment.. Test it to be sure your process works, then stick to the formula you come up with.