d661fb8d19ed9e1a9f2aef1ed7f26774a3f03b83
gperez2
  Wed Aug 21 18:32:34 2024 -0700
Changing the db parameter to genome since db does not seem to be working for a GenArk URL, refs #33580

diff --git src/hg/htdocs/goldenPath/help/hgTrackHubHelp.html src/hg/htdocs/goldenPath/help/hgTrackHubHelp.html
index 9bfc413..00cceb5 100755
--- src/hg/htdocs/goldenPath/help/hgTrackHubHelp.html
+++ src/hg/htdocs/goldenPath/help/hgTrackHubHelp.html
@@ -901,31 +901,31 @@
 <pre><code>genome hg38
 trackDb hg38/trackDb.txt
 <strong>groups</strong> groups.txt</code></pre>
 
 <p>
 An example &quot;genomes.txt&quot; file, which includes the hg38 genome, a GenArk assembly, and an
 assembly hub, is available here:
 <a href="/goldenPath/help/examples/hubExamples/hubGroupings/groupsExample/genomes.txt" 
 target="_blank">genomes.txt</a>.</p>
 
 <p>
 By attaching the hub with these group settings, the tracks will be displayed within the specified groups. Below are URLs showing the group settings for the hg38 genome, a GenArk assembly, and an assembly hub:</p>
 <ul>
    <li><b>hg38</b>: <a href="../../cgi-bin/hgTracks?hubUrl=https://genome.ucsc.edu/goldenPath/help/examples/hubExamples/hubGroupings/groupsExample/hub.txt&db=hg38" 
 target="_blank">hg38 Genome</a>.</p></li>
-   <li><b>GCF_000951035.1</b>: <a href="../../cgi-bin/hgTracks?hubUrl=https://genome.ucsc.edu/goldenPath/help/examples/hubExamples/hubGroupings/groupsExample/hub.txt&db=GCF_000951035.1" 
+   <li><b>GCF_000951035.1</b>: <a href="../../cgi-bin/hgTracks?hubUrl=https://genome.ucsc.edu/goldenPath/help/examples/hubExamples/hubGroupings/groupsExample/hub.txt&genome=GCF_000951035.1" 
 target="_blank">GenArk Assembly</a>.</p></li>
    <li><b>Arabidopsis thaliana Assembly Hub</b>: <a href="../../cgi-bin/hgTracks?hubUrl=https://genome.ucsc.edu/goldenPath/help/examples/hubExamples/hubGroupings/groupsExample/hub.txt&genome=araTha1" 
 target="_blank">Assembly Hub</a>.</p></li>
 </ul>
 
 
 <!-- ========== Debugging and Updating Track Hubs ============================== -->
 <a name="Debug"></a>
 <h2>Debugging Track Hubs</strong></h2>
 
 <h3>Not updating? Change udcTimeout</h3>
 <p>
 As part of the track hub mechanism, UCSC caches data from the hub on the local server. The hub
 utility periodically checks the time stamps on the hub files, and downloads them again only if they
 have a time stamp newer than the UCSC one. For performance reasons, UCSC checks the time stamps