README.md in rufus-scheduler-3.9.1 vs README.md in rufus-scheduler-3.9.2

@@ -70,22 +70,27 @@
 
 It does not persist your schedules. When the process is gone and the scheduler instance with it, the schedules are gone.
 
 A rufus-scheduler instance will go on scheduling while it is present among the objects in a Ruby process. To make it stop scheduling you have to call its [`#shutdown` method](#schedulershutdown).
 
+Please note: rufus-scheduler is not a cron replacement.
 
-## related and similar gems
 
-* [Whenever](https://github.com/javan/whenever) - let cron call back your Ruby code, trusted and reliable cron drives your schedule
+## related gems
+
 * [ruby-clock](https://github.com/jjb/ruby-clock) - a clock process / job scheduler for Ruby
+* [Puma-Rufus-Scheduler](https://github.com/javierav/puma-rufus-scheduler) - Puma plugin to run Rufus-Scheduler
+
+
+## similar gems
+
+* [Whenever](https://github.com/javan/whenever) - let cron call back your Ruby code, trusted and reliable cron drives your schedule
 * [Clockwork](https://github.com/Rykian/clockwork) - rufus-scheduler inspired gem
 * [Crono](https://github.com/plashchynski/crono) - an in-Rails cron scheduler
 * [PerfectSched](https://github.com/treasure-data/perfectsched) - highly available distributed cron built on [Sequel](https://sequel.jeremyevans.net) and more
 
-(please note: rufus-scheduler is not a cron replacement)
 
-
 ## note about the 3.0 line
 
 It's a complete rewrite of rufus-scheduler.
 
 There is no EventMachine-based scheduler anymore.
@@ -1459,11 +1464,11 @@
 
 ### :scheduler_lock and :trigger_lock
 
 (introduced in rufus-scheduler 3.0.9).
 
-Another way of prodiving `#lock`, `#unlock` and `#confirm_lock` to a rufus-scheduler is by using the `:scheduler_lock` and `:trigger_lock` options.
+Another way of providing `#lock`, `#unlock` and `#confirm_lock` to a rufus-scheduler is by using the `:scheduler_lock` and `:trigger_lock` options.
 
 See [:trigger_lock](#trigger_lock) and [:scheduler_lock](#scheduler_lock).
 
 The scheduler lock may be used to prevent a scheduler from starting, while a trigger lock prevents individual jobs from triggering (the scheduler goes on scheduling).
 
@@ -1777,10 +1782,10 @@
 
 If, anyway, you need something like `rails server -d`, why not try `bundle exec unicorn -D` instead? In my (limited) experience, it worked out of the box (well, had to add `gem 'unicorn'` to `Gemfile` first).
 
 ### executor / reloader
 
-You might benefit from wraping your scheduled code in the executor or reloader. Read more here: https://guides.rubyonrails.org/threading_and_code_execution.html
+You might benefit from wrapping your scheduled code in the executor or reloader. Read more here: https://guides.rubyonrails.org/threading_and_code_execution.html
 
 ## support
 
 see [getting help](#getting-help) above.