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

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

commit f56fd013fad422ae0b9e4d9eb8d60663dc6639b9
Author: Bilgin Ibryam <bibr...@gmail.com>
AuthorDate: Wed Dec 12 12:53:17 2018 +0000

    Fixed typo in docs
---
 camel-core/src/main/docs/rest-dsl.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/camel-core/src/main/docs/rest-dsl.adoc 
b/camel-core/src/main/docs/rest-dsl.adoc
index b5e4fce..5d552aa 100644
--- a/camel-core/src/main/docs/rest-dsl.adoc
+++ b/camel-core/src/main/docs/rest-dsl.adoc
@@ -207,7 +207,7 @@ the <<simple-language,Simple>> language, but it has more 
power than so.
 
 === Embedding Camel routes
 
-Each of the rest service becomes a Camel route, so in the first example
+Each of the rest services becomes a Camel route, so in the first example
 we have 2 x get and 1 x post REST service, which each become a Camel
 route. And we have 2 regular Camel routes, meaning we have 3 + 2 = 5
 routes in total. 
@@ -258,7 +258,7 @@ today.
 
 === Managing Rest services
 
-Each of the rest service becomes a Camel route, so in the first example
+Each of the rest services becomes a Camel route, so in the first example
 we have 2 x get and 1 x post REST service, which each become a Camel
 route. This makes it _the same_ from Camel to manage and run these
 services - as they are just Camel routes. This means any tooling and API

Reply via email to