Repository: zeppelin Updated Branches: refs/heads/branch-0.6 36580c665 -> 93956d80c
[ZEPPELIN-1202] Documentation typo under writing interpreter docs ### What is this PR for? To correct typo found in documentation ### What type of PR is it? Documentation ### Todos * [x] - Replace sentence with incorrect english docs with correction. ### What is the Jira issue? * https://issues.apache.org/jira/browse/ZEPPELIN-1202 ### How should this be tested? Build docs and see correct docs on `https://zeppelin.apache.org/docs/latest/development/writingzeppelininterpreter.html` ### Screenshots (if appropriate) ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? no Author: Zak Hassan <[email protected]> Closes #1198 from zmhassan/ZEPPELIN-1202 and squashes the following commits: 5b3d708 [Zak Hassan] Making correction to Json snippet inside docs. f3e2150 [Zak Hassan] Corrected typo of interpreter-setting.json file should not be interpareter-setting.json 8d6e068 [Zak Hassan] Documentation typo creation. (cherry picked from commit 4e6c7990ccb6bf25696ca9094f2fe0e688f40c0a) Signed-off-by: Mina Lee <[email protected]> Project: http://git-wip-us.apache.org/repos/asf/zeppelin/repo Commit: http://git-wip-us.apache.org/repos/asf/zeppelin/commit/93956d80 Tree: http://git-wip-us.apache.org/repos/asf/zeppelin/tree/93956d80 Diff: http://git-wip-us.apache.org/repos/asf/zeppelin/diff/93956d80 Branch: refs/heads/branch-0.6 Commit: 93956d80cb72f88d96234cdb0a07f9913aea1c15 Parents: 36580c6 Author: Zak Hassan <[email protected]> Authored: Sun Jul 17 22:59:33 2016 -0400 Committer: Mina Lee <[email protected]> Committed: Tue Jul 19 16:00:37 2016 +0900 ---------------------------------------------------------------------- docs/development/writingzeppelininterpreter.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/zeppelin/blob/93956d80/docs/development/writingzeppelininterpreter.md ---------------------------------------------------------------------- diff --git a/docs/development/writingzeppelininterpreter.md b/docs/development/writingzeppelininterpreter.md index 7e7f4ef..d40101b 100644 --- a/docs/development/writingzeppelininterpreter.md +++ b/docs/development/writingzeppelininterpreter.md @@ -40,15 +40,15 @@ In 'Separate Interpreter(scoped / isolated) for each note' mode which you can se ## Make your own Interpreter Creating a new interpreter is quite simple. Just extend [org.apache.zeppelin.interpreter](https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/interpreter/Interpreter.java) abstract class and implement some methods. -You can include `org.apache.zeppelin:zeppelin-interpreter:[VERSION]` artifact in your build system. And you should your jars under your interpreter directory with specific directory name. Zeppelin server reads interpreter directories recursively and initializes interpreters including your own interpreter. +You can include `org.apache.zeppelin:zeppelin-interpreter:[VERSION]` artifact in your build system. And you should put your jars under your interpreter directory with a specific directory name. Zeppelin server reads interpreter directories recursively and initializes interpreters including your own interpreter. -There are three locations where you can store your interpreter group, name and other information. Zeppelin server tries to find the location below. Next, Zeppelin tries to find `interpareter-setting.json` in your interpreter jar. +There are three locations where you can store your interpreter group, name and other information. Zeppelin server tries to find the location below. Next, Zeppelin tries to find `interpreter-setting.json` in your interpreter jar. ``` {ZEPPELIN_INTERPRETER_DIR}/{YOUR_OWN_INTERPRETER_DIR}/interpreter-setting.json ``` -Here is an example of `interpareter-setting.json` on your own interpreter. +Here is an example of `interpreter-setting.json` on your own interpreter. ```json [ @@ -57,7 +57,7 @@ Here is an example of `interpareter-setting.json` on your own interpreter. "name": "your-name", "className": "your.own.interpreter.class", "properties": { - "propertiies1": { + "properties1": { "envName": null, "propertyName": "property.1.name", "defaultValue": "propertyDefaultValue", @@ -216,4 +216,4 @@ We welcome contribution to a new interpreter. Please follow these few steps: - Add documentation on how to use your interpreter under `docs/interpreter/`. Follow the Markdown style as this [example](https://github.com/apache/zeppelin/blob/master/docs/interpreter/elasticsearch.md). Make sure you list config settings and provide working examples on using your interpreter in code boxes in Markdown. Link to images as appropriate (images should go to `docs/assets/themes/zeppelin/img/docs-img/`). And add a link to your documentation in the navigation menu (`docs/_includes/themes/zeppelin/_navigation.html`). - Most importantly, ensure licenses of the transitive closure of all dependencies are list in [license file](https://github.com/apache/zeppelin/blob/master/zeppelin-distribution/src/bin_license/LICENSE). - Commit your changes and open a [Pull Request](https://github.com/apache/zeppelin/pulls) on the project [Mirror on GitHub](https://github.com/apache/zeppelin); check to make sure Travis CI build is passing. - \ No newline at end of file +
