Update overview.md

docs/constraints/overview.md

@@ -14,6 +14,6 @@ The determinism and idempotency constraints for workflows and activities are imp
 
 The determinism and idempotency constraints are necessary because the workflow engine may need to replay the same event multiple times. If the code that is executed during the replay is not deterministic, it may produce different results each time it is run. This would cause the workflow engine to lose track of the current state of the workflow, leading to incorrect results.
 
-Additionally, since the events may be replayed multiple times, it is important that the code within an activity is idempotent. This means that running the code multiple times with the same input should produce the same result. If the code is not idempotent, it may produce unintended side effects when it is replayed.
+Additionally, since the events may be replayed multiple times, it is important that the code within an activity is idempotent. This means that running the code multiple times with the same input should produce the same result as simply running it once. If the code is not idempotent, it may produce unintended side effects when it is replayed.
 
 Overall, the determinism and idempotency constraints help ensure that the workflow engine is able to accurately rebuild the current state of the workflow from the event stream and produce the correct results. They also make it easier to debug and troubleshoot problems, as the system always behaves in a predictable and repeatable way.