[Webapps-common-discuss] webapps-common/doc Webapps-Policy-Manual-DRAFT.txt,1.9,1.10

neilm@haydn.debian.org neilm@haydn.debian.org


Update of /cvsroot/webapps-common/webapps-common/doc
In directory haydn:/tmp/cvs-serv11047

Modified Files:
	Webapps-Policy-Manual-DRAFT.txt 
Log Message:
Spelling corrections


Index: Webapps-Policy-Manual-DRAFT.txt
===================================================================
RCS file: /cvsroot/webapps-common/webapps-common/doc/Webapps-Policy-Manual-DRAFT.txt,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- Webapps-Policy-Manual-DRAFT.txt	9 May 2005 12:18:55 -0000	1.9
+++ Webapps-Policy-Manual-DRAFT.txt	9 May 2005 12:38:09 -0000	1.10
@@ -48,7 +48,7 @@
     2.2 Configuration Files and Customizable Content
     2.3 Static files
     2.4 Database issues
-    2.5 Architecture independant scripts (Perl, PHP and others)
+    2.5 Architecture independent scripts (Perl, PHP and others)
     2.6 Architecture dependant scripts
 
   3 Libraries for the web applications
@@ -113,7 +113,7 @@
 ---------------------------------------------------------------------
 
 Packaging a web application is much hard than it could seem in the first place.
-A web application comes with a couple of kinds of files wich should be handled 
+A web application comes with a couple of kinds of files which should be handled 
 with care. 
 
 This section will cover every common issue a webapp maintainer can face. Most of
@@ -133,7 +133,7 @@
 type of file                                location
 static web pages                            /usr/share/PACKAGE/www*
 dynamically interpreted web pages           /usr/share/PACKAGE/www*
-dynamcially executed web pages              /usr/lib/cgi-bin/PACKAGE**
+dynamically executed web pages              /usr/lib/cgi-bin/PACKAGE**
 application-specific libraries              /usr/share/PACKAGE/include***
 site configuration (settings/passwords)     /etc/PACKAGE
 locally modifiable/overridable content      /etc/PACKAGE****
@@ -172,10 +172,10 @@
 Webapp configuration files will likely need to have permissions and ownership
 different from the standard root:root ownership and 644 permissions.  The most
 notable reason for this is that the webserver usually needs the ability to
-read some of these configuration files.  note that some applicatoins provide
+read some of these configuration files.  note that some applications provide
 the ability to edit their configuration via a web-based interface.  in such
 a case, the files should be writable by the www-data group.  the local
-administrator should always be able to prevent this behavior by changing the
+administrator should always be able to prevent this behaviour by changing the
 file permissions via dpkg-statoverride.
 
 the following table reflects the requirements for configuration file
@@ -192,7 +192,7 @@
 2.2 Static files
 
 Every files needed by the web application and provided as static content (html,
-images or css) are called in this document "sattic files".
+images or css) are called in this document "static files".
 
 There are a couple of static files:
 
@@ -211,12 +211,12 @@
 
 Every static files provided by the package are considered read-only data.
 The user should not touch those files. This is the default version of the static
-content needed bythe application.
+content needed by the application.
 
 Thus, every static file should be put under /usr/share/$package.
 
 If there is a way to provide an alternate location for the static contents, the
-user could be pointed to the /usr/local/$package directory and should be adviced
+user could be pointed to the /usr/local/$package directory and should be advised
 to copy the /usr/share/$package content inside.
 He will then be able to handle his modifications safely.
 
@@ -225,13 +225,13 @@
 2.3 Database issues
 
 If the web application needs a database to run properly, the maintainer must use
-the dbconfig-common package to perform the databse configuration.
+the dbconfig-common package to perform the database configuration.
 
 See the dbconfig-common manual for details...
 
 FIXME: more details, reference...
 
-2.4 Architecture independant scripts (Perl, PHP and others)
+2.4 Architecture independent scripts (Perl, PHP and others)
 
 FIXME