spelchek

phpgwapi/doc/SECURITY

@@ -1,26 +1,26 @@
-First off, I would not recommend using this in a type of enviroment that 
+First off, I would not recommend using this in any type of environment in which
 security is a really big concern.  I am *NOT* saying that you shouldn't be
-concerned about it, but, until the system is thoughly tested.  I would not
+concerned about it.  But, until the system is thoroughly tested, I would not
 recommend it.
 
-Because of the current methods that the email system works.  It is required
+Because of the current methods that the email system uses, it is required
 that the users password is in the sessions table.  IMAP needs the password
 to verify the user.  This is one of the main reasons for the stalesessions
-program.  I do not like keeping passwords in any medium that is not encryped.
+program.  I do not like keeping passwords in any medium that is not encrypted.
 
-The email system stores its file attachments in a temp directory.  For right
-now, you need to watch this directory because it can fill up very quickly.
-If a user does not finsh composing the message (going else where in the program, 
-internet connection dieing, browser crash, etc) the file will sit there until
+The email system stores its file attachments in a temp directory.  For now,
+you need to watch this directory because it can fill up very quickly.
+If a user does not finish composing the message (going else where in the program, 
+Internet connection dieing, browser crash, etc) the file will sit there until
 it is deleted.  There will be a simple cron program to go through and clean
 things up.  
 
 The files/users and files/groups directories need to be writable by the UID
-that php runs under (nobody or your apache UID). This is a security risk
+that php runs under (nobody or your apache UID).  This is a security risk
 if 3rd parties can place php or cgi scripts on your machine, because they
 will have full read/write access to those directories.
 You should also consider moving the files directory outside of the
-tree your webserver has access to to prevent websurfers from directly accessing
+tree your web server has access to to prevent web surfers from directly accessing
 the files, or add in .htaccess files to restrict access to that tree.
 
 Besides this, there is nothing else that I am aware of.  Let me know if you

phpgwapi/doc/etiquette.txt

@@ -33,13 +33,13 @@ important that some basic rules be followed when developing in CVS:
 	project ;)
 
 6.  If you are working in the API, or on some other application which could
-	affect the useability for users and developers, please be sure to fully
+	affect the usability for users and developers, please be sure to fully
 	test your changes.  It is recommended that you visit a large sampling of
 	applications to ensure that they still work as expected after your
 	changes.  This could include the functioning of one application or the
 	API against mysql AND pgsql, at least.  It could also affect the function
 	of an application that uses LDAP instead of SQL for storage and
-	retreival.
+	retrieval.
 
 7.  Do not write table update scripts that alter content or structure of the
 	API or of another application's tables.
@@ -56,7 +56,7 @@ important that some basic rules be followed when developing in CVS:
 	the idsociety template.  Do not put a 31x31 color icon in the idsociety
 	template.
 
-11. Basicly all template files are located in the app_name/templates/default/
+11. Basically, all template files are located in the app_name/templates/default/
 	directory. Please do only commit template files to other app_name/templates/
 	_layout_/directories if they _differ_ from the default version. The same is
 	valid for images. All application images are located in the app_name/templates/