update docs

Documentation/CodeRecoveryInCuis.md

@@ -1,7 +1,7 @@
 # Code Recovery in Cuis
 
-Smalltalk systems store source code in two files, the Sources file (named, for example 'Cuis7.0.sources') and the Changes file (for example, 'Cuis7.1-6539.changes'). The Sources file is not modified after creation, and new and modified code is appended to the Changes file. Both these files are used (for instance) by the Smalltalk Browser, when exploring the source code for the system.
+Smalltalk systems store source code in two files, the Sources file (named, for example 'Cuis7.0.sources') and the Changes file (for example, 'Cuis7.1-6541.changes'). The Sources file is not modified after creation, and new and modified code is appended to the Changes file. Both these files are used (for instance) by the Smalltalk Browser, when exploring the source code for the system.
 
-Cuis saves an additional type of files, UserChanges (named, for example, Cuis7.1-6539.user.002.changes), in the -UserFiles/UserChanges folder. These files are numbered, and they are created anew each time the Cuis system is started. These files are not used by the system to retrive code, they only exist to aid programmers. They will only include our work, and will conveniently use a different file for each programming session. They are not deleted automatically, and the user is free to delete them when desired.
+Cuis saves an additional type of files, UserChanges (named, for example, Cuis7.1-6541.user.002.changes), in the -UserFiles/UserChanges folder. These files are numbered, and they are created anew each time the Cuis system is started. These files are not used by the system to retrive code, they only exist to aid programmers. They will only include our work, and will conveniently use a different file for each programming session. They are not deleted automatically, and the user is free to delete them when desired.
 
 To recover our code, the [recent changes] button in FileList will open a ChangeList on the selected file. This tool lets you review your work. For this, you can compare the various versions of methods in the file with their in-memory counterpart, filter them according to several criteria, load them as desired, etc.

RunCuisOnLinux.sh

@@ -41,7 +41,7 @@ else # all-in-one bundle
 
  BINDIR="${ROOT}/CuisVM.app/Contents/Linux-${CPU}/"
  IMAGEDIR="${ROOT}/CuisImage/"
- IMAGE="${IMAGEDIR}Cuis7.1-6539.image"
+ IMAGE="${IMAGEDIR}Cuis7.1-6541.image"
 fi
 
 VM="${BINDIR}${APP}"

RunCuisOnWindows.bat

@@ -1 +1 @@
-START /B .\CuisVM.app\Contents\Windows-x86_64\Squeak.exe "CuisImage\Cuis7.1-6539.image" -u
+START /B .\CuisVM.app\Contents\Windows-x86_64\Squeak.exe "CuisImage\Cuis7.1-6541.image" -u