diff -up ./debug/org.eclipse.cdt.debug.application/scripts/README.fix ./debug/org.eclipse.cdt.debug.application/scripts/README
--- ./debug/org.eclipse.cdt.debug.application/scripts/README.fix	2014-06-09 16:54:24.072430881 -0400
+++ ./debug/org.eclipse.cdt.debug.application/scripts/README	2014-06-09 17:05:38.052725022 -0400
@@ -3,23 +3,16 @@ is needed of the CDT plug-ins to debug a
 Editing is allowed, but you will need to rebuild outside the Stand-alone Debugger for
 those changes to manifest in your debugging session.
 
-To install the Stand-alone debugger locally in your $HOME directory, run the install.sh
-script directly from the scripts sub-directory of the plugins directory in your
-Eclipse installation:
-
-  sh ./install.sh
-
-The script uses relative directories so you cannot run the script from any other working directory.
-
-The install script will create a cdtdebugger directory in your $HOME directory.  This
-directory will contain a config.ini file, a dev.properties file, and a cdtdebug.sh script.
-The cdtdebug.sh script will start the debugger from the command-line.  It does not
-have relative directories so you can move it around as you like.
+To run the Stand-alone debugger, use the /usr/bin/cdtdebug script.  The first time
+the script is run, it will create a cdtdebugger sub-directory in your $HOME directory.  This
+directory will contain a config.ini file and a dev.properties file.
+
+The /usr/bin/cdtdebug script will start the debugger from the command-line.
 
 The script takes a few options which are mentioned below:
 
 -data : workspace to use for your Eclipse session if you do not want the default
-        $HOME/workspace-gdbstandalone
+        $HOME/workspace-cdtdebug
         
 -consoleLog : if you want error messages reported directly to the command console
 
@@ -42,12 +35,12 @@ If no -a or -e option is specified, the
 debugging.  Otherwise, if this is the first time, a dialog will be presented to enter
 an executable, build log, and program arguments.
 
-  e.g. sh ~/cdtdebugger/cdtdebug.sh -b ~/build.log ~/myproject/bin/a.out arg1 arg2
+  e.g. cdtdebug -b ~/build.log ~/myproject/bin/a.out arg1 arg2
 
-The cdtdebug.sh script that is found in the plug-in can also be run directly, but only
+The cdtdebug script that is found in this plug-in can also be run directly, but only
 in this scripts directory as it uses relative directories to find the Eclipse instance and
 the plugins directory.
 
   e.g. sh ./cdtdebug.sh -b ~/build.log ~/myproject/bin/a.out arg1 arg2
 
-                     
\ No newline at end of file
+