--- lynx_help/Lynx_users_guide.html.orig	Sun Apr 23 05:16:38 2000
+++ lynx_help/Lynx_users_guide.html	Sun Aug 27 23:50:07 2000
@@ -480,7 +480,7 @@
 
 The Lynx <em>Options Menu</em> may be accessed by pressing the '<em>o</em>'
 key. It allows you to change options at runtime, if you need to.
-Most changes are read from &amp; saved to your .lynxrc file; those which are not
+Most changes are read from &amp; saved to your .desk/lynxrc file; those which are not
 are marked (!) in the form-based menu (as below). Many other options
 are stored in the <A HREF="#lynx.cfg">lynx.cfg</A> file.
 
@@ -598,7 +598,7 @@
 
 <p>When you are done changing options use the '<em>r</em>' command to
 return to Lynx or the '<em>&gt;</em>' command to save the options to a
-<em>.lynxrc</em> file and return to Lynx.
+<em>.desk/lynxrc</em> file and return to Lynx.
 
 <p>The following table describes the options available on the
 <em>Options Menu</em>:
@@ -750,7 +750,7 @@
             If set to OFF or NEVER, color mode will be turned off.<BR>
             ALWAYS and
             NEVER are not offered in anonymous accounts.  If saved to a
-            <em>.lynxrc</em> file in non-anonymous accounts, ALWAYS will
+            <em>.desk/lynxrc</em> file in non-anonymous accounts, ALWAYS will
             cause Lynx to set color mode on at startup if supported.
             If Lynx is built with the slang library, this is equivalent to
             having included the <em>-color</em> command line switch or having the
@@ -766,7 +766,7 @@
             slang library is used) can be overridden with the <em>-color</em>
             switch.<BR>
             If the setting is OFF or ON
-            when the current options are saved to a <em>.lynxrc</em> file,
+            when the current options are saved to a <em>.desk/lynxrc</em> file,
             the default startup behavior is retained, such that color mode
             will be turned on at startup only if the terminal info indicates
             that you have a color-capable terminal, or (when the
@@ -1688,14 +1688,14 @@
 </pre><p>
 You can also use the <em>Options Menu</em>, as outlined below:
 <pre>
-     key  lynx.cfg       FM KM .lynxrc    variable in source
+     key  lynx.cfg       FM KM .desk/lynxrc    variable in source
 
        *  MAKE_LINKS_     Y  N       N    clickable_images
        [  MAKE_PSEUDO_    Y  N       N    pseudo_inline_alts
           VERBOSE_        Y  Y       Y    verbose_img
 
 FM = Form-based Menu ; KM = Key-based Menu ;
-in  .lynxrc ,  VERBOSE_IMAGES  is called `verbose_images':
+in  .desk/lynxrc ,  VERBOSE_IMAGES  is called `verbose_images':
 the other two cannot be saved between sessions.
 </pre><p>
 In the Form-based Menu, the 3-way `Show images' selection
@@ -2165,7 +2165,7 @@
 If ACCEPT_ALL_COOKIES is set TRUE, and SET_COOKIES is TRUE, Lynx will accept
 all cookies.  Additionally, the cookies that are automatically accepted or
 rejected by Lynx can be further modified with the COOKIE_ACCEPT_DOMAINS and
-COOKIE_REJECT_DOMAINS options in your .lynxrc file, each of which is a
+COOKIE_REJECT_DOMAINS options in your .desk/lynxrc file, each of which is a
 comma-separated list of domains to perform the desired action.  The domain
 listed in these options must be identical to the domain the cookie comes
 from, there is no wildcard matching.  If a domain is specific in both
@@ -2186,7 +2186,7 @@
 href="keystrokes/cookie_help.html">Cookie Jar Page</a>. If Lynx has been
 compiled with the --enable-persistent-cookies flag, then unexpired cookies
 will be stored between sessions in the filename set with the COOKIE_FILE
-option in your .lynxrc.
+option in your .desk/lynxrc.
 
 <p>A common use of cookies by http servers is simply to track the
 documents visited by individual users.  Though this can be useful to the
@@ -2323,9 +2323,9 @@
                        library like ncurses, Lynx relies completely on the terminal
                        description to determine whether color mode is possible, and
                        this flag is not needed and thus unavailable.)
-                       A saved show_color=always setting found in a .lynxrc file at
+                       A saved show_color=always setting found in a .desk/lynxrc file at
                        startup has the same effect.  A saved show_color=always found
-                       in .lynxrc on startup is overridden by this flag.
+                       in .desk/lynxrc on startup is overridden by this flag.
              <dt><code>-cookies</code>
                 <dd>toggles handling of Set-Cookie headers.
              <dt><code>-core</code>
@@ -2417,7 +2417,7 @@
                     within a mailto URL or form ACTION.
              <dt><code>-nocolor</code>
                 <dd>force color mode off, overriding terminal capabilities and any
-               <em>-color</em> flags, <em>COLORTERM</em> variable, and saved .lynxrc settings.
+               <em>-color</em> flags, <em>COLORTERM</em> variable, and saved .desk/lynxrc settings.
              <dt><code>-noexec</code>
                 <dd>disable local program execution. (DEFAULT)
              <dt><code>-nofilereferer</code>
@@ -2591,7 +2591,7 @@
                 <dt>news_post
                         <dd>disallow USENET News posting,
                 <dt>options_save
-                        <dd>disallow saving options in .lynxrc.
+                        <dd>disallow saving options in .desk/lynxrc.
                 <dt>outside_ftp
                         <dd>disallow ftps for people coming from outside your
                             domain.
@@ -2745,7 +2745,7 @@
 
 Lynx has several levels of customization:
 from the Options Menu (accessible on-line,
-and possibly stored in your local .lynxrc file),
+and possibly stored in your local .desk/lynxrc file),
 via command-line switches
 on startup (mainly for batch processing).
 The most important and numerous default settings are stored