198c9b8daecc44fbda6a6494c566c723920f030a lrnassar Wed Mar 11 18:25:21 2026 -0700 Fixing a few hundred clear typos with the help of Claude. Some are less important in code comments, but majority of them are in user-facing places. I manually approved 60%+ of the changes and didn't see any that were an incorrect suggestion, at worst it was potentially uncessesary, like a code comment having cant instead of can't. No RM. diff --git src/hg/htdocs/FAQ/FAQlink.html src/hg/htdocs/FAQ/FAQlink.html index b99806bebe3..4472000aeee 100755 --- src/hg/htdocs/FAQ/FAQlink.html +++ src/hg/htdocs/FAQ/FAQlink.html @@ -147,31 +147,31 @@ <h2>Zooming in or out with a link — HGVS </h2> <h6>How do I zoom out using a link to a HGVS identifier?</h6> <p> To link to a specific HGVS identifier, you can construct a link with the HGVS identifier in the position field instead of coordinates. The default padding is 5bp on either side, but you can always zoom in or out with <code>hgt.out1=submit</code> or <code>hgt.in1=submit</code>. The numbers 1 through 4 zoom in or out corresponding to the buttons above the track window. The following lists the zoom levels of each number, applicable to zooming in or out:</p> <ul> <li id="hgt.out1"><code>hgt.out1=submit</code> zooms out 1.5x</li> <li id="hgt.out2"><code>hgt.out2=submit</code> zooms out 3x</li> <li id="hgt.out3"><code>hgt.out3=submit</code> zooms out 10x</li> <li id="hgt.out4"><code>hgt.out4=submit</code> zooms out 100x</li> </ul> <p> -The following link is an example which leads to the variant NM_00257:c.1208G>T and zooms +The following link is an example which leads to the variant NM_000257:c.1208G>T and zooms out 3x:</p> <p> <code><a href="../cgi-bin/hgTracks?db=hg19&position=NM_000257:c.1208G%3ET&hgt.out2=submit">http://genome.ucsc.edu/cgi-bin/hgTracks?db=hg19&position=NM_000257:c.1208G>T&hgt.out2=submit</a></code></p> <a name="trackViz"></a> <h2>Setting Track Visibility via URL</h2> <h6>How do I create a custom URL to control the visibility of specific tracks?</h6> <p> You can control the visibility of tracks from the URL with the following parameters, each linked by the "&" sign: <ul> <li> <code>guidelines=on/off</code> - activate or deactivate the blue guidelines - <a href="../../cgi-bin/hgTracks?db=hg38&position=chr9%3A133255176-133275214&guidelines=off" @@ -465,31 +465,31 @@ You can also link directly to gene description pages from the URL. Instead of a position search, gene descriptions use the <code>hgg_gene=</code> URL parameter. The following URL connecting to 'hgGene' will open up the Genome Browser description page containing protein function, expression profile, and links to additional information for the gene TP53. </p> <p><code><a href="../cgi-bin/hgGene?db=hg19&hgg_gene=TP53" target="_blank">http://genome.ucsc.edu/cgi-bin/hgGene?db=hg19&hgg_gene=TP53</a> </code></p> <a name="hgsid"></a> <h2>The <em>hgsid</em> parameter</h2> <h6>What is the hgsid parameter and should I include it in Genome Browser links?</h6> <p>The hgsid is a temporary user ID that stores setting and custom track information in the URL. Including it in any shared URLs is a privacy concern, and it should be removed when constructing any links to the Genome Browser. Most significantly, it will change after -you share it. Anyone using it will see that last thing you did, not what you thought +you share it. Anyone using it will see the last thing you did, not what you thought you were sharing. Creating <a href="../goldenPath/help/hgSessionHelp.html#Create">Saved Sessions</a> is the recommended way to share Genome Browser information. </p> <a name="moreInfo"></a> <h2>Additional URL parameters</h2> <h6>Are there any more resources for URL and link parameters?</h6> <p> For more information, please see our <a href=../goldenPath/help/customTrack.html#optParams>section on URL parameters for custom tracks</a>. If you cannot find what you are looking for, please contact our active mailing list by emailing <a href="mailto:genome@soe.ucsc. edu">genome@soe.ucsc.edu</a>. All messages sent to that address are publicly archived. If your question includes sensitive data,