example-configurations.md in s3_website-1.1.0 vs example-configurations.md in s3_website-1.1.1

@@ -17,12 +17,14 @@
 ````
 
 If you run `s3_website` on an EC2 instance with IAM roles, it is possible to omit
 the `s3_id` and `s3_secret`.
 
-## Optimised for speed: using CloudFront, gzip and cache headers
+## Optimised for speed
 
+Use CloudFront, gzip, cache headers and greater concurrency:
+
 ````yaml
 s3_id: <%= ENV['your_domain_net_aws_key'] %>
 s3_secret: <%= ENV['your_domain_net_aws_secret'] %>
 s3_bucket: your.domain.net
 cloudfront_distribution_id: <%= ENV['your_domain_net_cloudfront_distribution_id'] %>
@@ -33,9 +35,10 @@
     quantity: 1
     items:
       CNAME: your.domain.net
 max_age: 120
 gzip: true
+concurrency_level: 100
 ````
 
 Above, we store the AWS credentials and the id of the CloudFront distribution as
 environment variables. It's convenient, since you can keep the `s3_website.yml`
 in a public Git repo, and thus have your deployment configurations