README.md in cronitor-5.0.0 vs README.md in cronitor-5.1.0

@@ -27,22 +27,22 @@
 
 ```ruby
 require 'cronitor'
 Cronitor.api_key = 'api_key_123'
 
-Cronitor.job 'warehouse-replenishmenth-report' do
-  ReplenishmentReport.new(Date.today).run()
+Cronitor.job 'important-job' do
+    ImportantJob.new(Date.today).run()
 end
 ```
 
 ### Integrating with Sidekiq
 Cronitor provides a [separate library](https://github.com/cronitorio/cronitor-sidekiq) built with this SDK to make Sidekiq integration even easier.
 
 
 ## Sending Telemetry Events
 
-If you want finer control over when/how [telemetry pings](https://cronitor.io/docs/telemetry-api) are sent,
+If you want more control over when/how [telemetry pings](https://cronitor.io/docs/telemetry-api) are sent,
 you can instantiate a monitor and call `#ping`.
 
 ```ruby
 require 'cronitor'
 Cronitor.api_key = 'api_key_123'
@@ -130,11 +130,11 @@
 You can also create and update monitors by calling `Monitor.put`.
 
 ```ruby
 require 'cronitor'
 
-monitors = Cronitor::Monitor.put([
+monitors = [
   {
     type: 'job',
     key: 'send-customer-invoices',
     schedule: '0 0 * * *',
     assertions: [
@@ -146,16 +146,18 @@
     type: 'check',
     key: 'Cronitor Homepage',
     request: {
         url: 'https://cronitor.io'
     },
-    schedule: 'every 45 seconds',
+    schedule: 'every 60 seconds',
     assertions: [
         'response.code = 200',
         'response.time < 600ms',
     ]
   }
-])
+]
+
+Cronitor::Monitor.put(monitors)
 ```
 
 ### Pause, Reset, Delete
 
 ```ruby