From b1168e4fbf7135c341f2b62fedfb0e022585d2b5 Mon Sep 17 00:00:00 2001
From: Keith Donald <kdonald@vmware.com>
Date: Tue, 8 Apr 2008 08:13:21 +0000
Subject: [PATCH] polish

---
 spring-webflow-reference/src/defining-flows.xml | 11 +++++++++--
 spring-webflow-reference/src/el.xml             |  6 +++---
 2 files changed, 12 insertions(+), 5 deletions(-)

diff --git a/spring-webflow-reference/src/defining-flows.xml b/spring-webflow-reference/src/defining-flows.xml
index b4c9e4f4..a7fb0aac 100644
--- a/spring-webflow-reference/src/defining-flows.xml
+++ b/spring-webflow-reference/src/defining-flows.xml
@@ -359,7 +359,11 @@ public interface FlowOutcome {
     &lt;end-state id="bookingCancelled" /&gt;
 		
 &lt;/flow&gt;		
-			</programlisting>		
+			</programlisting>	
+			<para>
+				The flow now accepts a <code>hotelId</code> input attribute and returns a <code>bookingId</code> output attribute
+				when a new booking is confirmed.
+			</para>	
 		</sect2>
 	</sect1>
 	<sect1 id="flow-variables">
@@ -473,7 +477,10 @@ public interface FlowOutcome {
     &lt;end-state id="bookingCancelled" /&gt;
 		
 &lt;/flow&gt;		
-			</programlisting>		
+			</programlisting>
+			<para>
+				The flow now calls a <code>createGuest</code> subflow to add a new guest to the guest list.
+			</para>				
 		</sect2>		
 	</sect1>
 </chapter>
\ No newline at end of file
diff --git a/spring-webflow-reference/src/el.xml b/spring-webflow-reference/src/el.xml
index 6ddd1240..d0d591ca 100644
--- a/spring-webflow-reference/src/el.xml
+++ b/spring-webflow-reference/src/el.xml
@@ -51,7 +51,7 @@
 			<listitem><para>Resolving constructs such as state transition criteria, subflow ids, and view names.</para></listitem>
 		</orderedlist>
 		<para>
-			Views rendered by flows often access flow data structures using EL as well.
+			Views rendered by flows typically access flow data structures using EL as well.
 		</para>
 		<sect2 id="el-types">
 			<title>Expression Types</title>
@@ -81,7 +81,7 @@
 				<para>
 					The second type of expression is a "template" expression.
 					Such expressions allow a mixing of literal text with one or more eval blocks.
-					Each evaluateable block is explictly delimited with the <code>${}</code> delimiters.
+					Each eval block is explictly delimited with the <code>${}</code> delimiters.
 					For example:
 				</para>
 				<programlisting type="xml">
@@ -89,7 +89,7 @@
 				</programlisting>
 				<para>
 					The expression above is a template expression.
-					The result of evaluation will be a string that combines the literal text <code>error-</code> with the result of evaluating <code>externalContext.locale</code>.
+					The result of evaluation will be a string that concatenates the literal text <code>error-</code> with the result of evaluating <code>externalContext.locale</code>.
 					As you can see, explicit delimiters are necessary here to demarcate eval blocks within the template.
 				</para>
 			</sect3>