README.md in elasticity-6.0.6 vs README.md in elasticity-6.0.7

@@ -129,10 +129,11 @@
 jobflow.placement                         = 'us-east-1a'
 jobflow.region                            = 'us-east-1'
 jobflow.instance_count                    = 2
 jobflow.master_instance_type              = 'm1.small'
 jobflow.slave_instance_type               = 'm1.small'
+jobflow.additonal_info                    = 'additonal info'
 ```
 
 ### EMR Applications (optional needs release_label >= 4.0.0)
 With the release of EMR 4.0.0 you can now supply applications which EMR will install for you on boot(rather than a manual bootstrap action. Which you can still use if required). You must set the `release_label` for the jobflow(>=4.0.0)
 
@@ -332,9 +333,13 @@
 ```ruby
 copy_step = Elasticity::S3DistCpStep.new
 copy_step.arguments = [...]
 
 jobflow.add_step(copy_step)
+
+# For AMI < 4.x you need to specifify legacy argument
+copy_step = Elasticity::S3DistCpStep.new(true)
+
 ```
 
 ## 7 - Upload Assets (optional)
 
 This isn't part of ```JobFlow```; more of an aside.  Elasticity provides a very basic means of uploading assets to S3 so that your EMR job has access to them.  Most commonly this will be a set of resources to run the job (e.g. JAR files, streaming scripts, etc.) and a set of resources used by the job itself (e.g. a TSV file with a range of valid values, join tables, etc.).