From 119c2cdbce808fd8ac3e6bf47fe78a14295811c7 Mon Sep 17 00:00:00 2001
From: Adam Hyde <adam@coko.foundation>
Date: Sat, 15 Oct 2022 08:41:54 +0000
Subject: [PATCH] Update WorkflowSprints.md

---
 src/articles/WorkflowSprints.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/articles/WorkflowSprints.md b/src/articles/WorkflowSprints.md
index 4e82080..c598ec8 100644
--- a/src/articles/WorkflowSprints.md
+++ b/src/articles/WorkflowSprints.md
@@ -14,7 +14,7 @@ I am in the business of building publishing technology. However, I actually beli
 
 To get to good technology, it is very important to start the process by not thinking about technology at all. If you frame your thinking through the lens of technology, you will more than likely end up with an expensive failure. What we are really interested in are good workflows and, later, designing technology to encapsulate and enable good workflow.
 
-![Coko Website](/images/uploads/wfs1.jpg)
+![Coko Website](/images/uploads/wfs1a.jpg)
 
 To help us understand this problem we need to define workflow as it means many different things to different people - by workflow, I mean the complete set and order of actions an organization (usually a publisher) undertakes to prepare an object (book, journal article, preprint review, question set etc) for publishing or sharing. 
 
-- 
GitLab