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/trackDb/trackDbLibrary.shtml src/hg/htdocs/goldenPath/help/trackDb/trackDbLibrary.shtml
index 195321c5d1c..56b67403f3c 100644
--- src/hg/htdocs/goldenPath/help/trackDb/trackDbLibrary.shtml
+++ src/hg/htdocs/goldenPath/help/trackDb/trackDbLibrary.shtml
@@ -30,31 +30,31 @@
       this setting is relevant to.
     - Each setting blurb MUST contain a <div class="format"> that gives the exact format of the
       setting, wrapped in <code> tags.
     - The setting blurb should also contain an <B>Example:</B> followed by a preferably real life
       example wrapped in <PRE> tags.  Remeber multi-line <PRE> text will include the indents
       found in this file!
     - Some settings may refer to other settings and your blurb should include a link to the other
       setting, especially if that setting's blurb will appear at some distance in the document.
       Since all settings should have an anchor by the setting name, a "jumpTo" link to
       visibility setting can be accomplished as:
           <A onclick="return jumpTo(this);" HREF="#">visibility</A>
       which is identical to
           <A HREF="#visibility">visibility</A>
     - Any setting or code that is not made into a <A> link should be wrapped with <code> tags.
   - "Type setting blurbs" are the same as other setting blurbs except that there should be a
-     seperate "example blurb" DIV with class of type_example (e.g. <DIV class="bed_example">).
+     separate "example blurb" DIV with class of type_example (e.g. <DIV class="bed_example">).
     This will allow a type definition to be followed by multiple type specific settings then
     be completed by the example that references those settings.
     - These example blurbs should also have a "class=format" DIV but in this case it contains a
       title to the example:  <div class="format"><B>Examples of item base types</B></div>.
     - Exmples should make use of <PRE> tags and preferrably multiple real life examples.
   - Document introductions and section introductions may also be shared by multiple documents
     and therefore may be included here as "intro blurb" DIVs as: <DIV class="bed_intro">.
     - intro DIVs do not contain a class="format" DIV.
   - Use trackDbTestBurbs.html to test blurbs you add or modify.  It runs javascript tests.
   HINT: It is the class={setting} that ties things togther.  If there is a need for multiple
   descriptions of the same setting, then create multiple blurb DIVs with different classes as:
     <DIV class="parent"> and <DIV class="parent_view">.
 
   II) Document HTML PAGES should include this trackDbLibrary.html with server side includes
   and wrapped in <DIV ID="library"> tags.