camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gno...@apache.org
Subject [camel] 02/03: Fix typo
Date Wed, 05 Sep 2018 14:46:55 GMT
This is an automated email from the ASF dual-hosted git repository.

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

commit d30d920c490a8f453e3b720e7d5fc5459a94676f
Author: Guillaume Nodet <gnodet@gmail.com>
AuthorDate: Tue Sep 4 11:03:53 2018 +0200

    Fix typo
---
 docs/user-manual/en/lifecycle.adoc | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/docs/user-manual/en/lifecycle.adoc b/docs/user-manual/en/lifecycle.adoc
index 7a0ca83..b03270b 100644
--- a/docs/user-manual/en/lifecycle.adoc
+++ b/docs/user-manual/en/lifecycle.adoc
@@ -33,14 +33,13 @@ The operations is paired: start/stop and suspend/resume.
 
 Stop is performing a Graceful shutdown
 which means all its internal state, cache, etc is cleared. And the
-routes is being stopped in a graceful manner to ensure messages is given
+routes is being stopped in a graceful manner to ensure messages are given
 time to complete. If you start a `CamelContext` after a stop, then its
 performing a _cold_ start, recreating all the state, cache etc. again.
 
 Instead you can use the suspend/resume operations. They will keep the
 `CamelContext` _warm_ and only suspend/stop routes using the same
-Graceful shutdown feature. This ensures
-messages is given time to complete.
+Graceful shutdown feature. This ensures messages are given time to complete.
 
 End users is encouraged to use suspend/resume if you are temporary
 stopping a Camel application.


Mime
View raw message