HyukjinKwon commented on a change in pull request #32835:
URL: https://github.com/apache/spark/pull/32835#discussion_r648790216



##########
File path: python/docs/source/development/ps_contributing.rst
##########
@@ -131,21 +131,21 @@ We follow `PEP 8 
<https://www.python.org/dev/peps/pep-0008/>`_ with one exceptio
 Doctest Conventions
 ===================
 
-When writing doctests, usually the doctests in pandas are converted into 
Koalas to make sure the same codes work in Koalas.
+When writing doctests, usually the doctests in pandas are converted into 
pandas APIs on Spark to make sure the same codes work in pandas APIs on Spark.
 In general, doctests should be grouped logically by separating a newline.
 
 For instance, the first block is for the statements for preparation, the 
second block is for using the function with a specific argument,
 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.
 
-These blocks should be consistently separated in Koalas, and more doctests 
should be added if the coverage of the doctests or the number of examples to 
show is not enough even though they are different from pandas'.
+These blocks should be consistently separated in pandas APIs on Spark, and 
more doctests should be added if the coverage of the doctests or the number of 
examples to show is not enough even though they are different from pandas'.

Review comment:
       ```suggestion
   These blocks should be consistently separated in pandas-on-Spark doctests, 
and more doctests should be added if the coverage of the doctests or the number 
of examples to show is not enough even though they are different from pandas'.
   ```




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to