From 10898eded280c3e7f072f5bd0fa881422b5b0733 Mon Sep 17 00:00:00 2001
From: Blaise Thompson <blaise@untzag.com>
Date: Thu, 10 May 2018 12:54:07 -0500
Subject: 2018-05-10 12:54

---
 software/chapter.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'software/chapter.tex')

diff --git a/software/chapter.tex b/software/chapter.tex
index 372acdf..50a9e75 100644
--- a/software/chapter.tex
+++ b/software/chapter.tex
@@ -238,7 +238,7 @@ change (feature addition, bugfix, etc).  %
 Typically version control is coupled with uploading to a remote server, for example using git with
 GitHub \cite{GitHub}, GitLab \cite{GitLab} or git.chem.wisc.edu \cite{git.chem.wisc.edu}, but
 version control need not be synonymous with uploading and distribution.  %
-Tools like git have a lot of fantastic features beyond simply saving [CITE], but those are beyond the
+Tools like git have a lot of fantastic features beyond simply saving, but those are beyond the
 scope of these ``good enough'' recommendations.  %
 Also consider defining a version for the software package as a whole.  %
 Use semantic versioning (MAJOR.MINOR.PATCH) \cite{SemanticVersioning}, unless there is a strong
-- 
cgit v1.2.3

