[ARVADOS] updated: 1.1.4-509-g32d954c32

[Git user]

Summary of changes:
 doc/admin/spot-instances.html.textile.liquid | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

       via  32d954c32f20a982bec4b3615bfd7cfca449c280 (commit)
      from  e9e440847c574d1152b128cfd508cf473f49121b (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.


commit 32d954c32f20a982bec4b3615bfd7cfca449c280
Author: Lucas Di Pentima <ldipentima at veritasgenetics.com>
Date:   Wed Jun 27 14:47:14 2018 -0300

    13649: Fixes in wording
    
    Arvados-DCO-1.1-Signed-off-by: Lucas Di Pentima <ldipentima at veritasgenetics.com>

diff --git a/doc/admin/spot-instances.html.textile.liquid b/doc/admin/spot-instances.html.textile.liquid
index 88f2def43..1c61b6074 100644
--- a/doc/admin/spot-instances.html.textile.liquid
+++ b/doc/admin/spot-instances.html.textile.liquid
@@ -63,13 +63,13 @@ With this configuration active, child container requests should include the @pre
 
 h3. AWS Permissions
 
-When requesting spot instances, Amazon's API may return an authorization error depending on how users and permissions are set on the account. If attempting to use this feature with an already working AWS account and getting an error message on nodemanager's log like this one:
+When requesting spot instances, Amazon's API may return an authorization error depending on how users and permissions are set on the account. If this is the case check nodemanager's log for:
 
 <pre>
 BaseHTTPError: AuthFailure.ServiceLinkedRoleCreationNotPermitted: The provided credentials do not have permission to create the service-linked role for EC2 Spot Instances.
 </pre>
 
-...the account needs to have a service linked role created. For this, you can log into your AWS account, go to _IAM Management_ → _Roles_ and create the @AWSServiceRoleForEC2Spot@ role by clicking on the @Create@ button, selecting @EC2@ service and @EC2 - Spot Instances@ use case.
+The account needs to have a service linked role created. This can be done by logging into the AWS account, go to _IAM Management_ → _Roles_ and create the @AWSServiceRoleForEC2Spot@ role by clicking on the @Create@ button, selecting @EC2@ service and @EC2 - Spot Instances@ use case.
 
 h3. Cost Tracking
 

-----------------------------------------------------------------------


hooks/post-receive
--