First attempt at converting "sig" to "activity" for v3

templates/add-spot.html

@@ -41,14 +41,14 @@
                     </select>
                 </div>
                 <div class="col-auto">
-                    <label for="sig" class="form-label">Activity</label>
-                    <select id="sig" class="form-select">
+                    <label for="activity" class="form-label">Activity</label>
+                    <select id="activity" class="form-select">
                         <option value="" selected></option>
                     </select>
                 </div>
                 <div class="col-auto">
-                    <label for="sig-ref" class="form-label">Activity Reference</label>
-                    <input type="text" class="form-control input-narrow" id="sig-ref" placeholder="e.g. GB-0001">
+                    <label for="activity-ref" class="form-label">Activity Reference</label>
+                    <input type="text" class="form-control input-narrow" id="activity-ref" placeholder="e.g. GB-0001">
                 </div>
                 <div class="col-auto">
                     <label for="dx-grid" class="form-label">DX Grid</label>

templates/help/usage/clients.html

@@ -23,7 +23,7 @@
         which you can automatically use to generate a client skeleton using various software.
     </li>
     <li>Call the main "spots" or "alerts" API endpoints to get the data you want. For example, your app could call
-        <code>https://spothole.app/api/v2/spots</code> once every few minutes. Apply filters if necessary.
+        <code>https://spothole.app/api/v3/spots</code> once every few minutes. Apply filters if necessary.
     </li>
     <li>Call the "options" API to get an idea of which bands, modes etc. the server knows about. You might want to do
         that first before calling the spots/alerts APIs, to allow you to populate your filters correctly.
@@ -38,11 +38,11 @@
     once every two minutes, so if your client is interested in POTA data there's no need to poll Spothole any more often
     than that.</p>
 <p>If you absolutely must be informed within seconds of a spot arriving in Spothole, please use the SSE endpoints
-    instead, e.g. <code>https://spothole.app/api/v2/spots/stream</code>.</p>
+    instead, e.g. <code>https://spothole.app/api/v3/spots/stream</code>.</p>
 <p>If you want to handle different types of spot or alert differently within your client, please consider making a
     single request to the Spothole API to retrieve all the data, then filtering on your side. For example, call
-    <code>https://spothole.app/api/v2/spots?sig=POTA,SOTA</code> rather than making two separate calls to
-    <code>https://spothole.app/api/v2/spots?sig=POTA</code> and <code>https://spothole.app/api/v2/spots?sig=SOTA</code>.
+    <code>https://spothole.app/api/v3/spots?activity=POTA,SOTA</code> rather than making two separate calls to
+    <code>https://spothole.app/api/v3/spots?activity=POTA</code> and <code>https://spothole.app/api/v3/spots?activity=SOTA</code>.
 </p>
 <p>Remember, here at Spothole Inc. we offer an industry-standard "five nines" uptime on our server, with our own unique
     twist: we don't tell you which side of the decimal point the nines start! (Translation: This is a hobby project.

templates/help/usage/embedding.html

@@ -13,7 +13,7 @@
 <p>These are supplied with the URL to the page you want to embed, for example for an embedded version of the band map in
     dark mode, use <code>https://spothole.app/bands?embedded=true&amp;dark-mode=true</code>. For an embedded version of
     the main spots/home page in the system light/dark mode, use <code>https://spothole.app/?embedded=true</code>. For
-    dark mode showing 70cm TOTA spots only, use <code>https://spothole.app/?embedded=true&amp;dark-mode=true&amp;sig=TOTA&amp;band=70cm</code>.
+    dark mode showing 70cm TOTA spots only, use <code>https://spothole.app/?embedded=true&amp;dark-mode=true&amp;activity=TOTA&amp;band=70cm</code>.
     Providing no URL params causes the page to be loaded in the normal way it would when accessed directly in the user's
     browser.</p>
 <p>The supported parameters are as follows. Generally these match the equivalent parameters in the real Spothole API,
@@ -82,10 +82,10 @@
             </td>
         </tr>
         <tr>
-            <td><code>sig</code></td>
+            <td><code>activity</code></td>
             <td>Comma-separated list</td>
             <td>(all)</td>
-            <td><code>?sig=POTA,SOTA,NO_SIG</code></td>
+            <td><code>?activity=POTA,SOTA,NO_ACTIVITY</code></td>
             <td>Sets the list of activities that will be shown on the spots, bands and map pages. Available options
                 match the labels of the buttons in the standard web interface.
             </td>

templates/status.html

@@ -82,7 +82,7 @@
     <div class="card-header">
         Activity Reference Data Providers
     </div>
-    <div class="card-body" id="sig_ref_data_providers-status-container">
+    <div class="card-body" id="activity_ref_data_providers-status-container">
 
     </div>
 </div>