svn commit: r481683 - /struts/struts1/trunk/src/site/xdoc/userGuide/release-notes.xml

[pbenedict]

Author: pbenedict
Date: Sat Dec  2 17:19:33 2006
New Revision: 481683

URL: http://svn.apache.org/viewvc?view=rev&rev=481683
Log:
STR-2978: Minor corrections to the release notes

Modified:
    struts/struts1/trunk/src/site/xdoc/userGuide/release-notes.xml

Modified: struts/struts1/trunk/src/site/xdoc/userGuide/release-notes.xml
URL: 
http://svn.apache.org/viewvc/struts/struts1/trunk/src/site/xdoc/userGuide/release-notes.xml?view=diff&rev=481683&r1=481682&r2=481683
==============================================================================
--- struts/struts1/trunk/src/site/xdoc/userGuide/release-notes.xml (original)
+++ struts/struts1/trunk/src/site/xdoc/userGuide/release-notes.xml Sat Dec  2 
17:19:33 2006
@@ -98,8 +98,8 @@
                                                                <p>Just as the 
<code>TilesRequestProcessor</code> could recognize a tile definition
                                                                and resolve it 
to the intended JSP, so does Struts now have built-in
                                                                recognition for 
URIs that begin with an <code>actionId</code> and will automatically
-                                                               translate 
forwards. Both these forwards will be rewritten internally
-                                                               to forward to 
<code>/person/view.do</code> (with parameters included):
+                                                               translate 
forwards. Both these forwards below will be resolved internally
+                                                               to 
<code>/person/view.do</code> (with parameters included):
                                                                </p>
                                                                
 <pre>
@@ -112,8 +112,8 @@
                                                                
<code>actionId</code>:</p>
                                                                
 <pre>
-&lt;html:form action="savePersonAction"&gt;...&lt;html:form&gt;
-&lt;html:link action="viewPersonAction" /&gt;
+&lt;html:form action="savePersonAction"&gt;...&lt;/html:form&gt;
+&lt;html:link action="viewPersonAction"&gt;...&lt;/html:link&gt;
 </pre>
                                                                
                                                                <p>Note: It is 
good practice to name the <code>actionId</code> as <em>entityAction</em>