chore: fix minor typos and grammar in docs and comments#8245
Open
Sujit-1509 wants to merge 1 commit into
Open
Conversation
|
Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need. |
|
|
No related issues found. Please ensure there is an open issue related to this change to avoid significant delays or closure. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Summary
Changes
This PR fixes a few low-risk, beginner-friendly typos and grammar issues found in the documentation and inline comments across the codebase:
aws_lambda_powertools/utilities/parameters/ssm.pyRecordsfield in Kinesis documentation (docs/utilities/parser.md)tests/functional/event_handler/_pydantic/test_openapi_responses.py)These changes contain no production logic modifications and solely improve correctness of text.
User experience
Before this change, users reading the parser documentation or developers reading parameter/test comments would encounter small grammar/typography errors. After this change, the text is clean and professional without affecting any runtime behavior or logic.
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.