GitHub user srowen opened a pull request:

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

    SPARK-1727. Correct small compile errors, typos, and markdown issues in 
(primarly) MLlib docs

    While play-testing the Scala and Java code examples in the MLlib docs, I 
noticed a number of small compile errors, and some typos. This led to finding 
and fixing a few similar items in other docs.
    
    Then in the course of building the site docs to check the result, I found a 
few small suggestions for the build instructions. I also found a few more 
formatting and markdown issues uncovered when I accidentally used maruku 
instead of kramdown.

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

    $ git pull https://github.com/srowen/spark SPARK-1727

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

    https://github.com/apache/spark/pull/653.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 #653
    
----
commit bac89285b057073941b6599c9c6596af10898e6a
Author: Sean Owen <[email protected]>
Date:   2014-05-05T09:32:58Z

    Fix small compile errors and typos across MLlib docs

commit d1c6ef2e572bcf798ba217ab304edfe194655d6a
Author: Sean Owen <[email protected]>
Date:   2014-05-05T19:52:56Z

    Add Scala Naive Bayes example, to use existing example data file (whose 
format needed a tweak)

commit 394562cc1d3d142f0af0d276556d34dee4cf881a
Author: Sean Owen <[email protected]>
Date:   2014-05-05T22:00:22Z

    Update issue tracker URL in docs

commit b2a6a21cec709d3c6d70798500cf831d486c1810
Author: Sean Owen <[email protected]>
Date:   2014-05-05T22:10:21Z

    Fix markdown syntax issues that maruku flags, even though we use kramdown 
(but only those that do not affect kramdown's output)

commit 5b739e8532defad7f3cd22c8122ca03fd88b3441
Author: Sean Owen <[email protected]>
Date:   2014-05-05T22:16:14Z

    Final doc updates - one more compile error, and use of mean instead of sum 
and count

----


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

Reply via email to