docs: fix typo #439
Merged
docs: fix typo #439
Conversation
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
"chanages" -> "changes"
"emmited" -> "emitted"
1. "emmited" -> "emitted" 2. "backrgound" -> "background"
|
This PR has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. If you believe this was a mistake, please comment. |
|
This PR has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. If you believe this was a mistake, please comment. |
|
thanks! |
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.
Change Overview
This change corrects typos in contributing.md and types.ts: "chanages" to "changes," "emmited" to "emitted," and "backrgound" to "background." These corrections improve clarity and professionalism in the documentation and code, ensuring a better user experience.
Impact of Change
Detailed Technical Description of Change
Fixed minor typos in the documentation.
Testing Approach and Results
No testing needed for typo fixes, but the documentation has been reviewed to ensure accuracy.
Collateral Work or Changes
No collateral work or changes required.
Operational Impact
No operational impact, as the changes are purely cosmetic.