tsonglew opened a new pull request, #59825:
URL: https://github.com/apache/spark/pull/59825

   ### What changes were proposed in this pull request?
   
   Minor grammar and style fixes in `docs/sql-programming-guide.md`:
   
   - `different APIs based on which` → `different APIs, depending on which`
   - `All of the examples` → `All examples`
   - `Python does not have the support for the Dataset API. But due to` → 
`Python does not support the Dataset API. However, due to`
   - `(i.e. you can` → `(i.e., you can` and clarify the `row.columnName` 
example parenthetical
   - `a data frame in R/Python` → `a DataFrame in R/Python`
   - `While, in [Java API]` → `In [Java API]`
   - `Dataset is a new interface` → `A Dataset is a new interface`
   
   This reclaims the closed PR #52396 (author self-closed; the grammar fixes 
never landed on master). The Python Dataset-API sentence is worded as a clean 
paragraph without the awkward line-continuation backslash from that earlier 
attempt.
   
   JIRA: https://issues.apache.org/jira/browse/SPARK-53665
   
   ### Why are the changes needed?
   
   The SQL programming guide has several small grammar/typo issues that make 
the intro harder to read. These are docs-only wording fixes with no behavior 
change.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No (documentation only).
   
   ### How was this patch tested?
   
   Docs-only change; manually reviewed the diff against current `master` and 
confirmed each targeted phrase was updated with no unrelated edits.
   
   Closes #52396 (supersedes; prior PR was self-closed unmerged).


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

To unsubscribe, e-mail: [email protected]

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