cbe3d85f5bb91ffbd522c69ec3477c47af157320
lrnassar
  Thu Jun 19 10:20:05 2025 -0700
Needed one more line break.

diff --git src/hg/makeDb/trackDb/human/revel.html src/hg/makeDb/trackDb/human/revel.html
index d3d59f405c9..6a9c51d528c 100644
--- src/hg/makeDb/trackDb/human/revel.html
+++ src/hg/makeDb/trackDb/human/revel.html
@@ -108,30 +108,31 @@
       <td style="color: rgb(255,0,0);">Pathogenic supporting</td>
     </tr>
     <tr>
       <td>0.643 - 0.291</td>
       <td style="color: rgb(192,192,192);">Neutral</td>
     </tr>
     <tr>
       <td>&le; 0.290</td>
       <td style="color: rgb(80,166,230);">Benign supporting</td>
     </tr>
   </tbody>
 </table>
 
 <p>
 More details on these scoring ranges can be found in Bergquist et al. Genet Med 2025, Table 2:<br>
+<br>
 <img src="../images/bergquist25.png" alt="Table 2 from Bergquist Genet Med 2025">
 </p>
 
 <p>For hg38, note that the data were converted from the hg19 data using the UCSC
 liftOver program, by the REVEL authors. This can lead to missing values or
 duplicated values. When a hg38 position is annotated with two scores due to the
 lifting, the authors removed all the scores for this position. They did the same when
 the reference nucleotide has changed from hg19 to hg38.  Also, on hg38, the track has
 the &quot;lifted&quot; icon to indicate
 this <img class="gbsInlineImg" src="../images/19.jpg">. You can double-check if a nucleotide
 position is possibly affected by the lifting procedure by activating the track
 &quot;Hg19 Mapping&quot; under &quot;Mapping and Sequencing&quot;.
 </p>
 
 <h2>Data access</h2>