d5932e4051a4885f0036831cdfc5fbf1eb08a499
lrnassar
  Tue Oct 10 17:16:27 2023 -0700
Fixing broken blog links, refs #32439

diff --git src/hg/htdocs/FAQ/FAQtracks.html src/hg/htdocs/FAQ/FAQtracks.html
index 31988d8..2849b7a 100755
--- src/hg/htdocs/FAQ/FAQtracks.html
+++ src/hg/htdocs/FAQ/FAQtracks.html
@@ -138,31 +138,31 @@
 database file, and consequently is based on the internal representation.</p> 
 <p> 
 We use this particular internal representation because it simplifies coordinate arithmetic, i.e. it 
 eliminates the need to add or subtract 1 at every step. If you use a database dump file but would 
 prefer to see the one-based start coordinates, you will always need to add 1 to each start 
 coordinate.</p> 
 <p> 
 If you submit data to the browser in position format (chr#:##-##), the browser assumes this 
 information is 1-based. If you submit data in any other format (BED (chr# ## ##) or otherwise), the 
 browser will assume it is 0-based. You can see this both in our liftOver utility and in our search 
 bar, by entering the same numbers in position or BED format and observing the results. Similarly, 
 any data returned by the browser in position format is 1-based, while data returned in BED format 
 is 0-based.</p>  
 <p> 
 For a detailed explanation, please see our blog entry for the 
-<a href="http://genome.ucsc.edu/blog/the-ucsc-genome-browser-coordinate-counting-systems/"
+<a href="https://genome-blog.gi.ucsc.edu/blog/the-ucsc-genome-browser-coordinate-counting-systems/"
 target="_blank">UCSC Genome Browser coordinate counting systems</a>.</p>
 
 <a name="tracks2"></a>
 <h2>mRNA-associated results</h2>
 <h6>Sometimes when I type in the name of a gene -- e.g. DAO (D aminoacid oxidase) -- the Genome 
 Browser returns a list that includes the gene entry on the assembly, but also contains links to 
 several other genes and aligned mRNAs. What is the relationship between my gene of interest and 
 these results?</h6>
 <p>
 The gene search results are obtained from scanning the RefSeq and Known Genes tracks, which are 
 typically based on non-redundant relatively high quality mRNAs. A small fraction of RefSeqs are 
 based on DNA level annotations. In most cases, there is a HUGO Gene Nomenclature Committee symbol or
 other biological name associated with the gene. In the case of the RefSeq track, the association 
 between these names and the accession is maintained at NCBI and is also present in the refLink 
 table.</p> 
@@ -415,19 +415,19 @@
 BLAT-generated RefSeq track methods are described in 
 corresponding track description pages (e.g., <a href="../cgi-bin/hgTrackUi?db=hg19&g=refGene" 
 target="_blank">RefSeq track description for hg19)</a>.</p>
 <p>
 In 2017, NCBI RefSeq coordinates for hg38 were used for generating non-discrepant RefSeq tracks 
 in the UCSC Genome Browser. This new 
 <a href="../cgi-bin/hgTrackUi?db=hg38&g=refSeqComposite" 
 target="_blank">NCBI RefSeq track</a> in the UCSC Genome Browser displays identical RNA 
 coordinates to annotations in the <a href="https://www.ncbi.nlm.nih.gov/refseq/" 
 target="_blank">NCBI Reference Sequence Database</a>. Please note that when annotations do map 
 to multiple loci, the NCBI RefSeq track displays unique identifiers for each locus, while the
 UCSC RefSeq track retains the same identifier.</p> 
 <p>
 For more information and future plans to integrate coordinate-generated NCBI RefSeq tracks for 
 other assemblies, please see the 
-<a href="http://genome.ucsc.edu/blog/the-new-ncbi-refseq-tracks-and-you/" 
+<a href="https://genome-blog.gi.ucsc.edu/blog/the-new-ncbi-refseq-tracks-and-you/" 
 target="_blank">NCBI RefSeq track blog post</a>.</p>
 
 <!--#include virtual="$ROOT/inc/gbPageEnd.html" -->