[SPARK-53679] Fix typos in Spark Kubernetes Operator documentation #334
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
- Fix grammar error in config property description ("to for" → "for")
- Correct property name consistency in configuration.md
- Fix spelling errors: registory→registry, secuirty→security, etc.
- Update cluster state diagram reference to use correct image
- Fix table header typo and various other spelling corrections
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
viirya
approved these changes
Sep 23, 2025
|
cc @jiangzho |
|
Congratulations for your first commit on K8s repository, @peter-toth . |
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.
What changes were proposed in this pull request?
This PR fixes a few typos in the documentation:
Why are the changes needed?
To have better documentation.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
This PR changes only documentation, no test is needed.
Was this patch authored or co-authored using generative AI tooling?
Yes, this PR was generated with
claude-sonnet-4and was reviewed manually.