b73f216db33fc474f4ec57ec8638fef390d69cef
jnavarr5
  Tue Nov 5 13:16:41 2024 -0800
Making changes from the code review, refs #34767

diff --git src/hg/htdocs/FAQ/FAQreleases.html src/hg/htdocs/FAQ/FAQreleases.html
index 947044a..9c2b67a 100755
--- src/hg/htdocs/FAQ/FAQreleases.html
+++ src/hg/htdocs/FAQ/FAQreleases.html
@@ -596,57 +596,58 @@
 </p>
 <p>
 If you are using versions dbSNP 153 and above, the data are formatted as bigBed files instead of
 being stored as a MariaDb table. For very large queries, this may cause the Table Browser to timeout
 before the query finishes as dbSNP has grown to include over 700 million variants. If you find that
 your Table Browser query timesout for your list of rsIDs, you can use the
 <code>bigBedNamedItems</code> command-line tool to extract the rsID coordinates directly from the
 bigBed file instead of using the Table Browser.</p>
 <p>More information and examples using the
 <code>bigBedNamedItems</code> utility can be found on the following
 <a href="FAQdownloads.html#snp">FAQ entry</a>. As a reminder, you can run any Kent command-line tool
 without arguments to get the usage statement.
 </p>
 
 <a name="snpExtract"></a>
-<h6>How can I extract a list of rsIDs using chrom:start-end or vise versa?</h6>
+<h6>How can I extract a list of rsIDs using chrom:start-end or vice versa?</h6>
 <p>
 Several utilities for working with bigBed-formatted binary files can be downloaded
 <a href="http://hgdownload.soe.ucsc.edu/downloads.html#utilities_downloads" target="_blank">here</a>.
 Run a utility with no arguments to see a brief description of the utility and its options.
 </p>
 <ul>
   <li><b>bigBedInfo</b> provides summary statistics about a bigBed file including the number of
     items in the file.  With the <b>-as</b> option, the output includes an
     autoSql definition of data columns, useful for interpreting the column values.</li>
   <li><b>bigBedToBed</b> converts the binary bigBed data to tab-separated text.
     Output can be restricted to a particular region by using the -chrom, -start
     and -end options.
   </li>
   <li><b>bigBedNamedItems</b> extracts rows for one or more rs# IDs.</li>
 </ul>
 
 <a name="snpExamples"></a>
 <h6>Examples:</h6>
 <ol>
-  <li>Retrieve all variants in the region chr1:200001-200400</p>
+  <li>Retrieve all variants in the region chr1:200001-200400
   <pre><tt>bigBedToBed http://hgdownload.soe.ucsc.edu/gbdb/hg38/snp/dbSnp155.bb -chrom=chr1 -start=200000 -end=200400 stdout</tt></pre>
   </li>
   <li>Retrieve variant rs6657048
   <pre><tt>bigBedNamedItems dbSnp155.bb rs6657048 stdout</tt></pre>
   </li>
-  <li>Retrieve all variants with rs# IDs in file myIds.txt</p>
+  <li>Retrieve all variants with rs# IDs in a file (myIds.txt)
+      and output to another file (dbSnp155.myIds.bed)
   <pre><tt>bigBedNamedItems -nameFile dbSnp155.bb myIds.txt dbSnp155.myIds.bed</tt></pre>
   </li>
 </ol>
 
 <a name="release9"></a>
 <h2>Missing annotation tracks</h2>
 <h6>Why is my favorite annotation track missing from your latest release?</h6>
 <p> 
 The initial release of a new genome assembly typically contains a small subset of core annotation 
 tracks. New tracks are added as they are generated. In many cases, our annotation tracks are 
 contributed by scientists not affiliated with UCSC who must first obtain the sequence, repeatmasked 
 data, etc. before they can produce their tracks. If you have need of an annotation that has not 
 appeared on an assembly within a month or so of its release, feel free to send an inquiry to 
 <a href="mailto:&#103;&#101;&#110;&#111;&#109;e&#64;&#115;&#111;&#101;.&#117;&#99;sc.e&#100;&#117;">&#103;&#101;&#110;&#111;&#109;e&#64;&#115;&#111;&#101;.&#117;&#99;sc.e&#100;&#117;</a>.
 <!-- above address is genome at soe.ucsc.edu -->