struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jmitch...@apache.org
Subject svn commit: r389667 - /struts/sandbox/trunk/action2/PRACTICES.txt
Date Wed, 29 Mar 2006 04:11:45 GMT
Author: jmitchell
Date: Tue Mar 28 20:11:43 2006
New Revision: 389667

URL: http://svn.apache.org/viewcvs?rev=389667&view=rev
Log:
Fix a few typos

Modified:
    struts/sandbox/trunk/action2/PRACTICES.txt

Modified: struts/sandbox/trunk/action2/PRACTICES.txt
URL: http://svn.apache.org/viewcvs/struts/sandbox/trunk/action2/PRACTICES.txt?rev=389667&r1=389666&r2=389667&view=diff
==============================================================================
--- struts/sandbox/trunk/action2/PRACTICES.txt (original)
+++ struts/sandbox/trunk/action2/PRACTICES.txt Tue Mar 28 20:11:43 2006
@@ -13,7 +13,7 @@
  ** If you using templates, bundle the templates with the Actions.
  ** Remember, if the namespace needs to change, you do not need to change packages or JSP
folders, if you don't want to.
 
-* Within a namespace, resuse names for common concepts. If each namespace has an entry page,
use the same action name in each namespace. For example, each namespace in the Cookbook has
an "Open" action.
+* Within a namespace, reuse names for common concepts. If each namespace has an entry page,
use the same action name in each namespace. For example, each namespace in the Cookbook has
an "Open" action.
 
 * Unit test actions before trying them in a web application.
   ** Since JUnit is integrated in most IDEs now, there is no excuse.
@@ -22,7 +22,7 @@
 
 * Use SiteMesh, or the equivalent, to separate application "chrome" from the core utility
of the server pages.
 
-* Specify the POST method for forums, unless there is a reason to use the default GET method.
+* Specify the POST method for forms, unless there is a reason to use the default GET method.
 
 * If an image, or other swatch of markup, is being used by multiple pages, remove it to its
own server page and include it where necessary.
  ** Better yet, encapsulate the markup in its own UI tag.
@@ -30,7 +30,7 @@
 * Extend the UI tags as needed.
 
 * Consider using the message resources for page titles, control labels, and so forth, even
if the application is not being localized.
- ** It is often useful to seperate the concern of what message to display form the concern
of where to display it.
+ ** It is often useful to seperate the concern of what message to display from the concern
of where to display it.
 
 * Use the XML framework to validate input.
 



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Mime
View raw message