[camel-k] branch master updated: corrected minor spelling or wrong language reference (Kotlin => JavaScript)

[nf...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

nferraro pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-k.git


The following commit(s) were added to refs/heads/master by this push:
     new bf9609f  corrected minor spelling or wrong language reference (Kotlin => JavaScript)
bf9609f is described below

commit bf9609f0361e50c071bb3a4436827d6c8cd7675f
Author: mala <zF7geWvehUkN7anRtMJARwHdYTLNjwQe>
AuthorDate: Sat Oct 20 15:03:32 2018 +0200

    corrected minor spelling or wrong language reference (Kotlin => JavaScript)
---
 README.adoc         | 4 ++--
 docs/languages.adoc | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/README.adoc b/README.adoc
index f969ee3..dd52f01 100644
--- a/README.adoc
+++ b/README.adoc
@@ -146,11 +146,11 @@ Camel K supports multiple languages for writing integrations:
 | Java				| Both integrations in source `.java` files or compiled `.class` file can be run.
 | XML				| Integrations written in plain XML DSL are supported (Spring XML or Blueprint not supported).
 | Groovy			| Groovy `.groovy` files are supported (experimental).
-| JavaScript                    | JavaScript `.js` files are supported (experimental).
+| JavaScript        | JavaScript `.js` files are supported (experimental).
 | Kotlin			| Kotlin Script `.kts` files are supported (experimental).
 |=======================
 
-More information about supported languages is provided in the link:docs/languages.adoc[lanuguages guide].
+More information about supported languages is provided in the link:docs/languages.adoc[languages guide].
 
 Integrations written in different languages are provided in the link:/runtime/examples[examples] directory.
 
diff --git a/docs/languages.adoc b/docs/languages.adoc
index 1bef183..42f0557 100644
--- a/docs/languages.adoc
+++ b/docs/languages.adoc
@@ -20,7 +20,7 @@ Work In Progress
 
 === Java
 
-Using java to write an integration to be deployed using camel-k is not different from defining your routing rules in Camel with the only difference that you do not need to build and package it as a jar.
+Using Java to write an integration to be deployed using camel-k is not different from defining your routing rules in Camel with the only difference that you do not need to build and package it as a jar.
 
 [source,java]
 .Example
@@ -271,7 +271,7 @@ rest {
 
 === JavaScript
 
-integration written in Kotlin looks very similar to a Java one:
+The integration written in JavaScript looks very similar to a Java one:
 
 [source,js]
 ----