--- README
+++ README
@@ -369,10 +369,10 @@
 
 COMPATIBILITY WITH PREVIOUS VERSIONS
 
-Existing .nedit Files
+Existing .desk/nedit Files
 
 As of version 5.1, NEdit employs a built-in upgrade mechanism which will
-automatically detects .nedit files of older versions. In general, NEdit
+automatically detects .desk/nedit files of older versions. In general, NEdit
 will try to convert and insert entries to match the latest version.
 However, in certain cases where the user has customized the default entries,
 NEdit will leave them untouched (except for possible syntactic conversions).
@@ -438,7 +438,7 @@
     
     However, if you used X resources to dynamically change the colors on
     different invocations, you will need to use the new application-level
-    resources instead.  See the .nedit file for details.
+    resources instead.  See the .desk/nedit file for details.
       
     In 5.3, color resources needed to be qualified by "nedit*" in order to
     prevent problems when the deepest color visual was not the default. 
@@ -449,12 +449,12 @@
     The default location and name of NEdit's resource files has been changed.
     The most important change is the fact that they can now be stored in a
     custom directory, defined by the NEDIT_HOME environment variable. If the
-    variable is not set, the directory defaults to ~/.nedit.
+    variable is not set, the directory defaults to ~/.desk/nedit.
     The files have been renamed as follows:
     
-       ~/.nedit        -> $NEDIT_HOME/nedit.rc
-       ~/.neditmacro   -> $NEDIT_HOME/autoload.nm
-       ~/.neditdb      -> $NEDIT_HOME/nedit.history
+       ~/.desk/nedit        -> $NEDIT_HOME/nedit.rc
+       ~/.desk/neditmacro   -> $NEDIT_HOME/autoload.nm
+       ~/.desk/neditdb      -> $NEDIT_HOME/nedit.history
        
     For backward compatibility reasons, NEdit continues to use the old 
     convention when these files are already present. No attempt is made
@@ -522,14 +522,14 @@
 
 * Upgrading from 5.2 to 5.3
 
-  There are no major changes in the format of the .nedit file for version
+  There are no major changes in the format of the .desk/nedit file for version
   5.2. Users that have customized the X Resources syntax highlighting 
   pattern may consider restoring the default patterns, as they resolve
-  a performance issue when editing the .nedit file itself, for instance.
+  a performance issue when editing the .desk/nedit file itself, for instance.
   
 * Upgrading from 5.1 to 5.2
 
-  There are no major changes in the format of the .nedit file for version
+  There are no major changes in the format of the .desk/nedit file for version
   5.2. NEdit will try to insert additional entries for the newly supported
   language modes and syntax highlighting patterns (CSS, Regex, and XML) and
   highlight styles (Pointer, Regex, Warning).
@@ -550,7 +550,7 @@
   substitutions.
 
   NEdit 5.1 employs a built-in upgrade mechanism which will automatically
-  detect pre-5.1 .nedit files and fix regular expressions which appear in
+  detect pre-5.1 .desk/nedit files and fix regular expressions which appear in
   user-defined highlight patterns. The automatic upgrade mechanism, however,
   can not fix regular expression problems within user-defined macros. If you
   have a macro which is failing under NEdit 5.1, you will have to fix it by
@@ -560,7 +560,7 @@
 
   If you are upgrading from a pre-5.0 version of NEdit, there are significant
   changes to the macro language, and you are best off simply editing out the
-  nedit.macroCommands section of your .nedit file, generating a new .nedit
+  nedit.macroCommands section of your .desk/nedit file, generating a new .desk/nedit
   file, and then re-introducing your user-written commands into the new file.
   Most macros written for previous versions will function properly under the
   new macro language. The most common problems with old macros is lack of a