diff --git a/README.md b/README.md
index 3cac7cb..bf4ffef 100644
--- a/README.md
+++ b/README.md
@@ -67,14 +67,15 @@ statement is formulated. The problem identification generally happens via
 the issue tracker in GitHub. Once a problem statement is formulated a pull
 request for the document located in documents/wip should be issued. A second
 step is the creation of a solution proposal which may then be solicited
-to distributions for discussion. Once consensus is reached the solution is
+to distributions, developers, customers and other interested parties
+for discussion. Once consensus is reached the solution is
 committed to documents/specifications without additional changes. Changes
 to accepted solutions should only consist of trivial fixes for spelling and
 grammar as well as additions of new distributions pledging to support
 a given specification.
 
 The solicitation of a Problem Statement or a Solution Proposal should
-occur on a distribution public mailing list and a link to the thread
+occur on distribution or other public mailing lists and link to the threads
 should be included in the document.
 
 Unless specifically stated no document should become an accepted
diff --git a/WorkFlow2.odp b/WorkFlow2.odp
new file mode 100644
index 0000000..73e0296
Binary files /dev/null and b/WorkFlow2.odp differ
diff --git a/WorkFlow2.pdf b/WorkFlow2.pdf
new file mode 100644
index 0000000..f3e0c63
Binary files /dev/null and b/WorkFlow2.pdf differ