[gnome-devel-docs] Update prose for GDA platform demo fixes

[David King <davidk src gnome org>]

commit 837617188ff6cc6c234077a8c3b4604cbb3393e6
Author: David King <amigadave amigadave com>
Date:   Mon Sep 14 07:41:28 2015 +0100

    Update prose for GDA platform demo fixes

 platform-demos/C/record-collection.js.page |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/platform-demos/C/record-collection.js.page b/platform-demos/C/record-collection.js.page
index 2df650d..d9c98ac 100644
--- a/platform-demos/C/record-collection.js.page
+++ b/platform-demos/C/record-collection.js.page
@@ -202,7 +202,7 @@ Gtk.main ();]]></code>
     <item><p>Line 4: Open the connection. In the SQLite provider, if the database does not exist, it will be 
created in this step.</p></item>
     <item>
       <p>Lines 6&#x2012;10: Try to do a simple select to check if the table exists (line 7). If it does not 
exist (because the database was just created), this command will raise an exception, which is handled by the 
<code>try</code>...<code>catch</code> block. If it is the case, we run the create table statement (line 
9).</p>
-      <p>In order to run the SQL commands above we are using global GDA functions, 
<code>execute_select_command</code> and <code>execute_non_select_command</code>. They are simple to use, and 
just require two arguments: The <code>Connection</code> object and the SQL command to be parsed.</p>
+      <p>In order to run the SQL commands above we are using the GDA connection methods 
<code>execute_select_command</code> and <code>execute_non_select_command</code>. They are simple to use, and 
just require two arguments: The <code>Connection</code> object and the SQL command to be parsed.</p>
     </item>
   </list>
 
@@ -232,7 +232,7 @@ Gtk.main ();]]></code>
     this.count_label.label = "<i>" + dm.get_n_rows () + " record(s)</i>";
   },]]></code>
   <list>
-    <item><p>Line 2: The <code>SELECT</code> command. We are using the global GDA's function 
<code>execute_select_command</code> for that. It returns a <code>DataModel</code> object, which is later used 
to retrieve the rows.</p></item>
+    <item><p>Line 2: The <code>SELECT</code> command. We are using the GDA connection's 
<code>execute_select_command</code> method for that. It returns a <code>DataModel</code> object, which is 
later used to retrieve the rows.</p></item>
     <item><p>Line 3: Create an <code>Iter</code> object, which is used to iterate over the 
<code>DataModel</code>'s records.</p></item>
     <item><p>Line 7: Loop through all the records, fetching them with the help of the <code>Iter</code> 
object. At this point, the <code>iter</code> variable contains the actual, retrieved data. Its 
<code>move_next</code> method returns <code>false</code> when it reaches the last record.</p></item>
     <item>
@@ -272,7 +272,7 @@ Gtk.main ();]]></code>
     this.selectData ();
   },]]></code>
   <p>
-    We have learned how to use GDA's convenience functions <code>execute_select_command</code> and 
<code>execute_non_select_command</code> to quickly execute SQL commands on the database. GDA allows one to 
build a SQL statement indirectly, by using its <code>SqlBuilder</code> object. What are the benefits of this? 
GDA will generate the SQL statement dynamically, and it will be valid for the connection provider used (it 
will use the same SQL dialect the provider uses). Let's study the code:
+    We have learned how to use the GDA connection's methods <code>execute_select_command</code> and 
<code>execute_non_select_command</code> to quickly execute SQL commands on the database. GDA allows one to 
build a SQL statement indirectly, by using its <code>SqlBuilder</code> object. What are the benefits of this? 
GDA will generate the SQL statement dynamically, and it will be valid for the connection provider used (it 
will use the same SQL dialect the provider uses). Let's study the code:
   </p>
   <list>
     <item><p>Lines 2&#x2012;3: Check if the user filled all the fields. The code for the private method 
<code>_validateFields</code> is really simple and you can read it in the full demo source code.</p></item>