From 1c42b57cefbdb14dac78949319fd7118b0ded452 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=A9rome=20Perrin?= <jerome@nexedi.com>
Date: Fri, 11 Mar 2011 13:57:22 +0000
Subject: [PATCH] fix a few typos

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@44183 20353a03-c40f-0410-a6d1-a30d3c3de9de
---
 product/ERP5/mixin/rule.py | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/product/ERP5/mixin/rule.py b/product/ERP5/mixin/rule.py
index 2959ce5915..3a447fa550 100644
--- a/product/ERP5/mixin/rule.py
+++ b/product/ERP5/mixin/rule.py
@@ -200,7 +200,7 @@ class RuleMixin(Predicate):
 
     At expand time, we must replace or compensate certain
     properties. However, if some properties were overwritten
-    by a decision (ie. a resource if changed), then we
+    by a decision (ie. a resource is changed), then we
     should not try to compensate such a decision.
     """
     # Update movements
@@ -352,7 +352,7 @@ class RuleMixin(Predicate):
     decision_movement.
 
     TODO:
-       - is this asumption appropriate ?
+       - is this assumption appropriate ?
     """
     # Sample implementation - but it actually looks very generic
     # Case 1: movements which are not needed
@@ -436,7 +436,7 @@ class RuleMixin(Predicate):
           # Not Frozen can be updated
           kw = {}
           for tester in updating_tester_list:
-            if not tester.compare(prevision_movement, decision_movement): 
+            if not tester.compare(prevision_movement, decision_movement):
               # Only update those updatable properties which are not recorded
               kw_candidate = tester.getUpdatablePropertyDict(prevision_movement,
                                                              decision_movement)
@@ -445,7 +445,7 @@ class RuleMixin(Predicate):
                 if decision_movement.isPropertyRecorded(property_key):
                   del kw_candidate[property_key]
               kw.update(kw_candidate)
-              # XXX-JPS - there is a risk here that quanity is wrongly updated
+              # XXX-JPS - there is a risk here that quantity is wrongly updated
           if kw:
             movement_collection_diff.addUpdatableMovement(decision_movement, kw)
     # Second, we calculate if the total quantity is the same on both sides
@@ -471,3 +471,4 @@ class RuleMixin(Predicate):
         # We must create a profit and loss movement
         new_movement = self._newProfitAndLossMovement(prevision_movement)
         movement_collection_diff.addNewMovement(new_movement)
+
-- 
2.30.9