correction

handbook/troggle/scriptsqms.html

@@ -35,18 +35,25 @@ QMs are only useful if they can be easily scanned by people planning the next pu
 
 <p>There are half a dozen ways we have used to manage QMs:
 <ol>
+
 <li><strong>Hand-edited lists of QMS</strong> - only exist for 1623-161 <a href="/1623/161/qmtodo.htm">Kaninchenh&ouml;hle</a>
+
 <li><strong>Perl script</strong> - Historically QMs were not in the survex file but typed up in a separate list <var>qms.csv</var> for 
 each cave system. A perl script turned that into an HTML file for the website. But there appear to be 3 different formats for this. Not currently used.
+
 <li><strong>Perl + troggle</strong> - One of troggle's input parsers "QM parser" is specifically designed to import the three HTML files 
 produced from <var>qms.csv</var> and produces reports by cave and individually, e.g. see <a href="/cave/qms/1623-161">the 161 QMs</a> 
 (slow page), which is <em>old</em> compared with the hand-edited <a href="/1623/161/qmtodo.htm">1623-161</a> page which was derived from it.
+
 <li><strong>troggle and QMs in survex files</strong> - Since Sam wrote this in 2020 we have had the recent QMs in troggle but the report 
 to display them was not written. This has now (July 2022) been fixed. Note that this means some duplication for 1623-161 and a few others.
+
 <li><strong>Python script</strong> - Phil Withnall's 2019 script <em>svx2qm.py</em> scans all the QMs in a single survex file. See below for how to run it on all survex files.
+
 <li><strong>The elderly Prospecting Guide</strong> - Used to cover some of the same sorts of information as needed by someone wanting to 
 chase QMs. It was a troggle-generated document at <a href="/prospecting_guide/">expo.survex.com/prospecting_guide/</a>. 
 It has been retired because the mapping software packages it used were terminally outdated.
+
 </ol>
 
 
@@ -57,7 +64,7 @@ It has been retired because the mapping software packages it used were terminall
 Thus a recent cave such as 1623-264 (Balkh&ouml;hle) will only show QMs imported from the survex files:
 <ul>
 <li>/cave/qms/&lt;caveslug&gt; e.g. <a href="/cave/qms/1623-264/">/cave/qms/1623-264/</a> works (slow page)
-<li>/cave/&lt;caveslug&gt;-&lt;year&gt;&lt;qm_id&gt; e.g. <a href="/cave/qms/1623-264/2019-lipstickdipstick2B">/cave/qms/1623-264/2019-lipstickdipstick2B</a> broken, no data shown
+<li>/cave/&lt;caveslug&gt;-&lt;year&gt;&lt;qm_id&gt; e.g. <a href="/cave/qms/1623-264/2019-lipstic2B">/cave/qms/1623-264/2019-lipstic2B</a> broken, no data shown
 </ul>
 <p>There is an open issue in that although we use the name of the 'block' in the survex file to disambiguate QMs in the same cave and from 
 the same year, it is still possible for blocks to be named non-uniquely. This would crash the system as two QMs would have the same URL.
@@ -96,7 +103,7 @@ Django Admin control panel for manipulating QMs. It is not live as media/js/ is
 <p>Note that the <var>qms.csv</var> file file used as input by this script is an <em>entirely different format and table structure</em> from the <var>qms.csv</var> file produced by <a href="#svx2qm">svx2qm.py</a>.
 
 <p>And in fact the formats of these 3 qm.csv files are <em>not the same</em> (These are the
-"older or artisanal QM formats" referred to by Phil Withnall at th ebottom if this page) :
+"older or artisanal QM formats" referred to by Phil Withnall at the bottom if this page) :
 
 Fields in 204/qm.csv are:
 <code><pre><span style="font-size:small">Number, grade, area, description, page reference, nearest station, completion description, Comment