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/bigBed.html src/hg/htdocs/goldenPath/help/bigBed.html
index e3b907599a8..7d871b80c00 100755
--- src/hg/htdocs/goldenPath/help/bigBed.html
+++ src/hg/htdocs/goldenPath/help/bigBed.html
@@ -263,46 +263,46 @@
-as=bedExample2.as to help correctly interpret all the columns in the data.
This example also demonstrates how to create an extra search index on the name field, and the first of the
extra fields to be used for track item search. The searchIndex setting requires the input BED data to be
case-sensitive sorted (sort -k1,1 -k2,2n), where newer versions of the tool bedToBigBed
(available here) are enhanced to catch
improper input.
bedToBigBed utility (Step 3, above).bedToBigBed utility (Step 2, above).
bedToBigBed -as=bedExample2.as -type=bed9+2 -extraIndex=name,geneSymbol bedExample2.bed hg18.chrom.sizes myBigBed2.bbitemRgb attribute in the track line.
It will look somewhat similar to this (note that you must insert the URL specific to your own
bigBed file):
track type=bigBed name="bigBed Example Three" description="A bigBed File with Color and two Extra Fields" itemRgb="On" bigDataUrl=http://yourWebAddress/myBigBed2.bbbedToBigBed utility with the option
-extraIndex=name, you will be able to search on the "name" field by adding
the line searchIndex name to the stanza about your bigBed in the hub's