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/goldenPath/help/bigGenePred.html src/hg/htdocs/goldenPath/help/bigGenePred.html
index 603afa3a5f2..1695e8f97a1 100755
--- src/hg/htdocs/goldenPath/help/bigGenePred.html
+++ src/hg/htdocs/goldenPath/help/bigGenePred.html
@@ -220,67 +220,67 @@
Run the bedToBigBed utility to create the bigGenePred output file (step 4,
above):
bedToBigBed -type=bed12+8 -tab -as=bigGenePred.as bigGenePred.txt hg38.chrom.sizes bigGenePred.bb
In this example, you will convert a GTF file to bigGenePred using command line utilities.
-You will need gtfToGenePred, genePredTobigGenePred,
+You will need gtfToGenePred, genePredToBigGenePred,
and bedToBigBed. If you would like to convert a GFF file to bigGenePred, you will use
gff3ToGenePred in place of the gtfToGenePred. You can download utilities from the
utilities directory.
wget command. Skip this step if you already have a GTF
or GFF file.
wget http://genome.ucsc.edu/goldenPath/help/examples/bigGenePredExample4.gtfgtfToGenePred command.
gtfToGenePred -genePredExt bigGenePredExample4.gtf example4.genePred
If you are converting a GFF file, use the gff3ToGenePred command.
gff3ToGenePred yourFile.gff example4.genePred genePredToBigGenePred example4.genePred bigGenePredEx4.txtwget https://genome.ucsc.edu/goldenPath/help/examples/bigGenePred.as
bedToBigBed -type=bed12+8 -tab -as=bigGenePred.as bigGenePredEx4.txt http://hgdownload.gi.ucsc.edu/goldenPath/hg38/bigZips/hg38.chrom.sizes bigGenePredEx4.bbhttp://genome.ucsc.edu/cgi-bin/hgTracks?db=hg38&position=chr19:44905790-44909388&hgct_customText=track%20type=bigGenePred%20bigDataUrl=http://genome.ucsc.edu/goldenPath/help/examples/bigGenePredEx4.bbYou can also add your data in the custom track management page. This allows you to set position, configuration options, and write a more complete -desciption. If you want to see codons, you can right click, then click configure codon view or +description. If you want to see codons, you can right click, then click configure codon view or set this options using
baseColorDefault=genomicCodons as is done below.
browser position chr19:44905790-44909388
track type=bigGenePred baseColorDefault=genomicCodons name="bigGenePred Example Four" description="Ex4:BigGenePred Made from GTF" visibility=pack bigDataUrl=http://genome.ucsc.edu/goldenPath/help/examples/bigGenePredEx4.bb
Once you are done, you should have a track on the Genome Browser like the one below.
In this example, you will set up a Track Hub that displays bigGenePred data and uses one of the bigGenePred-specific settings to display gene codons. You can see a pre-built version of this hub by clicking this link.
@@ -302,31 +302,31 @@ --hub.txt --genomes.txt --hg38 ----trackDb.txt ----bigGenePred.bb You may also include a hub description page and a track description page, where you will find additional instructions.
If you would like to share your bigGenePred data track with a colleague, learn how to create a URL link to your data by looking at Example #6 on the custom track help page.
Because the bigGenePred files are an extension of bigBed files, which are indexed binary files, it