deletions | additions       diff --git a/Version your code.tex b/Version your code.tex  index a4508a9..e94f8f2 100644  --- a/Version your code.tex  +++ b/Version your code.tex 
...
\end{lstlisting}  Now you're ready to start tracking your code.  This requires a basic understanding of how Git interprets tracks  your files and the edits you make to them (Figure 1). Unsaved files and/or  edits are in the working directory. When you save your edits, they are "committed" This is similar  to the Git repository.  You'll need how you have worked before, i.e. edits  to understand files in  the terminology used by working directory are not saved (unless you explicitly direct  Git to understand  In do so).  To follow what  Git terminology, repository refers to all is doing as we save  the files being tracked by Git and all initial version of our files, we'll use  the previous edits made to them. informative command \verb|git status|.  \begin{lstlisting}  $ git status 
...
process.sh  nothing added to commit but untracked files present (use "git add" to track)  \end{lstlisting} There are a few key things to notice from this output.  First, notice that the three scripts are recognized as untracked files because we have not saved anything yet.  Second, notice the use of the word "commit", which is an essential Git term.  When used as a verb, it means "to save", e.g. "to commit a change."  When used as a noun, it means "a version of the code", e.g. "the figure was generated using the commit from yesterday."