Update src/articles/WorkflowSprints.md

src/articles/WorkflowSprints.md

@@ -100,7 +100,7 @@ I designed the methodology after witnessing many publishers making these common
  1. Investing in slow and costly ‘requirements research’
  2. Looking at the problem exclusively through a ‘technology lens’
 
-Understanding and optimis processes are lengthy research projects that interview individual team members and produce immense amounts of narrative and flow diagrams. Such outputs are seldom clarifying. On the other hand, Workflow Sprints produce crisp clarity in a process that can be counted in days, not months or years.
+Understanding and optimising workflow need not be a slow or expensive process. Too often, these processes are lengthy research projects that interview individual team members and produce immense amounts of narrative and flow diagrams. Such outputs are seldom clarifying. On the other hand, Workflow Sprints produce crisp clarity in a process that can be counted in days, not months or years.
 
 A Workflow Sprint first investigates and describes the current workflow and then produces an optimised workflow. From these outputs, your organisation will be in a good position to consider technology choices.