6a2563095fd31472040d16eae2b2527945767f07
lrnassar
  Thu May 16 16:46:08 2019 -0700
Some missing anchor closings found by htmlCheck strictTagNestCheck

diff --git src/hg/htdocs/goldenPath/help/api.html src/hg/htdocs/goldenPath/help/api.html
index bfa2a48..188cc5c 100755
--- src/hg/htdocs/goldenPath/help/api.html
+++ src/hg/htdocs/goldenPath/help/api.html
@@ -41,33 +41,33 @@
 </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
 (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>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
+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
 the endpoint functions.  For example:
 <pre>
     curl -L 'https://api.genome.ucsc.edu/list/ucscGenomes'
 </pre>
 </p>
@@ -96,31 +96,31 @@
 assembly</li>
 <li>chrom=&lt;chrN&gt; - specify chromosome name for sequence or track data</li>
 <li>start=&lt;123&gt; - specify start coordinate (0 relative) for data from track or sequence
 retrieval (start and end required together). See also: <a
  href='http://genome.ucsc.edu/blog/the-ucsc-genome-browser-coordinate-counting-systems/'
 target=_blank>UCSC browser coordinate counting systems</a></li>
 <li>end=&lt;456&gt; - specify end coordinate (1 relative) for data from track or sequence
 retrieval (start and end required together). See also: <a
  href='http://genome.ucsc.edu/blog/the-ucsc-genome-browser-coordinate-counting-systems/'
 target=_blank>UCSC browser coordinate counting systems</a></li>
 <li>maxItemsOutput=1000 - limit number of items to output, default: 1,000, maximum limit:
 1,000,000 (use <em>-1</em> to get maximum output)</li>
 <li>trackLeavesOnly=1 - on <em>/list/tracks</em> function, only show tracks, do not show
 composite container information</li>
 <li>jsonOutputArrays=1 - on <em>/getData/track</em> function, JSON format is array type
-for each item of data, instead of the default object type
+for each item of data, instead of the default object type</li>
 </ul>
 </p>
 <p>
 The parameters are added to the endpoint URL beginning with a
 question mark <b>?</b>, and multiple parameters are separated with
 the semi-colon <b>;</b>.  For example:
 <pre>
 https://api.genome.ucsc.edu/getData/sequence?genome=hg38;chrom=chrM
 </pre>
 </p>
 
 <!-- ========== Required and optional parameters  ======================= -->
 <a id="Parameter_use"></a>
 <h2>Required and optional parameters</h2>
 <p>