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



##########
File path: python/docs/source/user_guide/pandas_on_spark/faq.rst
##########
@@ -2,30 +2,25 @@
 FAQ
 ===
 
-Is it Koalas or koalas?
------------------------
+Should I use PySpark's DataFrame API or pandas API on Spark?
+------------------------------------------------------------
 
-It's Koalas. Unlike pandas, we use upper case here.
+If you are already familiar with pandas and want to leverage Spark for big 
data, we recommend using pandas API on Spark.
+If you are learning Spark from ground up, we recommend you start with 
PySpark's API.
 
-Should I use PySpark's DataFrame API or Koalas?
------------------------------------------------
-
-If you are already familiar with pandas and want to leverage Spark for big 
data, we recommend
-using Koalas. If you are learning Spark from ground up, we recommend you start 
with PySpark's API.
-
-Does Koalas support Structured Streaming?
+Does pandas API on Spark support Structured Streaming?
 -----------------------------------------

Review comment:
       @itholic can you fix this underbars? it causes warnings:
   
   ```
   /.../spark/python/docs/source/user_guide/pandas_on_spark/faq.rst:12: 
WARNING: Title underline too short.
   
   Does pandas API on Spark support Structured Streaming?
   -----------------------------------------
   /.../spark/python/docs/source/user_guide/pandas_on_spark/faq.rst:12: 
WARNING: Title underline too short.
   
   Does pandas API on Spark support Structured Streaming?
   -----------------------------------------
   ```




-- 
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