I think that sentence doesn't intend to imply such a guarantee, but instead indicates ideal up to date state of the repo.

In fact that description is even more wrong since every RCS has a copy of the checked out tree -- that's the whole point of an RCS!

With git (why does that article insist on spelling it "Git"?) you have a copy of the whole tree, so every clone can also be a an upstream tree for somebody else if desired.

AFAICT, Git documentation capitalizes the first letter:

> The advantages of Git compared to other source control systems. [0]

> You can learn more about individual Git commands with "git help command". [1]

[0] https://git-scm.com [1] http://man7.org/linux/man-pages/man1/git.1.html

Interesting, old programs like 'rm' only use lower case but new programs like bash and git (or should I say "Bash" and "Git") capitalize the program name sometimes.

Given that Unix (not "unix") inherited case sensitivity from Multics I would expect more consistency in the spelling.

(Clearly I'm focusing on the most important topics in computing!)

You are /technically/ correct... the best kind of correct. A more accurate version of that sentence would be, "With distributed VCS, a copy of the entire code base, including the history of changes, resides on each developer's device"

That’s not correct either. The more accurate version (which is also still wrong) would be: “with distributed VCS, a subset of the entire code base, including history about a subset of changes might reside on a subset of the developers devices and other storage locations” (With a reminder that any set is a subset of itself)