# HG changeset patch
# User Henry S. Thompson <ht@markup.co.uk>
# Date 1497280814 -7200
# Node ID b66bcfae65d63b75893eb171bdbd0343c6d0a178
# Parent  d0edaceb04b6b9fd3f25e78a76324140a0e69f38
consistent defn style

diff -r d0edaceb04b6 -r b66bcfae65d6 annotate.xml
--- a/annotate.xml	Mon Jun 12 17:08:07 2017 +0200
+++ b/annotate.xml	Mon Jun 12 17:20:14 2017 +0200
@@ -54,7 +54,7 @@
    <title>Annotator-supplied features</title>
    <div>
     <title>All types</title>
-    <list type="defn">
+    <list type="1defn">
      <item term="comment">string: unconstrained.  By its nature difficult to
 exploit, really should only be used to document a problem with the available
 feature&amp;value vocabulary or structure.</item>
@@ -62,13 +62,13 @@
    </div>
    <div>
     <title>Both one-dimensional types</title>
-    <list type="defn">
+    <list type="1defn">
      <item term="type">string: <code>"data"|"key"|"label"</code>
       <p>"key" is my preferred word for what Dresden call "attribute".  In the
-simpler cases, think of it as what you might use in an HLOOKUP or VLOOKUP cell.</p>
+simpler cases, think of it as what you find as the first row/column of the 2nd argument to an HLOOKUP/VLOOKUP call.</p>
      </item>
      <item term="content">fvd:
-      <list type="defn">
+      <list type="1defn">
        <item term="type">string: <code>"currency"|"date"|"datetime"|"integer"|"float"|"key"|"label"|"string"|"time"</code></item>
       </list>
       <p>The "key" and "label" content types are for use (as in the Dresden
@@ -78,10 +78,10 @@
    </div>   
    <div>
     <title>Matrices</title>
-    <list type="defn">
+    <list type="1defn">
      <item term="type">string: <code>"table"|"data"|"label"|"condition"</code></item>
      <item term="content">fvd:
-      <list>
+      <list type="1defn">
        <item term="type">string: <code>"rows"|"columns"|"cells"</code></item>
       </list>
      </item>