Fix typo Update README.md #329
Open
Conversation
This file contains 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.
Original text: "It should answer as soon as posible"
Corrected text: "It should answer as soon as possible"
Explanation:
The word "posible" was a typo, which was corrected to "possible."
This change enhances the clarity and professionalism of the documentation, ensuring it is free of errors and more accessible to readers.
Change Details:
Lines affected: Line 32 in the README.md file.
Number of changes: One deletion (incorrect text) and one addition (corrected text).
This update adheres to best practices for maintaining high-quality documentation and makes the instructions more precise for users integrating with the events service.