[MINOR][PYTHON][DOCS] Fix a typo in pyspark documentation #50492
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
zhengruifeng
approved these changes
Apr 8, 2025
|
@kirisakow would you mind enabling the github action? you can refer to https://spark.apache.org/contributing.html and please fill the PR description, thanks |
zhengruifeng
changed the title
|
@zhengruifeng I believe I already have enabled GitHub Actions on the same day the PR was created. Not sure there's anything else I can do, sorry. |
|
LGTM |
|
I am going to merge it into master, the change is minor, no test is ran though |
|
merged to master, 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.
What changes were proposed in this pull request?
This PR aims to fix a minor typo in PySpark documentation.
Why are the changes needed?
...
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass Github Actions
Was this patch authored or co-authored using generative AI tooling?
No.