hooke/history.tex: Replace 'churn' with 'turnover'

Less jargon-y.  Thanks Mom!

diff --git a/src/hooke/history.tex b/src/hooke/history.tex
index 9ad040d109de375bd51293ef7eac0571d84283b8..468b5f1f5019af272c72671a8de277825c16812b 100644 (file)
--- a/src/hooke/history.tex
+++ b/src/hooke/history.tex
@@ -6,15 +6,16 @@ University of Bologna.  It was actively developed until the paper came
 out, after which development became more sporadic.  This was partly
 because \Hooke\ worked well enough for the original authors and partly
 because some of the developers had graduated and moved on to other
-fields\footnote{Developer churn may seem like a good reason to avoid
-  open source software.  Why use something when its developers may not
-  stay around to support it?  This argument may make sense if you're
-  comparing open source and commercial packages, but it makes less
-  sense if you're comparing existing open source packages to
-  hypothetical in-house software.  Why \emph{not} use something, if
-  it's free and already exists?  Figuring out someone else's software
-  is often much more efficient than writing your own tool from
-  scratch.}.
+fields\footnote{
+  Developer turnover may seem like a good reason to avoid open source
+  software.  Why use something when its developers may not stay around
+  to support it?  This argument may make sense if you're comparing
+  open source and commercial packages, but it makes less sense if
+  you're comparing existing open source packages to hypothetical
+  in-house software.  Why \emph{not} use something, if it's free and
+  already exists?  Figuring out someone else's software is often much
+  more efficient than writing your own tool from scratch.
+}.
 
 Before discovering \Hooke in 2010, I had been using a series of fairly
 site-specific scripts to post-process my unfolding data.  Excited by