1) Add more commas to the documentation - Bug request filed.
2) Move 1.3 and 1.4 to an appendix. What do they have to do with my application? May be nice to know someday but only makes the introduction more complicated at the start and does not really add to the initial experience or understanding of how to design a Webflow application.
3) In place of 1.3 and 1.4, put in an architectural overview of "my test application". Start with a description of a simple sample. It could be any one of the existing samples but simplify it to just show a simple set of transitions rather than the more advanced or application specific stuff in the existing samples.
Keep the discussion at th introductory level with forward references to where the particular concept will be discussed in detail.
4) You might want to consider using some of the graphs from the SpringEclipse plug-in. They are fairly attractive.
5) More commentary in the sample applications is always helpful.
6) Additional samples always appreciated.
The documentation is a much bigger problem in getting Spring and Spring WebFlow accepted than any deficiency in the functionality.
From my limited experience and the discussion of the enhancements requested, very few of them are show stoppers that are preventing people from getting their applications working. The documentation is.