better comment

designer/client/src/components/modals/CalculateCounts/useActivityHistory.ts

@@ -21,9 +21,13 @@ function displayableNameOfPredefinedActivityType(predefinedActivityType: Activit
     }
 }
 /*
-  Since information about deployment does not convey much information (such a process will not run immediately after deployment action)
-   in the context of count ranges we need to exclude them before we start computing count's ranges. The `Cancel` activity type is important
-   while resolving these ranges but is not important for the end user so it is also filtered at the end (thanks to `isOmitted` variable)
+   In the context of batch processing, the information about a performed deployment does not provide meaningful insights for range calculations.
+   This is because batch processes do not execute immediately after a deployment action. To address this, deployment-related activities
+   (of type `ScenarioDeployed`) are excluded when computing ranges for batch processes.
+
+   Additionally, the `Cancel` activity type (`ScenarioCanceled`) plays a role in determining count ranges during internal processing,
+   but it is not relevant to the end user. As a result, activities with this type are filtered out at the end of the computation process
+   (handled using the `isOmitted` variable).
  */
 export function useActivityHistory(processName: string, processingMode: string): Range[] {
     const { t } = useTranslation();