fix: correct log, Javadoc, and documentation grammar in SES and SQS#1623
Open
Baqirrizvidev wants to merge 1 commit into
Open
fix: correct log, Javadoc, and documentation grammar in SES and SQS#1623Baqirrizvidev wants to merge 1 commit into
Baqirrizvidev wants to merge 1 commit into
Conversation
Baqirrizvidev
requested review from
MatejNedic,
maciejwalkowiak and
tomazfernandes
as code owners
github-actions
Bot
added
component: ses
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
1 participant
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.
This PR corrects minor spelling/grammatical issues in the logs, Javadoc comments, and Asciidoc documentation for the Simple Email Service (SES) and Simple Queue Service (SQS) modules:
"Message with id: {} successfully send"instead of"successfully sent".allows to sendtoallows sending.allows to create andtoallows you to create and.allows to specify thetoallows you to specify the.These adjustments improve overall phrasing, standard grammar usage, and log correctness across the codebase.