summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOwen Jacobson <owen.jacobson@grimoire.ca>2014-10-14 16:06:46 -0400
committerOwen Jacobson <owen.jacobson@grimoire.ca>2014-10-14 16:06:46 -0400
commitdbf6d2be65b12418cbf8ac4e37fc191743e8813b (patch)
tree43a82d616c5f1ca0eb082b0ea57d4497b004ecc7
parentfde1dac375709c5cf495eced566faa44074b385e (diff)
The usual quote-mark fixing.
-rw-r--r--wiki/dev/whats-wrong-with-jenkins.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/wiki/dev/whats-wrong-with-jenkins.md b/wiki/dev/whats-wrong-with-jenkins.md
index 44121ff..4224eb7 100644
--- a/wiki/dev/whats-wrong-with-jenkins.md
+++ b/wiki/dev/whats-wrong-with-jenkins.md
@@ -5,7 +5,7 @@ mature software development. Jenkins (and its predecessor, Hudson) has the
unique privilege of being both an early player in the niche and
free-as-in-beer. The blog space is littered with interesting articles about
continuous builds, automated testing, and continuous deployment, all of which
-conclude on "how do we make Jenkins do it?"
+conclude on “how do we make Jenkins do it?”
This is unfortunate, because Jenkins has some serious problems, and I want it
to stop informing the discussion.