Skip to content

Commit 7e684b3

Browse files
Yicong-HuangHyukjinKwon
authored andcommitted
[SPARK-54603][PYTHON][DOCS] Fix typo in contributing.rst
### What changes were proposed in this pull request? Found typo "a example" -> "an example" ### Why are the changes needed? Fix grammar ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? ### Was this patch authored or co-authored using generative AI tooling? No Closes #53336 from Yicong-Huang/SPARK-54603/fix/typo-in-contribution.rst. Authored-by: Yicong-Huang <[email protected]> Signed-off-by: Hyukjin Kwon <[email protected]>
1 parent 179ade2 commit 7e684b3

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

python/docs/source/development/contributing.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -230,7 +230,7 @@ Doctest Conventions
230230
In general, doctests should be grouped logically by separating a newline.
231231

232232
For instance, the first block is for the statements for preparation, the second block is for using the function with a specific argument,
233-
and third block is for another argument. As a example, please refer `DataFrame.rsub <https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.rsub.html#pandas.DataFrame.rsub>`_ in pandas.
233+
and third block is for another argument. As an example, please refer `DataFrame.rsub <https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.rsub.html#pandas.DataFrame.rsub>`_ in pandas.
234234

235235
These blocks should be consistently separated in PySpark doctests, and more doctests should be added if the coverage of the doctests or the number of examples to show is not enough.
236236

0 commit comments

Comments
 (0)