6e67ef8295bba3ef3ab3cb5fcff3761328c47109
lrnassar
  Tue May 21 15:56:30 2019 -0700
Making small changes in response to CR

diff --git src/hg/htdocs/goldenPath/help/api.html src/hg/htdocs/goldenPath/help/api.html
index d045623..5dfafdd 100755
--- src/hg/htdocs/goldenPath/help/api.html
+++ src/hg/htdocs/goldenPath/help/api.html
@@ -37,32 +37,32 @@
 This access url: <b>https://api.genome.ucsc.edu/</b> is used to access
 the endpoint functions.  For example:
 <pre>
     wget -O- 'https://api.genome.ucsc.edu/list/publicHubs'
 </pre>
 </p>
 
 <!-- ========== What type of data can be accessed ? ===================== -->
 <a id="Return"></a>
 <h2>What type of data can be accessed ?</h2>
 <p>
 The following data sets can be accessed at this time:
 <ul>
 <li>List of available public hubs</li>
 <li>List of available UCSC Genome Browser genome assemblies</li>
-<li>List genomes from a specified assembly or track hub</li>
-<li>List available data tracks from a specified hub or UCSC Genome Browser genome assembly
+<li>List of genomes from a specified assembly or track hub</li>
+<li>List of available data tracks from a specified hub or UCSC Genome Browser genome assembly
 (see also: <a
  href='trackDb/trackDbHub.html' target=_blank>track definition help</a>)</li>
 <li>List of chromosomes contained in an assembly hub or UCSC Genome Browser genome assembly</li>
 <li>List of chromosomes contained in a specific track of an assembly or track hub, or UCSC Genome
 Browser genome assembly</li>
 <li>Return DNA sequence from an assembly hub 2bit file, or UCSC Genome Browser assembly</li>
 <li>Return track data from a specified assembly or track hub, or UCSC Genome Browser assembly</li>
 </ul>
 </p>
 
 <!-- ========== Endpoint functions ======================= -->
 <a id="Endpoint"></a>
 <h2>Endpoint functions to return data</h2>
 <p>
 The url <b>https://api.genome.ucsc.edu/</b> is used to access
@@ -292,31 +292,31 @@
 
 <h3>Hide track container information with trackLeavesOnly parameter</h3>
 
 <p>
 When using the <b>/list/tracks</b> function to see the available tracks in an assembly, it can 
 be useful to return all tracks in the same hierarchical level. By default, composite and 
 supertracks will have the subtracks nested below, however, the <b>trackLeavesOnly=1</b> parameter
 can be passed to hide the container information and display all tracks and subtracks at the
 same level.</p>
 
 <p>
 In the following example, the first link does not include the <b>trackLeavesOnly</b> parameter. The 
 output can be compared to the second link to see the difference, which can be observed in the 
 conservation track. In the first link, the <i>multiz20way</i> track is nested within the 
 <i>cons20way</i> track. In the second link, however, the <i>multiz20way</i> subtrack is seen at 
-an equivelant level with all other tracks, and the container, <i>cons20way</i>, is not 
+an equivalent level with all other tracks, and the container, <i>cons20way</i>, is not 
 present in the list.</p>
 
 <p>
 <a href='https://api.genome.ucsc.edu/list/tracks?genome=rn6'
 target=_blank>Request available tracks in the rn6 genome</a> -
 <br><b>api.genome.ucsc.edu/list/tracks?genome=rn6</b></p>
 
 <p>
 <a href='https://api.genome.ucsc.edu/list/tracks?genome=rn6;trackLeavesOnly=1'
 target=_blank>Request available tracks in the rn6 genome, hiding container information</a> -
 <br><b>api.genome.ucsc.edu/list/tracks?genome=rn6;trackLeavesOnly=1</b></p>
 
 <h3>Requesting track data with over one million (1M) items in output</h3>
 
 <p>