uncapitlaize

This commit is contained in:
Keith Donald
2008-04-10 05:15:24 +00:00
parent a406d638c6
commit 5fb1dafac0
2 changed files with 7 additions and 7 deletions

View File

@@ -32,7 +32,7 @@
</sect2> </sect2>
</sect1> </sect1>
<sect1 id="el-portability"> <sect1 id="el-portability">
<title>EL Portability</title> <title>EL portability</title>
<para> <para>
In general, you will find the Unified EL and OGNL have a very similar syntax. In general, you will find the Unified EL and OGNL have a very similar syntax.
For basic variable resolution, property access, and method invocation the syntax is identical. For basic variable resolution, property access, and method invocation the syntax is identical.
@@ -40,7 +40,7 @@
</para> </para>
</sect1> </sect1>
<sect1 id="el-usage"> <sect1 id="el-usage">
<title>EL Usage</title> <title>EL usage</title>
<para> <para>
EL is used for many things within a flow, including: EL is used for many things within a flow, including:
</para> </para>
@@ -54,7 +54,7 @@
Views rendered by flows typically access flow data structures using EL as well. Views rendered by flows typically access flow data structures using EL as well.
</para> </para>
<sect2 id="el-types"> <sect2 id="el-types">
<title>Expression Types</title> <title>Expression types</title>
<para> <para>
There are basically two types of expressions in Web Flow. There are basically two types of expressions in Web Flow.
</para> </para>
@@ -227,7 +227,7 @@
</sect2> </sect2>
</sect1> </sect1>
<sect1 id="el-scope-searching"> <sect1 id="el-scope-searching">
<title>Scope Searching Algorithm</title> <title>Scope searching algorithm</title>
<para> <para>
When assigning a variable in one of the flow scopes, referencing that scope is required. When assigning a variable in one of the flow scopes, referencing that scope is required.
For example: For example:

View File

@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<chapter id="views"> <chapter id="views">
<title>Rendering Views</title> <title>Rendering views</title>
<sect1 id="views-introduction"> <sect1 id="views-introduction">
<title>Introduction</title> <title>Introduction</title>
<para> <para>
@@ -337,7 +337,7 @@ reservationConfirmation=We have processed your reservation - thank you and enjoy
These view state history policies are configurable on a per view-state basis by using the <code>history</code> attribute. These view state history policies are configurable on a per view-state basis by using the <code>history</code> attribute.
</para> </para>
<sect2 id="history-discard"> <sect2 id="history-discard">
<title>Discarding History</title> <title>Discarding history</title>
<para> <para>
Set the history attribute to <code>discard</code> to prevent backtracking to a view: Set the history attribute to <code>discard</code> to prevent backtracking to a view:
</para> </para>
@@ -346,7 +346,7 @@ reservationConfirmation=We have processed your reservation - thank you and enjoy
</programlisting> </programlisting>
</sect2> </sect2>
<sect2 id="history-invalidate"> <sect2 id="history-invalidate">
<title>Invalidating History</title> <title>Invalidating history</title>
<para> <para>
Set the history attribute to <code>invalidate</code> to prevent backtracking to a view as well all previously displayed views: Set the history attribute to <code>invalidate</code> to prevent backtracking to a view as well all previously displayed views:
</para> </para>