file versions are not saved; changes to files are tracked/recorded

[maneesha]

How could the content be improved?

In the Summary and setup section, we say the following (emphasis mine):

Nothing that is committed to version control is ever lost, unless you work really, really hard at it. Since all old versions of files are saved, it’s always possible to go back in time to see exactly who wrote what on a particular day, or what version of a program was used to generate a particular set of results.

Git does not actually save entire versions of files. Instead it tracks and records the changes that were made to each file. When I was first learning Git, this was an important shift I had to make in my mental model of how my work was being saved. Consider changing the text here to reflect what Git is actually doing. That distinction would have helped me greatly when I was first learning Git.

Which part of the content does your suggestion apply to?

https://swcarpentry.github.io/git-novice/

[jas58]

@maneesha May I ask the words you are suggesting instead?
Would it be:
Since all changes made within a file are tracked and recorded after comit/push(I'm always confused by the verbs), it is possible to return to a particular day and read the prior versions.

Or something else?