a97fc1e7683c45ea203e849da91628d957cefee5
kuhn
  Wed Nov 24 16:07:43 2021 -0800
moved a word to the right place so it makes sense now

diff --git src/hg/htdocs/goldenPath/help/customTrackText.html src/hg/htdocs/goldenPath/help/customTrackText.html
index 5981e97..468bc97 100755
--- src/hg/htdocs/goldenPath/help/customTrackText.html
+++ src/hg/htdocs/goldenPath/help/customTrackText.html
@@ -757,31 +757,31 @@
   believes the user will come back to the Genome Browser expecting the
   changes to still be there. 
   Compare this behavior to the setting <code>incognito=1</code> described below.
   - <a href="../../cgi-bin/hgTracks?db=hg19&ignoreCookie=1" 
   target="_blank">example link</a> to show the default tracks and positions for hg19, 
   in a new, clean session.</li>
   <li>
 
   <code>incognito=1</code> - do not load the user's existing settings saved
   in the internet browser's UCSC Genome Browser cookie and also never save them to the cookie. 
   This means that that link will show the Genome Browser default 
   settings such as track selections, custom
   tracks, and track hubs. Also: Any changes made by the user or other URL arguments 
   will not affect the user's 
   Genome Browser settings. E.g., if you add a track in this new window, and come
-  back to the genome browser later, this track will appear NOT in the new window. This setting
+  back to the genome browser later, this track will NOT appear in the new window. This setting
   is useful if a website wants to link to the Genome Browser, wants to start 
   with a "clean slate" but does not want any changes to affect other Genome
   Browser windows that are open or that the user may open later.
   - <a href="../../cgi-bin/hgTracks?db=hg19&incognito=1" 
   target="_blank">example link</a> to show the default tracks and positions for hg19, 
   in a new, clean session,
   that is completely independent from all other Genome Browser windows that the user 
   has open or will open later.
   Any changes made to this window will not be saved and are lost as soon as the window is closed. 
   Compare this behavior to the setting <code>ignoreCookie=1</code> described above.
   (At the moment,
   there is no visual indicator in such a Genome Browser window that changes are not saved, 
   but we could add one 
   in the future, please contact us if you think this could be useful for you.) 
   This variable is probably