simulation: remove obsolete comments, fix typos

product/ERP5/bootstrap/erp5_core/DocumentTemplateItem/portal_components/document.erp5.SimulationMovement.py

@@ -82,22 +82,6 @@ class SimulationMovement(PropertyRecordableMixin, Movement, ExplainableMixin):
 
       - delivered (the movement is now archived in a delivery)
 
-      The simulation worklow uses some variables, which are
-      set by the template
-
-      - is_order_required
-
-      - is_delivery_required
-
-
-      XX
-      - is_problem_checking_required ?
-
-      Other flag
-      (forzen flag)
-
-      NEW: we do not use DCWorklow so that the simulation process
-      can be as much as possible independent of a Zope / CMF implementation.
   """
   meta_type = 'ERP5 Simulation Movement'
   portal_type = 'Simulation Movement'

product/ERP5/bootstrap/erp5_core/InterfaceTemplateItem/portal_components/interface.erp5.IRule.py

@@ -41,7 +41,7 @@ class IRule(IMovementCollectionUpdater):
     """
     Create a new applied rule in the context.
 
-    An applied rule is an instanciation of a Rule. The applied rule is
+    An applied rule is an instantiation of a Rule. The applied rule is
     linked to the Rule through the `specialise` relation.
 
     context -- usually, a parent simulation movement of the
@@ -56,7 +56,7 @@ class IRule(IMovementCollectionUpdater):
     applied rule.
 
     At expand time, we must replace or compensate certain
-    properties. However, if some properties were overwriten
+    properties. However, if some properties were overwritten
     by a decision (ie. a resource if changed), then we
     should not try to compensate such a decision. The principles
     of compensation are implemented through

product/ERP5/bootstrap/erp5_core/MixinTemplateItem/portal_components/mixin.erp5.RuleMixin.py

@@ -108,7 +108,7 @@ class RuleMixin(Predicate):
     policy_dict[expand_policy](**kw).expand(self, applied_rule)
 
   def _expandNow(self, maybe_expand, applied_rule):
-    # Update moveme-nts
+    # Update movements
     #  NOTE-JPS: it is OK to make rounding a standard parameter of rules
     #            although rounding in simulation is not recommended at all
     self.updateMovementCollection(applied_rule,