5d0ada09248607057deba841ace59fd4d1f766ec
jnavarr5
  Fri Jun 26 12:49:54 2026 -0700
Use e.g. for font examples and make configure page's Font menu wording consistent in the mirror manual, refs #37698

diff --git src/product/mirrorManual.txt src/product/mirrorManual.txt
index 434d0da9311..af5f6d71a40 100644
--- src/product/mirrorManual.txt
+++ src/product/mirrorManual.txt
@@ -1606,68 +1606,68 @@
     28bb40d1700909b2509e2125a1963e2c  n019044l.pfb
     adf4d5565bec1170f0a5810c6984ff55  n019063l.pfb
     57e1a49c39a546c2883375df12111816  n019064l.pfb
     84e347c88eff2e77ed40b020b457bafe  n021003l.pfb
     8721c1175d907d7d484bdaa91d4533ad  n021004l.pfb
     eef0367afaa10b929e528c40c980b941  n021023l.pfb
     7af41ff3536fadcdc27eb9e5cc1c32d3  n021024l.pfb
     db95b702b81c12df1f91d15c8a6c3191  n022003l.pfb
     e97c9af68414fabe157af711b7691df7  n022004l.pfb
     f13fb8e581426a1ffa5fc12b10ad0f34  n022023l.pfb
     f3cd9244150f086434b62d5c5bb559b0  n022024l.pfb
     30aef717b7c68a6b6b7760b764fbd01c  z003034l.pfb
 
 # Adding a new font to the Genome Browser display
 
-The fonts offered in the hgTracks "configure" page Font menu are defined in a
+The fonts offered in the hgTracks configure page's Font menu are defined in a
 table in the source code: the `freeTypeFonts[]` array in
 `src/hg/hgTracks/config.c`
 ([view on GitHub](https://raw.githubusercontent.com/ucscGenomeBrowser/kent/refs/heads/master/src/hg/hgTracks/config.c)).
 Adding a font is therefore a source code change, and you will need to rebuild the
 CGIs afterward (see the [Building the kent source tree](#building-the-kent-source-tree)
 section below).
 
 Once you have a font file in hand, adding it takes just two steps:
 
 1.  Put the font file where the rendering engine can find it. At run time the
     file is looked up under the directory given by the `freeTypeDir` setting in
     hg.conf, which defaults to `../htdocs/urw-fonts`. That path is relative to the
     CGI working directory, so it resolves to the shared `htdocs/urw-fonts`
     directory even when you run from a per-user sandbox; you do not need a copy
     under your own htdocs. Both Type1 (`.pfb`) and TrueType (`.ttf`) font files
     are supported.
 
 2.  Add a row to the `freeTypeFonts[]` table in `src/hg/hgTracks/config.c`,
     giving the name to display and the font file name, for example:
 
         {"Lexend",      "Lexend-Regular.ttf"},
         {"Lexend-Bold", "Lexend-Bold.ttf"},
 
-    The name is what appears in the configure-page Font menu. The configure page
+    The name is what appears in the configure page's Font menu. The configure page
     splits the name on the first "-" into a face and a style: the part before the
     "-" is the face shown in the Font menu, and the part after is an entry in the
     Style menu. A plain weight is just the face name (Lexend); a variant is
     written as Face-Style (Lexend-Bold). Group a face's variants on consecutive
     rows so the Style menu lists them together.
 
 A couple of things to watch out for:
 
-- Avoid variable fonts (for example InterVariable.ttf). The engine opens face
+- Avoid variable fonts (e.g. InterVariable.ttf). The engine opens face
   index 0 with no named instance selected, so a variable font renders only its
   default master, which is usually not the weight you expected. The symptom is
   that the new option appears in the menu but a different font is drawn. Use a
-  static, single-weight file instead (for example Inter-Regular.ttf).
+  static, single-weight file instead (e.g. Inter-Regular.ttf).
 
 - The menu name must match the table exactly, including the face/style split
   described above. If a selected name matches no row in the table, the browser
   silently falls back to the old bitmap font engine.
 
 # Building the kent source tree.
 
 In some cases, you may have to modify the source code itself. In these cases, you would need
 to build all the tools and CGI programs from the source code on your machine.
 
 There are scripts available in the git repo src/product/scripts/ directory 
 that can run all of these steps for you with the script: scripts/kentSrcUpdate.sh
 See the instructions in scripts/README
 
 If you have the kent git repository cloned: