560b2736eecac74f65a714e84e7375ce8018730a
dschmelt
  Fri Nov 15 16:44:42 2019 -0800
Slight change to wording to reflect that useOneFile doesn't require ordered stanzas No Rm

diff --git src/hg/htdocs/goldenPath/help/hgTracksHelp.html src/hg/htdocs/goldenPath/help/hgTracksHelp.html
index 0b3f5b2..30ba6a0 100755
--- src/hg/htdocs/goldenPath/help/hgTracksHelp.html
+++ src/hg/htdocs/goldenPath/help/hgTracksHelp.html
@@ -1395,33 +1395,32 @@
 <h2>Do Track Hubs require directories for the data?</h2>
 <p>
 Historically, a hub needed a set of text files to specify properties for a track hub and each of
 the data tracks within the hub. The track hub settings were stored in a three file structure:
 hub.txt, genomes.txt, and trackDb.txt</p>
 <pre>
 myHub/          - directory containing track hub files
 * hub.txt       - a short description of hub properties
 * genomes.txt   - list of genome assemblies included in the hub data
 * hg19/         - directory of data for the hg19 (GRCh37) human assembly
 ** trackDb.txt  - display properties for tracks in this directory
 </pre>
 <p>
 Now, there is a trackDb option to have your entire track hub inside of one file,
 <code>useOneFile on</code>. Adding the <code>useOneFile on</code> line to the hub.txt section of the
-file allows the contents of all three files to be referenced inside of one file. The order of the
-file contents is essential and needs to be in the following order to work: hub.txt, genomes.txt,
-then trackDb.txt.
+file allows the contents of all three files to be referenced inside of one file. We recommend the 
+single hub.txt file's contents be in the following order: hub.txt, genomes.txt, then trackDb.txt.
 </p>
 <pre>
 hub myExampleHub
 shortLabel Example Hub
 longLabel Example Hub for useOneFile option
 useOneFile on
 email genome-www@soe.ucsc.edu
 
 genome hg19
 
 track vcfExample
 shortLabel VCF example
 longLabel VCF: 1000 Genomes phase 1 interim SNVs
 visibility pack
 type vcfTabix