37a8930e3a492001f14a73f8a676cc50fbfcd16d
jnavarr5
  Tue Jul 16 17:21:18 2024 -0700
Adding Gerardo's suggestions from the code review, refs #34117

diff --git src/hg/htdocs/goldenPath/newsarch.html src/hg/htdocs/goldenPath/newsarch.html
index 0baf3a5..62b4acc 100755
--- src/hg/htdocs/goldenPath/newsarch.html
+++ src/hg/htdocs/goldenPath/newsarch.html
@@ -59,53 +59,54 @@
 For the full list of our daily code changes head to <a
 href="https://github.com/ucscGenomeBrowser/kent/commits/master"
 target=_blank>our GitHub page</a>.</p>
 
 <!-- ============= 2024 archived news ============= -->
 <a name="2024"></a>
 
 <a name="071224"></a>
 <h2>Jul. 12, 2024 &nbsp;&nbsp; First update to hg19's UCSC Genes track since 2013</h2>
 <p>
 The UCSC Genome Browser is getting ready to update hg19's UCSC Genes dataset for the first time
 since 2013. In this update, the UCSC Genes track will now use GENCODE v45 gene models lifted to hg19
 and replace the old UCSC transcript IDs with the official GENCODE IDs.
 </p>
 <p>
-The anticipated released
-date for this update is July 31, 2024.</p>
+The anticipated release date for this update is July 31, 2024.</p>
 
 <p>
 As an example of what to expect, here are some GENCODE IDs that will replace the UCSC IDs in the
 update:</p>
 
 <pre>
 oldId      newId
 uc003qfo.3 ENST00000341911.10_8
 uc003jsk.2 ENST00000462279.5_3
 uc003umk.1 ENST00000318238.9_6
 uc003gzi.3 ENST00000682860.1_2
 uc011dpu.2 ENST00000375023.3_6
 uc021raj.2 ENST00000258149.11_6
 uc002fxp.3 ENST00000341657.9_12
 uc010xhp.1 ENST00000429344.7_6
 uc003zze.3 ENST00000242285.11_9</pre>
 
 <p>
-For each transcript ID, the _# portion is part of the official hg19 backmap ID, so they are not
-confused with the gene/transcript they are derived from in hg38. Between hg38 and hg19, the two IDs
-are not always in the same sequence and may not be a one-to-one mapping.
+For each transcript ID, the _# portion is part of the
+<a href="https://github.com/diekhans/gencode-backmap?tab=readme-ov-file#identification"
+target="_blank">official hg19 backmap ID</a>, so they are not confused with the gene/transcript they
+are derived from in hg38. Between hg38 and hg19, the two IDs are not always in the same sequence and
+may not be a one-to-one mapping.
 </p>
 <p>
 With this update, we will also be freezing the previous 2013 knownGene release in a separate
 archive track. Once new GENCODE versions are available, the previous track will then be added to the
 archive for future reproducibility. More information about the knownGene archive will be available
 once the update is released.</p>
 
 <a name="060724"></a>
 <h2>June 7, 2024 &nbsp;&nbsp; New GENCODE gene tracks: Human V46 (hg19/hg38) - Mouse M35
 (mm39)</h2>
 <p>
 We are pleased to announce new GENCODE Gene annotation tracks, which correspond
 to <a href="https://www.ensembl.info/2024/05/13/ensembl-112-has-been-released/"
 target="_blank">Ensembl 112</a>, for three assemblies: <a target="_blank"
 href="../../cgi-bin/hgTrackUi?db=hg19&c=chr21&g=wgEncodeGencodeV46lift37">hg19/GRCh37</a>,