- tidied up some of the web page text

- added volker to the list of developers

(This used to be ctdb commit 1d531c4f9c53fe9b1dc0ccadf5788c0d657cbb1c)

diff --git a/ctdb/web/index.html b/ctdb/web/index.html
index 29df1434e6d5bf2f863c5c4aa40f57fe840c1e52..8cdcce271491f33b3e3e16f3805ec84948b9941d 100644 (file)
--- a/ctdb/web/index.html
+++ b/ctdb/web/index.html
@@ -12,9 +12,9 @@ other projects to store temporary data. If an application is already
 using TDB for temporary data it is very easy to convert that
 application to be cluster aware and use CTDB instead.
 
-<p>CTDB provides the same types of functions as TDB but with the
-difference that it is clustered and thus it appears as a TDB database
-that spans multiple physical hosts in a cluster.
+<p>CTDB provides the same types of functions as TDB but in a clustered
+  fashion, providing a TDB-style database that spans multiple physical
+  hosts in a cluster.
 
 <p>Features include:
 <ul>
@@ -39,25 +39,24 @@ all nodes in a cluster.
 
 <h2>Requirements</h2>
 
-CTDB relies on that a clustered filesystem is available and shared on
+CTDB relies on a clustered filesystem being available and shared on
 all nodes that participate in the CTDB cluster. This filesystem must
 be mounted and available on all nodes in the CTDB cluster.
 
 <p>On top of this cluster filesystem, CTDB then provides clustered HA
 features so that data from the clustered filesystem can be exported
 through multiple nodes in the CTDB cluster using various
-services. Currently this is used to export data off a clustered
-filesystem using Samba (for SMB/CIFS) and NFS to Windows and Unix
-clients.
+services. Currently included with CTDB are the necessary hooks for Samba, NFS
+  and ftp exports. Support for new service types can easily be added.
 
 <h2>TDB</h2>
 
 TDB is a very fast simple database that was originally developed for
 use in Samba. Today several other projects use TDB to store their data.
 
-<p>See <a
-href="http://viewcvs.samba.org/cgi-bin/viewcvs.cgi/branches/SAMBA_4_0/source/lib/tdb/docs/README">TDB
-README file</a> for some description of how TDB is used.
+<p>See the <a
+href="http://samba.org/ftp/unpacked/samba4/source/lib/tdb/docs/README">TDB
+README file</a> for a description of how TDB is used.
 
 <h2>Documentation</h2>
 
@@ -70,7 +69,7 @@ Additional documentation on how to install and configure CTDB is available in th
 <h2>High Availability Features</h2>
 
 The CTDB nodes in a cluster designates one node as a recovery master
-through an election process. If the recovery master node fail a
+through an election process. If the recovery master node fails a
 new election is initiated so that the cluster will always guarantee
 there will be a recovery master. The recovery master will
 continuously monitor the cluster to verify that all nodes contain a
@@ -81,7 +80,7 @@ recovery process when required.
 rebuild/recover all clustered TDB database to ensure that the
 databases are consistent. Recovery typically takes between 1 and 3
 seconds. During the recovery period the databases are 'frozen', and
-all IO operations by ctdb clients are suspended.
+all database IO operations by ctdb clients are suspended.
 
 <h3>Is CTDB a HA solution?</h3>
 
@@ -90,15 +89,16 @@ Yes and no.<p>
 CTDB alone is not a HA solution, but when you combine CTDB with a clustered 
 filesystem it becomes one.<p>
 
-CTDB is primarily developed around the concept of having a shared cluster 
-filesystem shared across all the nodes in the cluster to provide the features
-required for building a NAS cluster.<p>
+CTDB is primarily developed around the concept of having a shared
+cluster filesystem across all the nodes in the cluster to provide the
+features required for building a NAS cluster.<p>
 
-Thus CTDB relies on an external component (the cluster filesystem) to provide 
-the mechanisms for avoiding split-brain and other difficult tasks.<p>
+Thus CTDB relies on an external component (the cluster filesystem) to
+provide the mechanisms for avoiding split-brain and other core
+clustering tasks.<p>
 
-However, If you applications do need a clustered filesystem for all the nodes, 
-in that scenario CTDB will provide a very easy to install and manage 
+However, if you do have a clustered filesystem for all the nodes, in
+that scenario CTDB will provide a very easy to install and manage
 solution for your clustering HA needs.
 
 <h3>IP Takeover</h3>
@@ -135,6 +135,7 @@ projects that want to make their services cluster aware using CTDB.
 <li><a href="http://samba.org/~tridge/">Andrew Tridgell</a><br>
 <li>Ronnie Sahlberg<br>
 <li>Peter Somogyi<br>
+<li><a href="http://sernet.de/Samba/">Volker Lendecke</a><br>
 <ul>
 
 <!--#include virtual="footer.html" -->