Skip to content

Commit 19ca461

Browse files
authored
Fix grammar (#277)
1 parent 707ad6c commit 19ca461

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

docs/en/RuleEngine_en.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ Back to our example of a simple purchasing system: some business Rules should be
5656
calculate the final price, probably calculating the tax first, and then the discount. If both the tax and
5757
discount are known, we can show the price.
5858

59-
Let's specify some Rules (in psuedocode).
59+
Let's specify some Rules (in pseudocode).
6060

6161
```text
6262
Rule 1
@@ -114,8 +114,8 @@ Rule 7
114114
with given Tax and Discount
115115
```
116116

117-
If you examine the above Rules, you should easily understand the of **Rule** concept for Rule Engines.
118-
These collection of rules will form a set of **Knowledge**. In this case, they form a Knowledge set of
117+
If you examine the above Rules, you should easily understand the **Rule** concept for Rule Engines.
118+
These collections of rules will form a set of **Knowledge**. In this case, they form a Knowledge set of
119119
**"how to calculate Item's final price"**.
120120

121121
## Cycle
@@ -133,8 +133,8 @@ That depends on the contents of the conflict set:
133133
* If there are multiple Rules in the Conflict Set, the engine must apply a strategy to prioritize one Rule and execute its action.
134134

135135
If an action gets executed, the cycle repeats again, as long as there's an action that needs execution.
136-
When no more actions get executed, this indicates that there are no more Rules that are statisfied
137-
by the fact (no more matching **IF** statements), and the cycle stops, letting the Rule engine finish evalutation.
136+
When no more actions get executed, this indicates that there are no more Rules that are satisfied
137+
by the fact (no more matching **IF** statements), and the cycle stops, letting the Rule engine finish evaluation.
138138

139139
The pseudocode for this conflict resolution strategy is depicted below:
140140

@@ -172,11 +172,11 @@ an error will be returned.
172172

173173
As explained above, the Rule engine will evaluate all Rules' requirements and add
174174
them into a list of conflicting Rules called the **Conflict Set**. If only one Rule is
175-
inside the list, it means that are no Rule(s) conflicting with that noe Rule. The engine
175+
inside the list, it means that there are no Rule(s) conflicting with that one Rule. The engine
176176
will immediately execute the Rule's action.
177177

178-
If there are multiple Rules inside the set, there maybe conflicts. There are many conflict resolution
179-
strategies that can be implemented for this type of Ruel conflict resolution. The easiest way to resolve
178+
If there are multiple Rules inside the set, there may be conflicts. There are many conflict resolution
179+
strategies that can be implemented for this type of Rule conflict resolution. The easiest way to resolve
180180
is through specification of a Rule's **salience** (also known as **priority** or **importance**).
181181
We can add an indicator of Rule **salience** or importance into a Rule definition like in the pseudocode below:
182182

0 commit comments

Comments
 (0)