[camel] branch master updated: Document update (#4215)

[ac...@apache.org]

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


The following commit(s) were added to refs/heads/master by this push:
     new 6324b16  Document update (#4215)
6324b16 is described below

commit 6324b1637cdb510fd5165f328425e911767d3666
Author: Nitesh Koushik S <39...@users.noreply.github.com>
AuthorDate: Mon Sep 14 12:21:34 2020 +0530

    Document update (#4215)
    
    * Document update
    
    Grammatical correction
    
    * Document Update
    
    Change in key word from "shoud" to "should"
---
 .../src/main/docs/modules/eips/pages/saga-eip.adoc                | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/core/camel-core-engine/src/main/docs/modules/eips/pages/saga-eip.adoc b/core/camel-core-engine/src/main/docs/modules/eips/pages/saga-eip.adoc
index e16b875..5bfb24e 100644
--- a/core/camel-core-engine/src/main/docs/modules/eips/pages/saga-eip.adoc
+++ b/core/camel-core-engine/src/main/docs/modules/eips/pages/saga-eip.adoc
@@ -77,7 +77,7 @@ The service belongs to the `camel-core` module.
 === Using the LRA Saga Service
 
 The LRA Saga Service is an implementation based on the MicroProfile sandbox LRA specification.
-It leverages a *external Saga coordinator* to control the execution of the various steps of the Saga.
+It leverages an *external Saga coordinator* to control the execution of the various steps of the Saga.
 The proposed reference implementation for the LRA specification is the http://jbossts.blogspot.it/2017/12/narayana-lra-implementation-of-saga.html[Narayana LRA Coordinator].
 Users can follows instructions present on the Narayana website to *startup a remote instance of the coordinator*.
 
@@ -164,10 +164,10 @@ Once done, the Saga EIP can be directly used inside Camel routes and it will use
 == Examples
 
 Suppose you want to place a new order and you have two distinct services in your system: one managing the orders and one managing the credit.
-Logically you can place a order if you have enough credit for it.
+Logically you can place an order if you have enough credit for it.
 
 With the Saga EIP you can model the _direct:buy_ route as a Saga composed of two distinct actions, one to create the order and one to take the credit.
-*Both actions must be executed, or none of them*: a order placed without credit can be considered a inconsistent outcome (as well as a payment without an order).
+*Both actions must be executed, or none of them*: an order placed without credit can be considered an inconsistent outcome (as well as a payment without an order).
 
 [source,java]
 ----
@@ -230,7 +230,7 @@ It may happen that due to a delay in the execution of the _direct:newOrder_ rout
 
 So, when the compensating action _direct:cancelOrder_ is called, it may not find the Order record that should be cancelled.
 It is important, in order to guarantee full global consistency, that *any main action and its corresponding compensating action are commutative*,
-i.e. if compensation occurs before the main action it shoud have the same effect.
+i.e. if compensation occurs before the main action it should have the same effect.
 
 Another possible approach, when using a commutative behavior is not possible,
 is to consistently fail in the compensating action until data produced by the main action is found (or the maximum number of retries is exhausted):