This is an automated email from the ASF dual-hosted git repository.
uros-b pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/spark.git
The following commit(s) were added to refs/heads/master by this push:
new 92343dbe37f3 [MINOR][PYTHON][DOC] Improve PySpark contributing
documentation wording
92343dbe37f3 is described below
commit 92343dbe37f3a660c8fd21d561a40210ac2bdf12
Author: Israel Obukonise <[email protected]>
AuthorDate: Wed Jul 22 15:54:38 2026 +0000
[MINOR][PYTHON][DOC] Improve PySpark contributing documentation wording
### What changes were proposed in this pull request?
This PR fixes a few grammar issues in the PySpark contributing
documentation.
### Why are the changes needed?
The current wording contains a few minor grammar issues, including phrases
such as "This release candidates", "generate the documentations", and "raise a
API request". This update improves readability without changing the technical
meaning of the documentation.
### Does this PR introduce _any_ user-facing change?
No. This is a documentation-only change and does not change runtime
behavior.
### How was this patch tested?
Ran:
git diff --check
### Was this patch authored or co-authored using generative AI tooling?
No
Closes #56821 from Israelobuk/improve-pyspark-contributing-docs.
Authored-by: Israel Obukonise <[email protected]>
Signed-off-by: Uros Bojanic <[email protected]>
---
python/docs/source/development/contributing.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/python/docs/source/development/contributing.rst
b/python/docs/source/development/contributing.rst
index ee26de1af211..bbf7c49a17d7 100644
--- a/python/docs/source/development/contributing.rst
+++ b/python/docs/source/development/contributing.rst
@@ -29,7 +29,7 @@ Contributing by Testing Releases
--------------------------------
Before the official release, PySpark release candidates are shared in the
`[email protected] <https://mail-archives.apache.org/mod_mbox/spark-dev/>`_
mailing list to vote on.
-This release candidates can be easily installed via pip. For example, in case
of Spark 3.0.0 RC1, you can install as below:
+These release candidates can be easily installed via pip. For example, in case
of Spark 3.0.0 RC1, you can install as below:
.. code-block:: bash
@@ -48,7 +48,7 @@ Contributing Documentation Changes
The release documentation is located under Spark's `docs
<https://github.com/apache/spark/tree/master/docs>`_ directory.
`README.md <https://github.com/apache/spark/blob/master/docs/README.md>`_
describes the required dependencies and steps
-to generate the documentations. Usually, PySpark documentation is tested with
the command below
+to generate the documentation. Usually, PySpark documentation is tested with
the command below
under the `docs <https://github.com/apache/spark/tree/master/docs>`_ directory:
.. code-block:: bash
@@ -81,7 +81,7 @@ Additionally, there are a couple of additional notes to keep
in mind when contri
Apache Spark is an unified engine that provides a consistent API layer. In
general, the APIs are consistently supported across other languages.
* PySpark-specific APIs can be accepted
- As long as they are Pythonic and do not conflict with other existent APIs,
it is fine to raise a API request, for example, decorator usage of UDFs.
+ As long as they are Pythonic and do not conflict with other existent APIs,
it is fine to raise an API request, for example, decorator usage of UDFs.
* Adjust the corresponding type hints if you extend or modify public API
See `Contributing and Maintaining Type Hints`_ for details.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
