Updated documentation for #110. Updated CHANGES.

* Fixed issue #110: Create a simple command line arguments debugging application.

CHANGES

@@ -1,8 +1,10 @@
 Changes for 0.10.0
 
+* Shellanything now features verbose logging mode and command line arguments debugging tools.
 * Fixed issue #6  : (twice) Right-click on a directory with Windows Explorer in the left panel shows the menus twice.
 * Fixed issue #31 : (twice) Error in logs for CContextMenu::GetCommandString()
 * Fixed issue #109: Implement default and verbose logging.
+* Fixed issue #110: Create a simple command line arguments debugging application.
 * Fixed issue #150: ico icon (that do not specifically force index=0) are not working.
 * Fixed issue #157: Compilation fails on Github Action: `fatal error C1083: Cannot open include file: 'atlbase.h': No such file or directory`.
 * Fixed issue #158: Compilation fails on Github Action: `CPack error : Problem running WiX.`.

UserManual.md

@@ -1819,7 +1819,7 @@ The utility is useful during the [uninstall process](https://github.com/end2endz
 
 There are two applications `arguments.debugger.console.exe` and `arguments.debugger.window.exe`. The first is a console application, the second is a windows application. Both applications will show the individual command line arguments received from [<exec> action](#exec-action).
 
-This tool allows one to properly escape string values to use as command line parameters.
+This tool allows one to validate that he properly escaped string values to use as command line parameters. Test your <exec> actions with _arguments.debugger_ until all your arguments are ready. Then switch your actions to launch your actual programs.
 
 For example, if you execute the following menu action:
 ```xml