diff --git a/docs/development/howtocontributewebsite.md b/docs/development/howtocontributewebsite.md index 2ee299b40aa..0c2bafc5b64 100644 --- a/docs/development/howtocontributewebsite.md +++ b/docs/development/howtocontributewebsite.md @@ -62,7 +62,7 @@ When you are ready, just make a pull-request. ## Alternative way -You can directly edit `.md` files in `/docs/` directory at the web interface of github and make pull-request immediatly. +You can directly edit `.md` files in `/docs/` directory at the web interface of github and make pull-request immediately. ## Stay involved Contributors should join the Zeppelin mailing lists. diff --git a/docs/install/install.md b/docs/install/install.md index 4d81fe5ce7f..b80bbd22cdb 100644 --- a/docs/install/install.md +++ b/docs/install/install.md @@ -183,7 +183,7 @@ Congratulation on your successful Apache Zeppelin installation! Here are two nex * If you need more configuration setting for Apache Zeppelin, jump to the next section: [Apache Zeppelin Configuration](#apache-zeppelin-configuration). #### If you need more information about Spark or JDBC interpreter setting - * Apache Zeppelin provides deep integration with [Apache Spark](http://spark.apache.org/). For the further informtation, see [Spark Interpreter for Apache Zeppelin](../interpreter/spark.html). + * Apache Zeppelin provides deep integration with [Apache Spark](http://spark.apache.org/). For the further information, see [Spark Interpreter for Apache Zeppelin](../interpreter/spark.html). * Also, you can use generic JDBC connections in Apache Zeppelin. Go to [Generic JDBC Interpreter for Apache Zeppelin](../interpreter/jdbc.html). #### If you are in multi-user environment diff --git a/docs/install/virtual_machine.md b/docs/install/virtual_machine.md index 45aa00f997b..d30dbb8d9ca 100644 --- a/docs/install/virtual_machine.md +++ b/docs/install/virtual_machine.md @@ -75,7 +75,7 @@ into a directory on your host machine, or directly in your virtual machine. Cloning Zeppelin into the `/scripts/vagrant/zeppelin-dev` directory from the host, will allow the directory to be shared between your host and the guest machine. -Cloning the project again may seem counter intuitive, since this script likley originated from the project repository. Consider copying just the vagrant/zeppelin-dev script from the Zeppelin project as a stand alone directory, then once again clone the specific branch you wish to build. +Cloning the project again may seem counter intuitive, since this script likely originated from the project repository. Consider copying just the vagrant/zeppelin-dev script from the Zeppelin project as a stand alone directory, then once again clone the specific branch you wish to build. Synced folders enable Vagrant to sync a folder on the host machine to the guest machine, allowing you to continue working on your project's files on your host machine, but use the resources in the guest machine to compile or run your project. _[(1) Synced Folder Description from Vagrant Up](https://docs.vagrantup.com/v2/synced-folders/index.html)_ diff --git a/docs/manual/interpreters.md b/docs/manual/interpreters.md index c47d5369d8a..70b94d42bca 100644 --- a/docs/manual/interpreters.md +++ b/docs/manual/interpreters.md @@ -79,6 +79,6 @@ interpreter.start() ``` -The above code will start interpreter thread inside your process. Once the interpreter is started you can configure zeppelin to connect to RemoteInterpreter by checking **Connect to existing process** checkbox and then provide **Host** and **Port** on which interpreter porocess is listening as shown in the image below: +The above code will start interpreter thread inside your process. Once the interpreter is started you can configure zeppelin to connect to RemoteInterpreter by checking **Connect to existing process** checkbox and then provide **Host** and **Port** on which interpreter process is listening as shown in the image below: