chore(iam): correct spelling in documentation

[kavichu]

chore(iam): correct spelling in documentation

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[gitpod-io]

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

✅ Updated pull request passes all PRLinter validations. Dissmissing previous PRLinter review.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

Pull request has been modified.

[mrgrain]

@kavichu Thanks for the fix and updating the branch!

In this case it was needed. But just for future reference: Normally you should not update the branch from main, unless there are merge conflicts or workflow conflicts (like this time). It makes everything more complicated for us since any previous reviews will be revoked etc.

[kavichu]

@kavichu Thanks for the fix and updating the branch!

In this case it was needed. But just for future reference: Normally you should not update the branch from main, unless there are merge conflicts. It just makes everything more complicated for us since any previous reviews will be revoked etc.

@mrgrain Sorry for that, I am really into learning the workflow. I thought it would update my fork branch and then hit back to this PR, thanks for the explanation.

[mrgrain]

@kavichu Thanks for the fix and updating the branch!
In this case it was needed. But just for future reference: Normally you should not update the branch from main, unless there are merge conflicts. It just makes everything more complicated for us since any previous reviews will be revoked etc.

@mrgrain Sorry for that, I am really into learning the workflow. I thought it would update my fork branch and then hit back to this PR, thanks for the explanation.

All good! In this situation we did hit one of the two scenarios where an update is required.

It's more of an FYI. Unfortunately GitHub has this shiny "Update branch" button that we cannot disable. 😅
If you ever want to update for any other reason, you can comment @mergifyio update and the automation will take over.

[kavichu]

@kavichu Thanks for the fix and updating the branch!
In this case it was needed. But just for future reference: Normally you should not update the branch from main, unless there are merge conflicts. It just makes everything more complicated for us since any previous reviews will be revoked etc.

@mrgrain Sorry for that, I am really into learning the workflow. I thought it would update my fork branch and then hit back to this PR, thanks for the explanation.

All good! In this situation we did hit one of the two scenarios where an update is required.

It's more of an FYI. Unfortunately GitHub has this shiny "Update branch" button that we cannot disable. 😅 If you ever want to update for any other reason, you can comment @mergifyio update and the automation will take over.

Awesome, next time I know about @mergifyio update and that the shiny button is there only trick you into click it and see what happens. Deep inside I wanted to know what will happen.

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 68e630b
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).