CHANGELOG.md in ruby-clock-2.0.0.beta6 vs CHANGELOG.md in ruby-clock-2.0.0.beta7

@@ -4,14 +4,20 @@
 * The way the [rails app reloader](https://guides.rubyonrails.org/threading_and_code_execution.html)
   is implemented is now compatible with both rails 6 and 7
 * RUBY_CLOCK_SHUTDOWN_WAIT_SECONDS value is logged when starting
 * DSL methods are now at the top-level namespace (`schedule.every` → `every`, `schedule.cron` → `cron`)
 * Error handler definition is now at the top-level namespace (`def schedule.on_error` → `on_error do`)
-* Around callbacks now have a top-level namespace method. `def schedule.around_trigger` → `around_action` - see readme
-* Multiple around callbacks can be consecutively assigned - no need to put all behavior into one action
-* Errors encountered when loading Clockfile (such as incorrect cron syntaxt)
+* Around callbacks now have a top-level namespace method. `def schedule.around_trigger` → `around_action do`
+* Multiple around callbacks can be consecutively assigned - no need to put all behavior into one method
+* Errors encountered when loading Clockfile (such as incorrect cron syntax)
   will be reported to the error handler
+* The automatic identifier generator will now ignore `}` and `end` lines
+* posix-spawn is no longer used. In ruby 3, native `Process.spawn` is more performant. See
+  [posix-spawn#90](https://github.com/rtomayko/posix-spawn/issues/90)
+  and
+  [terrapin#19](https://github.com/thoughtbot/terrapin/pull/19)
+  for more info.
 
 ### Anti-Features
 * ruby 3.0 is now the minimum version
 
 ### Code Improvements
@@ -24,14 +30,12 @@
 
 * The minimum ruby version is 3.0
 * The top of every Clockfile must begin with `using RubyClock::DSL`
 * If you have an existing `def schedule.around_trigger`, you will need to change it to use the new
   `around_action` method.
-* Your existing Clockfile will still work, but you now have the option to use
+* Your existing Clockfile with `schedule.foo` invocations will still work, but you now have the option to use
   `every`, `cron`, and `on_error` at the top-level, without referencing `schedule`.
-  See the readme for examples.
 * You now have the option of catching and reporting errors encountered when parsing the Clockfile.
-  See the readme.
 * There is no longer a need to have a binstub in rails. You can delete bin/clock from your app.
 * The invocations (in Procfile, or wherever else you start ruby-clock) should change from
 
       bundle exec rails runner bin/clock
   to