README.md in s3_website-2.14.0 vs README.md in s3_website-2.14.1

@@ -70,10 +70,15 @@
 the [dotenv](https://github.com/bkeepers/dotenv) gem. You can create a `.env` file
 in the project's root directory to take advantage of this feature. Please have
 a look at [dotenv's usage guide](https://github.com/bkeepers/dotenv#usage) for
 syntax information.
 
+Your `.env` file should containing the following variables:
+
+    AWS_ACCESS_KEY_ID=FOO
+    AWS_SECRET_ACCESS_KEY=BAR
+
 ## Project goals
 
 * Provide a command-line interface tool for deploying and managing S3 websites
 * Let the user have all the S3 website configurations in a file
 * Minimise or remove the need to use the AWS Console
@@ -167,10 +172,13 @@
 Remember that the extensions here are referring to the *compiled* extensions,
 not the pre-processed extensions.
 
 After changing the `gzip` setting, push with the `--force` option.
 
+s3_website will not gzip a file that is already gzipped. This is useful in the
+situations where your build tools gzip a file before you invoke `s3_website push`.
+
 ### Using non-standard AWS regions
 
 By default, `s3_website` uses the US Standard Region. You can upload your
 website to other regions by adding the setting `s3_endpoint` into the
 `s3_website.yml` file.
@@ -183,10 +191,13 @@
 ```
 
 The valid `s3_endpoint` values consist of the [S3 location constraint
 values](http://docs.amazonwebservices.com/general/latest/gr/rande.html#s3_region).
 
-Note that at the moment s3_website does not support the *eu-central-1* region.
+Note that at the moment s3_website does not support any region that
+supports only a V4 Signature and does not support V2
+ (i.e. *eu-central-1*, *ap-south-1*, *ap-northeast-2*).
+This support can be tracked in [issue #126](https://github.com/laurilehmijoki/s3_website/issues/126).
 
 ### Ignoring files you want to keep on AWS
 
 Sometimes there are files or directories you want to keep on S3, but not on
 your local machine. You may define a regular expression to ignore files like so: