bh: doc/architecture server.sgml,1.36,1.37

[cvs at kolab.org]

Author: bh

Update of /kolabrepository/doc/architecture
In directory doto:/tmp/cvs-serv29923/architecture

Modified Files:
	server.sgml 
Log Message:
Fix some typos


Index: server.sgml
===================================================================
RCS file: /kolabrepository/doc/architecture/server.sgml,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -d -r1.36 -r1.37
--- server.sgml	20 Apr 2005 11:10:53 -0000	1.36
+++ server.sgml	1 Aug 2006 16:21:09 -0000	1.37
@@ -63,7 +63,7 @@
 
 <sect2><title> Top Level LDAP Structure </title>
 <para> It is difficult to find a commonly accepted LDAP scheme.
-It seems, most real life LDAP installations go for the domain oriented apporach
+It seems, most real life LDAP installations go for the domain oriented approach
 and lay out the structure after an existing domain/subdomain structure.</para>
 <para> The most widely accepted and standardized object for storing personal data
 clearly is "inetOrgPerson".</para>
@@ -174,7 +174,7 @@
 
 # kolabEncryptedPassword is an asymmetrically (RSA) encrypted copy of the
 # cleartext password. This is required in order to pass the password from
-# the maintainance/administration application to the kolabHomeServer running the
+# the maintinance/administration application to the kolabHomeServer running the
 # resource handler application in a secure maner
 attributetype ( 1.3.6.1.4.1.19419.2.1.4
   NAME 'kolabEncryptedPassword'
@@ -1556,7 +1556,7 @@
 <para>With Kolab 3.0 we will use Apache mod_rewrite modules in order to have a transparent server side support for legacy Kolab clients. We use this mod_rewrite in order to process the download requests with a php script, fetch the required freebusy list from the appropriate Kolab server and then present the result to the requesting client.
 </para>
 </sect1>
-<sect1><title> Maintainance of Kolab server </title>
+<sect1><title> Maintenance of Kolab server </title>
 <para>
 </para>
 <sect2><title> Installation of Kolab server </title>
@@ -1564,10 +1564,10 @@
 </para>
 </sect2>
 <sect2><title> Upgrade of Kolab server </title>
-<para>It is save to expect that for security reasons, new features or bugfixes a new release of
+<para>It is safe to expect that for security reasons, new features or bugfixes a new release of
 the Kolab server is often desirable.</para>
 <para>We use the same <filename>obmtool</filename> for upgrading which is used for installing the Kolab server.</para>
-<para>A save method for updating in case a short downfime is acceptable is first to become the superuser of the system and then
+<para>A safe method for updating in case a short downfime is acceptable is first to become the superuser of the system and then
 get the proper shell environment. Afterwards the new kolab rpm packages get installed and compiled if required.
 The <filename>obmtool</filename> takes care about downloading further required packages automatically. The intermediate
 <filename>kolabconf</filename> which happens to depend on OpenLDAP is sometimes mandatory for doing an update of the