GitHub user rfilmyer opened a pull request:
https://github.com/apache/zeppelin/pull/1416
Rewrite of "Quick Start" page.
### What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide -
https://github.com/apache/zeppelin/blob/master/CONTRIBUTING.md
This is a rewrite of the "Quick Start" page, fixing syntax/grammar issues
while trying to keep to the original content. I may look at other pages, but I
wanted my first PR to be very small.
### What type of PR is it?
Documentation
### Todos
Verify the accuracy of the configuration settings section
### What is the Jira issue?
(Does this apply to documentation PRs?)
### How should this be tested?
Do documentation changes like this need to be tested?
If so, is the github preview sufficient for these changes? How is
Zeppelin's markdown interpreter different than Github's?
If Github's MD preview isn't sufficient, is it possible to build the
documentation locally?
### Screenshots (if appropriate)
### Questions:
* Since this is my first PR on the project, I limited the scope of my
changes. Is there any desire to change the content of these pages in any way?
Do we have documentation conventions?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rfilmyer/zeppelin master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1416.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 #1416
----
commit f2c126bdb9bfc51bb59b7b02e7cbcece92cf32de
Author: Roger Filmyer <roger.film...@gmail.com>
Date: 2016-09-08T18:45:54Z
Rewrite of "Quick Start"
I rewrote the "Quick Start"/installation page for syntax and grammar,
trying to keep the to the original content as much as possible.
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
