[libgda] Corrected bug #651692 (thanks to Christian Kirbach)

[Vivien Malerba <vivien src gnome org>]

commit b1d4c5e570bb23b40cc195fe779089e7b0e13377
Author: Vivien Malerba <malerba gnome-db org>
Date:   Thu Jun 2 13:33:15 2011 +0200

    Corrected bug #651692 (thanks to Christian Kirbach)

 tools/browser/help/C/actions.page                  |    2 +-
 tools/browser/help/C/ldap-browser-perspective.page |    2 +-
 tools/browser/help/C/ldap-connections.page         |   12 ++++++------
 tools/browser/help/C/sql-sqlite.page               |    8 ++++----
 tools/browser/help/C/virtual-connections.page      |    2 +-
 5 files changed, 13 insertions(+), 13 deletions(-)
---
diff --git a/tools/browser/help/C/actions.page b/tools/browser/help/C/actions.page
index 42f9b98..fb2972b 100644
--- a/tools/browser/help/C/actions.page
+++ b/tools/browser/help/C/actions.page
@@ -18,7 +18,7 @@
   </p>
   <p>
     An action can be defined to show all the entries in the "comments" table provided
-    the key is defining a product. Then anytime a product is listed in a resultset, the
+    the key is defining a product. Then anytime a product is listed in a result set, the
     contextual menu will allow the user to execute this action and thus display all
     the comments on the selected product. This situation is illustrated in the following figures.
   </p>
diff --git a/tools/browser/help/C/ldap-browser-perspective.page b/tools/browser/help/C/ldap-browser-perspective.page
index 5c50841..07e4494 100644
--- a/tools/browser/help/C/ldap-browser-perspective.page
+++ b/tools/browser/help/C/ldap-browser-perspective.page
@@ -55,7 +55,7 @@
   Links in these tabs (identified by blue and underlined text) open a new tab, or use the first tab next
   to the current tab to display information about the selected link. For example in the figure above illustrating
   an LDAP entries tab, clicking on
-  the "inetOrgPerson" will open a new "LDAP classes" tab and disply the information about that class.
+  the "inetOrgPerson" will open a new "LDAP classes" tab and display the information about that class.
 </p>
 
 </page>
diff --git a/tools/browser/help/C/ldap-connections.page b/tools/browser/help/C/ldap-connections.page
index 234e446..c1d033a 100644
--- a/tools/browser/help/C/ldap-connections.page
+++ b/tools/browser/help/C/ldap-connections.page
@@ -9,7 +9,7 @@
   <title>LDAP connections</title>
   <p>
     LDAP connections are different than other connections in a way that an LDAP database stores data in
-    a hierarchical way, in the DIT (Directory Information Tree), whereas other databases acessible using
+    a hierarchical way, in the DIT (Directory Information Tree), whereas other databases accessible using
     the <app>gda-browser</app> application are relational databases.
   </p>
   <p>
@@ -39,7 +39,7 @@
       then the top level entry of the LDAP connection is used)</p></item>
       <item><p>the search filter: a valid LDAP search filter (if none is provided then the default 
       search filter is "(objectClass=*)", requesting any LDAP entry).</p></item>
-      <item><p>the attributes: the attributes to retreive, each attribute will be mapped to a column of the
+      <item><p>the attributes: the attributes to retrieve, each attribute will be mapped to a column of the
       table. The attributes must be a comma separated list of attributes, where each attribute can optionally
       be assigned a type and a multi value option (see below).</p></item>
       <item><p>the scope: the search scope, "subtree" (to search the base DN and the entire sub tree below),
@@ -60,7 +60,7 @@
   <section id="ldap-columns-mapping">
     <title>Attributes to columns mapping</title>
     <p>
-      As mentionned in the previous section, each attribute will be mapped to a column. The column type
+      As mentioned in the previous section, each attribute will be mapped to a column. The column type
       is normally automatically determined (string, number, ...) but can be forced by appending to the attribute
       name the "::&lt;type&gt;" for the requested type.
     </p>
@@ -76,7 +76,7 @@
       This only works for string attribute types.</p></item>
       <item><p>"MULT" or "*": a row will be returned for each value of the attribute, effectively
       multiplying the number of returned rows</p></item>
-      <item><p>"1": only the first vakue of the attribute will be used, the other values ignored</p></item>
+      <item><p>"1": only the first value of the attribute will be used, the other values ignored</p></item>
       <item><p>"CONCAT": the attributes' values are concatenated (with a newline char
       between each value)</p></item>
       <item><p>"ERROR": an error value will be returned (this is the default behaviour)</p></item>
@@ -84,7 +84,7 @@
   </section>
 
   <section id="ldap-ddl-sql">
-    <title>SQL useable with LDAP connections</title>
+    <title>SQL usable with LDAP connections</title>
     <p>
       You can use the SQL understood by <link href="http://sqlite.org/lang.html";>SQLite</link> in any LDAP
       connection. Be aware however that if you define database objects (outside of the extended SQL
@@ -102,7 +102,7 @@
   </section>
 
   <section id="ldap-sql">
-    <title>SQL extension to hande LDAP tables</title>
+    <title>SQL extension to handle LDAP tables</title>
     <p>
       LDAP tables can be created using an extended set of SQL commands:
     </p>
diff --git a/tools/browser/help/C/sql-sqlite.page b/tools/browser/help/C/sql-sqlite.page
index 4f92bb1..42620f0 100644
--- a/tools/browser/help/C/sql-sqlite.page
+++ b/tools/browser/help/C/sql-sqlite.page
@@ -12,15 +12,15 @@
     are the same.
   </p>
   <p>
-    All the SQL understood by <link href="http://sqlite.org/lang.html";>SQLite</link> is useable
-    in these connections, with the limitations and modifications detailled in the next sections.
+    All the SQL understood by <link href="http://sqlite.org/lang.html";>SQLite</link> is usable
+    in these connections, with the limitations and modifications detailed in the next sections.
   </p>
 
   <section id="sql-sqlite-dbobjects">
     <title>Database objects</title>
     <p>
       It is possible to create database objects (tables, views, ...) but these will be lost when the
-      connection is closed. The only "persistant" objects are the ones automatically created
+      connection is closed. The only "persistent" objects are the ones automatically created
       when the connection is opened (and they contain no data as they are merely proxies to
       other sources of data).
     </p>
@@ -30,7 +30,7 @@
     <title>Extra available functions</title>
     <p>
       All the functions provided by <link href="http://sqlite.org/lang_corefunc.html";>SQLite</link>
-      are useable in these connections, and a few other ones have been added:
+      are usable in these connections, and a few other ones have been added:
     </p>
     <list>
       <item>
diff --git a/tools/browser/help/C/virtual-connections.page b/tools/browser/help/C/virtual-connections.page
index 2afaf22..7228fc7 100644
--- a/tools/browser/help/C/virtual-connections.page
+++ b/tools/browser/help/C/virtual-connections.page
@@ -126,7 +126,7 @@ WHERE "Error code"=0
   </section>
 
   <section id="virtual-ddl-sql">
-    <title>SQL useable with virtual connections</title>
+    <title>SQL usable with virtual connections</title>
     <p>
       You can use the SQL understood by <link href="http://sqlite.org/lang.html";>SQLite</link> in any virtual
       connection. Be aware however that if you define database objects (outside of the extended SQL