X-Git-Url: http://git.indexdata.com/?a=blobdiff_plain;f=doc%2Fquerymodel.xml;h=e4fc7db9c4b3690eaebba3e40db0f969bec4a29d;hb=89d16cf15eda0e4802d18b8ad09bd3653508ebfc;hp=da2844ca3226361673461eafd481eb13916f3b2b;hpb=3f837255e2e97bd39ffabb13621d398f5610348c;p=idzebra-moved-to-github.git

diff --git a/doc/querymodel.xml b/doc/querymodel.xml
index da2844c..e4fc7db 100644
--- a/doc/querymodel.xml
+++ b/doc/querymodel.xml
@@ -1,5 +1,4 @@
  <chapter id="querymodel">
-  <!-- $Id: querymodel.xml,v 1.33 2007-05-25 12:17:11 adam Exp $ -->
   <title>Query Model</title>
   
   <section id="querymodel-overview">
@@ -922,7 +921,7 @@
       The relation attributes 1-5 are supported and work exactly as
       expected.
       All ordering operations are based on a lexicographical ordering, 
-      <emphasis>expect</emphasis> when the 
+      <emphasis>except</emphasis> when the 
       structure attribute numeric (109) is used. In
       this case, ordering is numerical. See 
       <xref linkend="querymodel-bib1-structure"/>.
@@ -1562,7 +1561,7 @@
      
      <para>
       All ordering operations are based on a lexicographical ordering, 
-      <emphasis>expect</emphasis> when the 
+      <emphasis>except</emphasis> when the 
       <literal>structure attribute numeric (109)</literal> is used. In
       this case, ordering is numerical. See 
       <xref linkend="querymodel-bib1-structure"/>.
@@ -1768,9 +1767,9 @@
        </row>
        <row>
 	<entry>Approximative Limit</entry>
-	<entry>9</entry>
+	<entry>12</entry>
 	<entry>scan</entry>
-	<entry>1.4</entry>
+	<entry>2.0.20</entry>
        </row>
       </tbody>
      </tgroup>
@@ -1821,9 +1820,9 @@
     </section>
 
     <section id="querymodel-zebra-attr-approx">
-     <title>&zebra; Extension Approximative Limit (type 11)</title>
+     <title>&zebra; Extension Approximative Limit (type 12)</title>
      <para>
-      The &zebra; Extension Approximative Limit (type 11) is a way to
+      The &zebra; Extension Approximative Limit (type 12) is a way to
       enable approximate hit counts for scan hit counts, in the same
       way as for search hit counts. 
      </para>