Release v3.4.0 - Adjusting readme file to point to aws s3 additional …

…information

AMAZON-S3-PUBLISHED-URL.MD

@@ -1,8 +1,8 @@
 ##### In Live Blog version 3.4.0 we updated the Superdesk core libraries to a version higher than v1.8
-That version brings breaking changes on how we are dealing with the Amazon s3 publishing of Live Blog's Live URLs: Instead of composing the Amazon URL directly, we now make use of an enviroment variable **MEDIA_PREFIX**
+That version brings breaking changes on how we are dealing with the Amazon s3 publishing of Live Blog's Live URLs: Instead of composing the Amazon URL directly, we now make use of an environment variable **MEDIA_PREFIX**
 that is dealing with that.
 
-To keep the same behaviour prior to 3.4.0  the **MEDIA_PREFIX** needs to be composed on shell
+To keep the same behavior prior to 3.4.0  the **MEDIA_PREFIX** needs to be composed on shell
 ex:
 * export MEDIA_PREFIX = https://<bucket>.s3-<region>.amazonaws.com/<subfolder>
 * export MEDIA_PREFIX = https://<AMAZON_CONTAINER_NAME>.s3-<AMAZON_REGION>.amazonaws.com/<AMAZON_S3_SUBFOLDER>

README.md

@@ -100,6 +100,8 @@ sleep 10
 honcho -f ../docker/Procfile-dev start
 ```
 
+##### In Live Blog version 3.4.0 we updated the Superdesk core libraries to a version higher than v1.8. If you plan to use Amazon S3 to store your assets, please check [this information](AMAZON-S3-PUBLISHED-URL.MD))
+
 #### Configure the client
 
 Now we can install the dependencies for the client
@@ -146,7 +148,7 @@ $ ./scripts/docker-local-demo.sh
 
 ### Testing
 
-How to run the behaviore tests for the syndication feature:
+How to run the behavior tests for the syndication feature:
 
 ```
 cd server
@@ -190,7 +192,7 @@ Once in the virtual machine:
 /opt/liveblog/scripts/vagrant-provision.sh
 ```
 
-Once the provisioning done whil still in the virtual machine:
+Once the provisioning done will still in the virtual machine:
 
 ```
 /opt/liveblog/scripts/vagrant-start-dev.sh