---------------------------------------------------------------


hg16.trackDb.html : Differences exist between hgwbeta and hgw2 

(RR fields taken from public MySql server, not individual machine)

3180,3192c3180,3182
< cytoBand | <p>
< cytoBand | Chromosome band information was <a target="_blank"
< cytoBand | href="https://ftp.ncbi.nlm.nih.gov/pub/gdp/">downloaded from NCBI</a>
< cytoBand | using the ideogram.gz file for the respective assembly. These data were then 
< cytoBand | transformed into our visualization format. See our <a target="_blank"
< cytoBand | href="https://github.com/ucscGenomeBrowser/kent/tree/master/src/hg/makeDb/doc">
< cytoBand | assembly creation documentation</a> for the organism of interest
< cytoBand | to see the specific steps taken to transform these data.
< cytoBand | Band lengths are typically estimated based on FISH or other
< cytoBand | molecular markers interpreted via microscopy.</p>
< cytoBand | <p>
< cytoBand | For some of our older assemblies, greater than 10 years old, the tracks were
< cytoBand | created as detailed below and in Furey and Haussler, 2003.</p>
---
> cytoBand | <P>
> cytoBand | A full description of the method by which the chromosome band locations are 
> cytoBand | estimated can be found in Furey and Haussler, 2003.

11985c11975
< mgcFullMrna | This track show alignments of human mRNAs from the
---
> mgcFullMrna | This track shows alignments of human mRNAs from the

11990c11980
< mgcFullMrna | clones for human, mouse, rat, xenopus, and zerbrafish genes.
---
> mgcFullMrna | clones for human, mouse, and rat genes.

14310,14322d14299
< rmsk | 
< rmsk | <p>
< rmsk | When analyzing the data tables of this track, keep in mind that Repbase is not the same 
< rmsk | as the Repeatmasker sequence database and that the repeat names in the
< rmsk | Repeatmasker output are not the same as the sequence names in the Repeatmasker
< rmsk | database.  Concretely, you can find a name such as "L1PA4" in the Repeatmasker
< rmsk | output and this track, but there is not necessarily a single sequence "L1PA4"
< rmsk | in the Repeatmasker database. This is because Repeatmasker creates annotations
< rmsk | by joining matches to partial pieces of the database together so there is no
< rmsk | 1:1 relationship between its sequence database and the annotations. To learn
< rmsk | more, you can read the Repeatmasker paper, its source code or reach out to the
< rmsk | Repeatmasker authors, your local expert on transposable elements or us.
< rmsk | </p>