Obsolete fixes in documentation.

Author: fredericDelaporte

doc/reference/modules/architecture.xml

@@ -132,8 +132,8 @@
                     <listitem>
                         <para>
                             (Optional) A factory for ADO.NET connections and commands. Abstracts application
-                            from the concrete vendor-specific implementations of <literal>IDbConnection</literal>
-                            and <literal>IDbCommand</literal>. Not exposed to application, but can be
+                            from the concrete vendor-specific implementations of <literal>DbConnection</literal>
+                            and <literal>DbCommand</literal>. Not exposed to application, but can be
                             extended/implemented by the developer.
                         </para>
                     </listitem>

doc/reference/modules/basic_mapping.xml

@@ -681,7 +681,7 @@
 
                 <para>
                     Unfortunately, you can't use <literal>hilo</literal> when supplying your own
-                    <literal>IDbConnection</literal> to NHibernate. NHibernate must be able to
+                    <literal>DbConnection</literal> to NHibernate. NHibernate must be able to
                     fetch the "hi" value in a new transaction.
                 </para>
             </sect3>
@@ -3188,7 +3188,7 @@
             NHibernate's schema evolution tools, to provide the ability to fully define
             a user schema within the NHibernate mapping files.  Although designed specifically
             for creating and dropping things like triggers or stored procedures, really any
-            SQL command that can be run via a <literal>IDbCommand.ExecuteNonQuery()</literal>
+            SQL command that can be run via a <literal>DbCommand.ExecuteNonQuery()</literal>
             method is valid here (ALTERs, INSERTS, etc).  There are essentially two modes for
             defining auxiliary database objects.
         </para>

doc/reference/modules/configuration.xml

@@ -115,8 +115,8 @@ Configuration cfg = new Configuration()
             obtain ADO.NET connections wherever it pleases:
         </para>
 
-        <programlisting><![CDATA[IDbConnection conn = myApp.GetOpenConnection();
-ISession session = sessions.OpenSession(conn);
+        <programlisting><![CDATA[var conn = myApp.GetOpenConnection();
+var session = sessions.OpenSession(conn);
 
 // do some data access work]]></programlisting>
 
@@ -291,7 +291,7 @@ ISession session = sessions.OpenSession(conn);
                     <literal>command_timeout</literal>
                 </entry>
                 <entry>
-                    Specify the default timeout of <literal>IDbCommands</literal>
+                    Specify the default timeout of <literal>DbCommand</literal>s
                     generated by NHibernate.
                 </entry>
             </row>

doc/reference/modules/manipulating_data.xml

@@ -160,7 +160,7 @@ var problems = sess
         <para>
             These given <literal>Set</literal> parameters are used to bind the given values to the
             <literal>?</literal> query placeholders (which map to input
-            parameters of an ADO.NET <literal>IDbCommand</literal>). Just
+            parameters of an ADO.NET <literal>DbCommand</literal>). Just
             as in ADO.NET, you should use this binding mechanism in preference to string
             manipulation.
         </para>

doc/reference/modules/query_queryover.xml

@@ -337,9 +337,9 @@ IList<CatSummary> catReport =
 
         <para>
             In addition to projecting properties, there are extension methods to allow certain common dialect-registered
-            functions to be applied.  For example you can write the following to extract just the year part of a date:
+            functions to be applied.  For example you can write the following to get 3 letters named people.
         </para>
-        <programlisting><![CDATA[        .Where(p => p.BirthDate.YearPart() == 1971)]]></programlisting>
+        <programlisting><![CDATA[        .Where(p => p.FirstName.StrLength() == 3)]]></programlisting>
 
         <para>
             The functions can also be used inside projections:

doc/reference/modules/query_sql.xml

@@ -588,7 +588,7 @@ var pusList = query.SetString("name", "Pus%").List<Cat>();]]></programlisting>
         <itemizedlist spacing="compact">
           <listitem>
             <para>The procedure must return a result set. NHibernate will
-            use <literal>IDbCommand.ExecuteReader()</literal> to obtain
+            use <literal>DbCommand.ExecuteReader()</literal> to obtain
             the results.
             </para>
           </listitem>
@@ -657,7 +657,7 @@ var pusList = query.SetString("name", "Pus%").List<Cat>();]]></programlisting>
 
     <para>The stored procedures are by default required to affect the same number
     of rows as NHibernate-generated SQL would. NHibernate uses
-    <literal>IDbCommand.ExecuteNonQuery</literal> to retrieve the number of rows
+    <literal>DbCommand.ExecuteNonQuery</literal> to retrieve the number of rows
     affected. This check can be disabled by using <literal>check="none"</literal>
     attribute in <literal>sql-insert</literal> element.
     </para>

doc/reference/modules/quickstart.xml

@@ -414,7 +414,7 @@ finally
             NHibernate also offers an object-oriented <emphasis>query by criteria</emphasis> API
             that can be used to formulate type-safe queries, and the Hibernate Query Language (HQL),
             which is an easy to learn and powerful object-oriented extension to SQL.
-            NHibernate of course uses <literal>IDbCommand</literal>s and parameter binding for all
+            NHibernate of course uses <literal>DbCommand</literal>s and parameter binding for all
             SQL communication with the database. You may also use NHibernate's direct SQL query
             feature or get a plain ADO.NET connection from an <literal>ISession</literal> in rare
             cases.