GitHub user 1ambda opened a pull request: https://github.com/apache/zeppelin/pull/1998
[ZEPPELIN-2070][DOCS] Create Docs for Spell ### What is this PR for? Docs for Spell which was added by #1940 ### What type of PR is it? [Documentation] ### Todos * [x] - Add docs for spell * [x] - Fix typo in vis docs ### What is the Jira issue? [ZEPPELIN-2070](https://issues.apache.org/jira/browse/ZEPPELIN-2070) ### How should this be tested? - `cd docs` - `/usr/local/bin/bundle exec jekyll serve --watch` - Open `http://localhost:4000/development/writingzeppelinspell.html` ### Screenshots (if appropriate) ![image](https://cloud.githubusercontent.com/assets/4968473/22772190/9e6cfbfc-eede-11e6-8f36-8ee3749d4b36.png) ![image](https://cloud.githubusercontent.com/assets/4968473/22772196/a43de578-eede-11e6-8f49-25f0ae4e5662.png) ### Questions: * Does the licenses files need update? - NO * Is there breaking changes for older versions? - NO * Does this needs documentation? - YES You can merge this pull request into a Git repository by running: $ git pull https://github.com/1ambda/zeppelin ZEPPELIN-2070/docs-for-spell Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1998.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 #1998 ---- commit 04deb81a4d4cd2292b5d57ba151145c7c8f81026 Author: 1ambda <1am...@gmail.com> Date: 2017-02-07T09:20:55Z fix: Invalid desc in vis docs commit 83ee0506092a8c871aabbb5e268fbc0f0b1ebb57 Author: 1ambda <1am...@gmail.com> Date: 2017-02-09T05:12:11Z docs: Add spell doc to nav commit bcc9b3e3ec3b62c4f2ce01e0e44be7383a2a5e3e Author: 1ambda <1am...@gmail.com> Date: 2017-02-09T06:35:38Z docs: Add docs for spell commit c7dc9bdd6a736f6d63b781eea7251fd64646bb71 Author: 1ambda <1am...@gmail.com> Date: 2017-02-09T06:39:21Z fix: Typo in writing in viz ---- --- 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. ---