From 91c762cff89d7417bfdcfc5ce7f057acf55b2149 Mon Sep 17 00:00:00 2001
From: Philip Sargent <philip.sargent@gmail.com>
Date: Sat, 16 May 2026 23:11:03 +0100
Subject: [PATCH] typos and comments

---
 templates/new_hole.html | 25 +++++++++++++++----------
 urls.py                 |  2 +-
 2 files changed, 16 insertions(+), 11 deletions(-)

diff --git a/templates/new_hole.html b/templates/new_hole.html
index 31464974..64d30372 100644
--- a/templates/new_hole.html
+++ b/templates/new_hole.html
@@ -84,7 +84,7 @@
 <h3>Instructions</h3>
 <p>Refer to the handbook <a href="/handbook/l/new-cave-form.html">New Cave Datasheet</a> 
 page for what all these mean and how to fill them in.</p>
-<p>If starting from scrastch, read <a href="/handbook/survey/newcave.html">New Cave Process</a>.
+<p>If starting from scratch, read <a href="/handbook/survey/newcave.html">New Cave Process</a>.
 
 <form action="" method="post" enctype="multipart/form-data">
     {% csrf_token %}
@@ -133,26 +133,31 @@ page for what all these mean and how to fill them in.</p>
 </form>
 
 <h3>What this will do:</h3>
-<p>🚧 under construction.
+
 <ul>
 <li>Calculate whether this new cave is in area 1623 or 1626
 <li>Create a <span style="font-variant: small-caps;">fixed point</span> record by inserting into :loser:/fixedpts/gps/auto.svx
-<li>Create a new Cave record with associated new Entrance record 
+<li>Create a new Cave record 
+<li>Create a new Entrance record on that Cave
 <li>Do a git commit (expoweb) of the new Cave and Entrance description files
-<li>Do a git commit (loser) of the new GPS position<br />
+<li>Do a git commit (loser) of the new GPS position fix<br />
  (git commits use your logged-in identity in the "Who are you ?" field)
 <li>Update the database with this new information
 <li>Return you to this form if any important data is missing, invalid or inconsistent
-<li>Take you to the new Wallet for this information and this trip <br />
-  (and create a new digital wallet if it does not already exist)<br />
-  If left blank, it will create the next Wallet number as yet unallocated.
 <li>If all is fine, will take you to <br />
 - the Entrance edit page for you to upload the photos<br />
-- a new Wallet edit page to upload the <em>GPTTest</em> screenshot and trip details
+- a new Wallet edit page to upload the <em>GPTTest</em> screenshot and trip details<br />
+ (and create a new digital wallet if it does not already exist)<br />
 - the GPSlogs upload page to upload your prospecting track<br />
 - the new Survex page to upload survey data (if any)<br />
 - a new Logbook page if you have not already recorded this trip<br />
-
 </ul>
 </p>
-{% endblock %}
\ No newline at end of file
+<h4>Why we ask for the time the GPS was recorded</h4>
+<p>Because ionospheric disturbance happens on a scale of an hour or so, every few hours,
+and is local to an area about ~50km in size. If we continuously record the GPS position
+of the potato hut during the expo then we will know if the GPS 
+position of this cave entrancce was recorded during one of these "bad" periods.</p>
+<p>Go back and re-record the GPS positon the next day at the exact same point and put that data in the logbook.</p>
+{% endblock %}
+<p>🚧 under construction.
\ No newline at end of file
diff --git a/urls.py b/urls.py
index 916f2fa6..e4a44a1d 100644
--- a/urls.py
+++ b/urls.py
@@ -259,7 +259,7 @@ trogglepatterns = [
     re_path(r'^getEntrances/(?P<caveslug>.*)', get_entrances, name = "get_entrances"), 
 
 #   New hole data input
-    path('newhole',  new_hole,  name="new_hole"), 
+    path('newhole',  new_hole,  name="newhole"), 
 #   Cave description pages
     path('cave/<slug:slug>',  caveslugfwd,  name="caveslugfwd"), 
     path('cave_debug',  cave_debug,  name="cave_debug"),