docs: typo for serverless framework

[HaaLeo]

Description of your changes

According to the docs it should be {aws:region} Reference

Related issues, RFCs

Issue number: #1706

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my change is effective and works
• The PR title follows the conventional commit semantics

Breaking change checklist

Is it a breaking change?: NO

• I have documented the migration process
• I have added, implemented necessary warnings (if it can live side by side)

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[boring-cyborg]

Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need.
In the meantime, check out the #typescript channel on our Powertools for AWS Lambda Discord: Invite link

[github-actions]

No related issues found. Please ensure there is an open issue related to this change to avoid significant delays or closure.

[am29d]

Thanks for PR fixing the typo. I have added the issue #1706 .

We need also to adjust the update layer script here so we can update the layer version in the docs. Could you please change this file as well?

[HaaLeo]

Hi @am29d, thx for creating the issue. I've updated the script as well.
You can review once more. :)

[am29d]

Thanks @HaaLeo for the PR 🙏 , closes #1706 .

[am29d]

Hey @HaaLeo , apologies for the merge conflict, I have approved the PR during a minor release and it changed the index.md during the layer version update. Can I ask you to resolve the conflict this last time, then we can merge it and update the docs (we can update docs outside of release cycle).

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[HaaLeo]

@am29d now it should be good to go

[boring-cyborg]

Awesome work, congrats on your first merged pull request and thank you for helping improve everyone's experience!