From 26c9d5ed4c8083031978397606d38517c5cb8634 Mon Sep 17 00:00:00 2001
From: Expo on server <expo@expo.survex.com>
Date: Mon, 13 Mar 2023 11:03:09 +0000
Subject: [PATCH] QM process update - online edit of
 handbook/computing/regular.html

---
 handbook/computing/regular.html | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/handbook/computing/regular.html b/handbook/computing/regular.html
index e5ad9a226..685a62fde 100644
--- a/handbook/computing/regular.html
+++ b/handbook/computing/regular.html
@@ -42,7 +42,9 @@ from phones are a bit variable in how they do EOL characters.
 <h3>Tunnel files (Drawings)</h3>
 
 <h3>QMs</h3>
-<p>As the caves get written up, run <a href="scriptsqms.html">svx2qm.py</a> and  <a href="scriptsqms.html">find-dead-qms.py</a> to check that the QMs have all be entered correctly into the svx files and that thecave descriptions have been updated with (a) the new open QMs and (b) the old closed QMs.
+<p>As the caves get written up (i.e. as survex files are written), run the QM reports on the updated caves to check that the QM data appears correctly. Check the DataIssues page for import error messages. 
+  <p> This is now obsolete:
+    <strike>run <a href="scriptsqms.html">svx2qm.py</a> and  <a href="scriptsqms.html">find-dead-qms.py</a> to check that the QMs have all be entered correctly into the svx files and that thecave descriptions have been updated with (a) the new open QMs and (b) the old closed QMs.</strike>
 
 <h3>Survex files</h3>
 Look at the <a href="svxvalid.html">valid SVX refs</a> page to check that new svx files properly reference the wallet folders, and create the wallet folder link back to the svx if the contents.json file in the wallet folder needs updating.