[libgda/LIBGDA_4.2] Correction for bug #Bug 651178



commit 8b2cfb65af273c80cfbbb7ae5ea4787a6c56469a
Author: Vivien Malerba <malerba gnome-db org>
Date:   Thu May 26 21:05:01 2011 +0200

    Correction for bug #Bug 651178
    
    doc: couple of spelling and other fixes (thanks to Christian Kirbach)

 tools/browser/help/C/actions.page             |    2 +-
 tools/browser/help/C/features.page            |    2 +-
 tools/browser/help/C/table-insert-data.page   |    4 ++--
 tools/browser/help/C/virtual-connections.page |    8 ++++----
 4 files changed, 8 insertions(+), 8 deletions(-)
---
diff --git a/tools/browser/help/C/actions.page b/tools/browser/help/C/actions.page
index 9d05ef8..42f9b98 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 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 resultset, 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/features.page b/tools/browser/help/C/features.page
index 915058f..9019a20 100644
--- a/tools/browser/help/C/features.page
+++ b/tools/browser/help/C/features.page
@@ -33,7 +33,7 @@
       The activities are grouped by theme around the notion of <link type="topic" xref="general-ui">perspectives</link>, the following are currently implemented:
     </p>
     <list>	
-      <item><p>analyse the database schema (tables, relations, ...), see the
+      <item><p>analyse the database schema (tables, relations, ...), see 
       the <link xref="schema-browser-perspective">Schema browser perspective</link></p></item>
       <item><p>execute SQL commands, see the
       <link xref="query-execution-perspective">Query execution perspective</link></p></item>
diff --git a/tools/browser/help/C/table-insert-data.page b/tools/browser/help/C/table-insert-data.page
index abd588a..5300d2d 100644
--- a/tools/browser/help/C/table-insert-data.page
+++ b/tools/browser/help/C/table-insert-data.page
@@ -32,13 +32,13 @@
 	<list>
 	  <item><p>Red: means the current value in the data entry is invalid</p></item>
 	  <item><p>Blue: means the current value in the data entry is unused and the column's default value
-	      will be used instead (usefull for example for auto incremented columns)</p></item>
+	      will be used instead (useful for example for auto incremented columns)</p></item>
 	  <item><p>Green: means the current value in the data entry is NULL</p></item>
 	  <item><p>Same color as the rest of the UI: means none of the above situations apply</p></item>
 	</list>
     </item>
     <item><p>Columns which are foreign keys to other tables are presented as a drop down combo box where
 	you can only choose among the values in the referenced table (hint: to have that values list
-	refresned you should close the popup dialog and reopen it);</p></item>
+	refreshed you should close the popup dialog and reopen it);</p></item>
   </list>
 </page>
diff --git a/tools/browser/help/C/virtual-connections.page b/tools/browser/help/C/virtual-connections.page
index c0ec791..45a0a7e 100644
--- a/tools/browser/help/C/virtual-connections.page
+++ b/tools/browser/help/C/virtual-connections.page
@@ -6,14 +6,14 @@
     <link type="guide" xref="features"/>
     <link type="guide" xref="index#connections"/>
   </info>
-  <title>Connections binding (ie. virtual connections)</title>
+  <title>Connections binding (i.e. virtual connections)</title>
   <p>
     Connection binding is a feature which allows to "bind" several connections and/or imported
     data sets into a single connection, which can be used almost like a regular connection.
   </p>
   <p>
-    This feature is usefull when one needs to execute an SQL command (for example to extract data)
-    takinginto account data actually stored in different databases. Without this feature, the way
+    This feature is useful when one needs to execute an SQL command (for example to extract data)
+    taking into account data actually stored in different databases. Without this feature, the way
     to achieve the same result is by exporting the necessary data from each database and work on
     the data outside of the databases.
   </p>
@@ -39,7 +39,7 @@
   <section id="vcnc-use-case">
     <title>Use case for virtual connections</title>
     <p>
-      To illustrate virtual connection usage, let's define a simple use case and see how it's usefull. Suppose you have
+      To illustrate virtual connection usage, let's define a simple use case and see how it's useful. Suppose you have
       a database which contains the list of servers which you are responsible for. For simplicity, let's assume that
       the database contains a table named "server" with the following definition:
     </p>



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]