Update CHANGELOG

Author: znorman-harris

CHANGELOG.md

@@ -36,7 +36,7 @@ New-and improved IDL Notebook user experience!
 
 - The paths for notebook cells have been cleaned up and are now easy to read (before they had IDs in the names of the paths)
 
-- Notebook cells now offer implied print! For main level programs (i.e. cells by default), we detect and automatically print variables, outputs from function calls, and expressions like "2 + 42".
+- Notebook cells now offer implied print! For main level programs (i.e. cells by default), we detect and automatically print variables, outputs from function calls, and expressions like "2 + 42". You can see some examples of this in our sample IDL Notebook included with the extension.
 
 - Variables that will be printed have a special semantic token highlighting applied to them to make it clear it is not being interpreted as a procedure. This depends on your VSCode theme, but should either look like other variables or stands out compared to procedure calls.
 
@@ -53,13 +53,14 @@ Fixed an edge case when reporting that a variable cannot be indexed with the `!n
 Type detection now properly handles the following cases:
 
 - Any statement using `&&` or `||` will return boolean type
+
 - Any statement using a logical operator should return the correct type (i.e. `eq`, `ne`, `le`). For example: `[1,2,3] eq 5` should give a type of `Array<Boolean>`. This supports lists, hashes, orderedhashes, and dictionaries.
 
-These type changes help catch some cases that were incorrectly reporting errors for extension users.
+These type changes help fix scenarios where we were incorrectly reporting errors for extension users.
 
-The extension now automatically detects when you have code that is "floating" which needs to be assigned to a value (or have a value assigned to it).
+The extension now automatically detects when you have code that is "standalone" which needs to be assigned to a value (or have a value assigned to it).
 
-Add potential fix to resolve edge-case for debugging when breakpoints/stops/interrupts are encountered without a user issuing a command to IDL. This comes from IDL GUI applications that trigger callbacks.
+When running IDL through the debug console, we now properly catch stops/breakpoints that aren't a result of manually sending commands to IDL. This supports use cases where widget/UI applications are running and hit a stop or breakpoint in a callback routine.
 
 ## 4.4.2 - April 2024