(it's actually not that much!)
Please note - this remains a first draft stage document; and will forever be so. It's main goal is to give you some of the core phrases you will need to search out answers on your own! Searching around for answers to git will almost, if not actually always, lead to a solution. Comments, improvements, and especially links to more and more different types of introductory git guides (videos! interactive sites! gifs!) are welcomed.
Git in a simple view is like a really fine-tuned track-changes process. To painfully extend the word processor analogy, you know when you're trying to just move an image in a document a teensy bit, but you can't touch it without it going crazy, moving to the next page, or overlapping text, and you really wish (if you're a bit of a nerd) that you could just edit manually the setting, like an HTML/CSS stylesheet or similar? Git is like that, but for changes.
Of course, it is built for and around software development - and has a