public/git-how.md
... ...
@@ -1,6 +1,6 @@
1
-We are going to make a repo for a wiki. Along the way we are going to watch what Git is doing.
1
+## We are going to make a repo for a wiki. Along the way we are going to watch what Git is doing.
2 2
3
-### Why is Git so hard?
3
+## Why is Git so hard?
4 4
5 5
In my opinion, the reason Git is so hard is that the commands (`git add`, `git commit`, `git checkout`, etc.),
6 6
have names whose semantics seem to be mapped onto the history of a variety of versioning tools, especially Subversion. The actual git commands, however, have behaviors with very precise meanings regarding specific git entities. For instance, `git add` means: Compress the files and add them to a git-managed directory, and add references to those files to the binary "index" file. Even when the official Git docs use the language of the implementation (for instance, we are told by `git help add` that `git-add` means "Add file contents to the index") it isn't very clear what