README.md in capistrano-asg-rolling-0.3.0 vs README.md in capistrano-asg-rolling-0.4.0

@@ -99,10 +99,18 @@
 ```ruby
 # config/deploy.rb
 set :asg_rolling_instance_overrides, { instance_type: 'c5.large' }
 ```
 
+You can make Capistrano wait until the instances in the autoscaling group have completed refreshing with:
+
+```ruby
+# config/deploy.rb
+set :asg_wait_for_instance_refresh, true
+set :asg_instance_refresh_polling_interval, 30 # default
+```
+
 ## Usage
 
 Specify the Auto Scaling Groups with the keyword `autoscale` instead of using the `server` keyword in Capistrano's stage configuration. Provide the name of the Auto Scaling Group and any properties you want to pass to the server:
 
 ```ruby
@@ -139,10 +147,10 @@
 
 ### Custom stage
 
 The rolling configuration of the stage has a side-effect: any Capistrano tasks you run, will also launch instances per Auto Scaling Group.
 
-For example the command: `cap production rails:console`, will launch a new instance and run `rails:console` and that instance. While that can be useful, you often just want to run the task on the primary server. A solution is to create two stages with different rolling configurations, for example:
+For example the command: `cap production rails:console`, will launch a new instance and run `rails:console` on that instance. While that can be useful, you often just want to run the task on the primary server. A solution is to create two stages with different rolling configurations, for example:
 
 ```ruby
 # config/deploy/production.rb
 set :stage, :production