08afd09bf225ea50691998f829926e9d71d55b49
lrnassar
  Wed Mar 11 19:21:42 2026 -0700
Fixing small grammatical and consistency errors with the heatmap page and trackDb entry. Also some bigger fixes like a broken anchor. Refs #36176

diff --git src/hg/htdocs/goldenPath/help/trackDb/trackDbLibrary.shtml src/hg/htdocs/goldenPath/help/trackDb/trackDbLibrary.shtml
index 56b67403f3c..b62088c1e58 100644
--- src/hg/htdocs/goldenPath/help/trackDb/trackDbLibrary.shtml
+++ src/hg/htdocs/goldenPath/help/trackDb/trackDbLibrary.shtml
@@ -6677,31 +6677,31 @@
             parent myViewSignals on
             shortLabel Sig Two
             longLabel Sig Two Long
             bigDataUrl https://hgdownload.gi.ucsc.edu/gbdb/hg38/bbi/wgEncodeRegDnase/wgEncodeRegDnaseUwK562Signal.bw
             subGroups cell=A1GM12 view=SIG
     </pre>
     <p>
     Similar to the example above, except this example shows a composite track containing two views, one with
     bigBeds and one with bigBeds, all inside of a superTrack.</p>
 </DIV>
 
 <!-- - - - - - - - FACETED COMPOSITE settings - - - - - - - -->
 <DIV class="faceted_composite_intro">
 <H3>Faceted Composite Tracks</H3>
 <p>Some data sets fit easily into the view- and subgroup-based organization scheme.  Other datasets, however,
-may consist of too many tracks to easily coherce into that structure, and may also benefit from mixing
+may consist of too many tracks to easily coerce into that structure, and may also benefit from mixing
 datasets with different underlying types (e.g. signals and peaks) together under the same heading.
 For those situations, a "faceted composite" track may be appropriate.</p>
 <p>A faceted composite track is a composite with no views or subgroups to organize the subtracks.  Instead,
 the subtracks are organized by a list of facets drawn from an accompanying tsv (tab-separated values) file.
 These facets can be combined with an optional <code>dataTypes</code> setting to control which subtracks are
 visible.  When <code>dataTypes</code> is absent, each row in the list represents an individual track
 that can be turned on or off.  When <code>dataTypes</code> is present, the rows instead represent sample
 IDs that are combined with the active dataTypes to control which tracks are turned on.</p>
 <p>Important: for this setting to be used, the subtrack names must be arranged carefully.
 Subtrack names in a faceted composite are derived from the parent track name and the metadata
 instead of being assigned freely.  The exact format depends on whether the <code>dataTypes</code>
 setting is present.</p>
 <p>Without <code>dataTypes</code>:
 <br>
 <pre>    &lt;parentTrackName&gt;_&lt;primaryKeyValue&gt;</pre>