deletions | additions       diff --git a/box-3-what-not-to-version-control.tex b/box-3-what-not-to-version-control.tex  index 693ea06..4070c05 100644  --- a/box-3-what-not-to-version-control.tex  +++ b/box-3-what-not-to-version-control.tex 
...
\subsection{Box 3: What \textit{not} to version control}  You \textit{can} version control any file that you put in a git Git  repository, whether it is text-based, an image, or giant data files. However, just because you \textit{can} version control something, does not mean you \textit{should}. Git works great best  for plain text based documents such as your scripts or your manuscript if written in latex LaTeX  or markdown. Markdown.  This is because for text files, git Git  saves the entire file only the first time you commit it and then saves just your changes with each commit. This takes up very little space and git Git  has the capabilities capability  to compare between versionsbuilt in  (using \verb|git diff|). You can commit a non-text file, but a full copy of the file will be saved with each commit. Over time, you may find the size of your repository growing very quickly. A good rule of thumb is to version control anything text based: your scripts or manuscripts if they are written in plain text. Things \textit{not} to version control are large data files that never change, binary files (including Word and Excel documents), and the output of your code.