X-Git-Url: http://git.indexdata.com/?p=idzebra-moved-to-github.git;a=blobdiff_plain;f=doc%2Frecordmodel-domxml.xml;h=5aab33e1920ba9ab0f11df8c4ff2a4dda250ddce;hp=50876cb1d83e2c4473eaf45cc1b3fb9823c44a91;hb=1d5d4f08cb84516d75fcb5e6ed4199b6454cccd6;hpb=97a7adeb9e5059463f039495cc01cfa448463a27

diff --git a/doc/recordmodel-domxml.xml b/doc/recordmodel-domxml.xml
index 50876cb..5aab33e 100644
--- a/doc/recordmodel-domxml.xml
+++ b/doc/recordmodel-domxml.xml
@@ -401,7 +401,8 @@
               <listitem>
                <para>
                 The record is deleted. If the record does not already exist,
-                it is skipped (i.e. nothing is deleted).
+                a warning issued and rest of records are skipped in
+                from the input stream.
                </para>
               </listitem>
              </varlistentry>
@@ -416,6 +417,20 @@
                </para>
               </listitem>
              </varlistentry>
+             <varlistentry>
+              <term><literal>adelete</literal></term>
+              <listitem>
+               <para>
+                The record is deleted. If the record does not already exist,
+                it is skipped (i.e. nothing is deleted).
+               </para>
+               <note>
+                <para>
+                 Requires version 2.0.54 or later.
+                </para>
+               </note>
+              </listitem>
+             </varlistentry>
             </variablelist>
           Note that the value of <literal>type</literal> is only used to
           determine the action if and only if the Zebra indexer is running
@@ -461,7 +476,7 @@
          found. Therefore,
          invalid document processing is aborted, and any content of
          the <literal>&lt;extract&gt;</literal> and 
-         <literal>&lt;store&gt;</literal> pipelines is discarted.
+         <literal>&lt;store&gt;</literal> pipelines is discarded.
           A warning is issued in the logs. 
          </para>
        </listitem>
@@ -819,7 +834,7 @@
    <title>Debuggig &acro.dom; Filter Configurations</title>
    <para>
     It can be very hard to debug a &acro.dom; filter setup due to the many
-    sucessive &acro.marc; syntax translations, &acro.xml; stream splitting and 
+    successive &acro.marc; syntax translations, &acro.xml; stream splitting and 
     &acro.xslt; transformations involved. As an aid, you have always the
     power of the <literal>-s</literal> command line switch to the 
     <literal>zebraidz</literal> indexing command at your hand: