diff --git a/UseCases/WorkFlow.mdwn b/UseCases/WorkFlow.mdwn
index 283ad4d3fddaabb18faaf0fea58ebe1ffda04c3a..d20b5680d09a92fe52b54167723c59d9ed635a5f 100644
--- a/UseCases/WorkFlow.mdwn
+++ b/UseCases/WorkFlow.mdwn
@@ -1,12 +1,17 @@
# Non-Profit Workflow
+
+
Many accounting systems seem to assume that the workflow fits a certain type
of uses. While the ability to impose a specific workflow (e.g., for a
bookkeeper who might make an error easily if the system doesn't require a
-workflow), the workflow should not be dictated.
+workflow), the workflow should not be dictated.
-## The "Unaccrued Invoice" Example
+ Ideally, in fact workflows should be
+configurable in some way. Many systems try to do this and are a bit
+constraining on it.
+## The "Unaccrued Invoice" Example
The easiest example I have of this relates to accruing income upon invoice
generation. Non-profits very typically generate invoices as part of a