Revision: 1587
          http://svn.sourceforge.net/spring-rich-c/?rev=1587&view=rev
Author:   kevinstembridge
Date:     2006-11-28 15:41:58 -0800 (Tue, 28 Nov 2006)

Log Message:
-----------
Minor spelling and grammar fixes

Modified Paths:
--------------
    trunk/spring-richclient/src/site/apt/development/conventions.apt

Modified: trunk/spring-richclient/src/site/apt/development/conventions.apt
===================================================================
--- trunk/spring-richclient/src/site/apt/development/conventions.apt    
2006-11-28 23:35:13 UTC (rev 1586)
+++ trunk/spring-richclient/src/site/apt/development/conventions.apt    
2006-11-28 23:41:58 UTC (rev 1587)
@@ -20,9 +20,9 @@
     * We follow {{{http://www.springframework.org/development}Spring's 
conventions}}, which are a dialect of
     {{{http://java.sun.com/docs/codeconv/}Sun coding conventions for Java}}, 
with these few differences:
 
-        * The maximum is line length is 120 chars instead of 80 chars.
+        * The maximum line length is 120 chars instead of 80 chars.
 
-        * Identation is done by tabs of 4 spaces.
+        * Indentation is done by tabs of 4 spaces.
 
         * A new line before <<<else>>>, <<<catch>>> and <<<finally>>>.
 
@@ -48,13 +48,13 @@
 Build process
 
     The project root pom is the (in)direct parent pom of all module poms.
-    Therefor dependency configuration is inherited.
+    Therefore dependency configuration is inherited.
 
     * All versions should be specified in the project root pom: never in a 
module pom.
 
     * All poms should only depend on their direct dependencies.
 
-    * Dependency scope is ussually defined in the project root pom.xml (under 
discussion)
+    * Dependency scope is usually defined in the project root pom.xml (under 
discussion)
 
     * Dependencies should be marked optional (if they are optional) in the 
module pom. 
 
@@ -72,4 +72,4 @@
 
 * Site documentation
 
-    * All apt/fml/xdoc files should be in camelCase starting with a low letter.
+    * All apt/fml/xdoc files should be in camelCase starting with a lower case 
letter.


This was sent by the SourceForge.net collaborative development platform, the 
world's largest Open Source development site.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
spring-rich-c-cvs mailing list
spring-rich-c-cvs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/spring-rich-c-cvs

Reply via email to