GitHub user HyukjinKwon opened a pull request:

    https://github.com/apache/spark/pull/15952

    [WIP][SPARK-18514][DOCS] Fix the markdown for `Note:`/`NOTE:`/`Note that` 
across R API documentation

    ## What changes were proposed in this pull request?
    
    It seems in R, there are
    
    - `Note:`
    - `NOTE:`
    - `Note that`
    
    This PR proposes to fix those to `Note:` to be consistent.
    
    **Before**
    
    ![2016-11-21 11 30 
07](https://cloud.githubusercontent.com/assets/6477701/20468848/2f27b0fa-afde-11e6-89e3-993701269dbe.png)
    
    
    **After**
    
    ![2016-11-21 11 29 
44](https://cloud.githubusercontent.com/assets/6477701/20468851/39469664-afde-11e6-9929-ad80be7fc405.png)
    
    
    ## How was this patch tested?
    
    The notes were found via
    
    ```bash 
    grep -r "NOTE: " .
    grep -r "Note that " .
    ```
    
    And then fixed one by one comparing with API documentation.
    
    After that, manually tested via `sh create-docs.sh` under `./R`.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/HyukjinKwon/spark SPARK-18514

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/15952.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #15952
    
----
commit ca26d34ee3daa67bf2e38360fe0b3c5c078ba672
Author: hyukjinkwon <[email protected]>
Date:   2016-11-21T02:23:14Z

    Fix `NOTE:` and `Note that` to `Note:` to be consistent

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

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

Reply via email to