Skip to content

Commit d3856a4

Browse files
minor readme adjustment
1 parent d649e91 commit d3856a4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -108,7 +108,7 @@ There are four different supported ways to retrieve credentials. We recommend
108108
using [GitHub's OIDC provider](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services)
109109
to get short-lived credentials needed for your actions. Specifying
110110
`role-to-assume` **without** providing an `aws-access-key-id` or a
111-
`web-identity-token-file` (or setting `role-chaining`) will signal to the action that you wish to use the
111+
`web-identity-token-file`, or setting `role-chaining`, will signal to the action that you wish to use the
112112
OIDC provider. If `role-chaining` is `true`, existing credentials in the environment will be used to assume `role-to-assume`.
113113

114114
The following table describes which identity is used based on which values are supplied to the Action:

0 commit comments

Comments
 (0)