> I think we've dropped the bit about the default interpretation of "git > checkout <something>". Maybe > > When you run `git checkout <something>`, Git tries to guess whether > `<something>` is intended to be a branch, a commit, or a set of file(s), > and then switches branches, switches commits, or restores the files. > > By default, Git interprets `<something>` as a _<tree-ish>_. > [explain what choosing a tree-ish means for the user?] > > [Your notes on disambiguation as before] Thanks, will fix. Though I don't think it's accurate that Git will treat <something> as a <tree-ish> in this context, since `git checkout <tree>` is not valid. Will find a different wording. (I get "fatal: Cannot switch branch to a non-commit")
