fixup! Obsolete fixes in documentation.

Author: fredericDelaporte

doc/reference/modules/basic_mapping.xml

@@ -2650,7 +2650,7 @@
                             </entry>
                             <entry>
                                 Default when no <literal>type</literal> attribute specified. Does no
-                                more ignore milliseconds since NHibernate v5.0.
+                                longer ignore fractional seconds since NHibernate v5.0.
                             </entry>
                         </row>
                         <row>
@@ -2659,7 +2659,10 @@
                             <entry>
                                 <literal>DbType.DateTime</literal> / <literal>DbType.DateTime2</literal><coref linkend="basic_mapping.datetime-co" />
                             </entry>
-                            <entry><literal>type="DateTimeNoMs"</literal> must be specified. Ignores milliseconds.</entry>
+                            <entry>
+                                <literal>type="DateTimeNoMs"</literal> must be specified. Ignores fractional seconds.
+                                Available since NHibernate v5.0.
+                            </entry>
                         </row>
                         <row>
                             <entry><literal>DateTime2</literal></entry>
@@ -2734,7 +2737,7 @@
                                 <literal>type="LocalDateTime"</literal> must be specified. Ensures the
                                 <literal>DateTimeKind</literal> is set to <literal>DateTimeKind.Local</literal>.
                                 Throws if set with a date having another kind.
-                                Does no more ignore milliseconds since NHibernate v5.0.
+                                Does no longer ignore fractional seconds since NHibernate v5.0.
                             </entry>
                         </row>
                         <row>
@@ -2745,7 +2748,8 @@
                             </entry>
                             <entry>
                                 <literal>type="LocalDateTimeNoMs"</literal> must be specified. Similar to
-                                <literal>type="LocalDateTime"</literal> but ignores milliseconds.
+                                <literal>LocalDateTime</literal> but ignores fractional seconds.
+                                Available since NHibernate v5.0.
                             </entry>
                         </row>
                         <row>
@@ -2836,7 +2840,7 @@
                             <entry>
                                 Ensures the <literal>DateTimeKind</literal> is set to <literal>DateTimeKind.Utc</literal>.
                                 Throws if set with a date having another kind.
-                                Does no more ignore milliseconds since NHibernate v5.0.
+                                Does no longer ignore fractional seconds since NHibernate v5.0.
                             </entry>
                         </row>
                         <row>
@@ -2847,7 +2851,8 @@
                             </entry>
                             <entry>
                                 <literal>type="UtcDateTimeNoMs"</literal> must be specified. Similar to
-                                <literal>type="LocalDateTime"</literal> but ignores milliseconds.
+                                <literal>UtcDateTime</literal> but ignores fractional seconds.
+                                Available since NHibernate v5.0.
                             </entry>
                         </row>
                         <row>

doc/reference/modules/query_linq.xml

@@ -428,15 +428,15 @@ using NHibernate.Linq;]]></programlisting>
       At that point, all defined future results are evaluated in one single round-trip to database.
     </para>
     <programlisting><![CDATA[// Define queries
-IEnumerable<Cat> cats =
+IFutureEnumerable<Cat> cats =
     session.Query<Cat>()
         .Where(c => c.Color == "black")
         .ToFuture();
 IFutureValue<int> catCount =
     session.Query<Cat>()
         .ToFutureValue(q => q.Count());
 // Execute them
-foreach(Cat cat in cats)
+foreach(Cat cat in cats.GetEnumerable())
 {
     // Do something
 }
@@ -447,7 +447,9 @@ if (catCount.Value > 10)
 ]]></programlisting>
     <para>
       In above example, accessing <literal>catCount.Value</literal> does not trigger a round-trip to database:
-      it has been evaluated with <literal>cats</literal> enumeration.
+      it has been evaluated with <literal>cats.GetEnumerable()</literal> call. If instead
+      <literal>catCount.Value</literal> was accessed first, it would have executed both future and
+      <literal>cats.GetEnumerable()</literal> would have not trigger a round-trip to database.
     </para>
   </sect1>
 
@@ -482,6 +484,7 @@ IList<Cat> oldCats =
     oldCatsQuery
         .FetchMany(c => c.AnotherCollection)
         .ToFuture()
+        .GetEnumerable()
         .ToList();]]></programlisting>
     <para>&nbsp;</para>