further fixes of waitForFinish

Author: TC-MO

apify-api/openapi/paths/actor-runs/actor-runs@{runId}.yaml

@@ -88,7 +88,7 @@ get:
         The maximum number of seconds the server waits for the run to finish. By
         default it is `0`, the maximum value is `60`. <!--
         MAX_ACTOR_JOB_ASYNC_WAIT_SECS -->
-        If the build finishes in time then the returned run object will have a terminal status (e.g. `SUCCEEDED`),
+        If the run finishes in time then the returned run object will have a terminal status (e.g. `SUCCEEDED`),
         otherwise it will have a transitional status (e.g. `RUNNING`).
       style: form
       explode: true

apify-api/openapi/paths/actor-tasks/actor-tasks@{actorTaskId}@runs.yaml

@@ -231,7 +231,7 @@ post:
       description: |
         The maximum number of seconds the server waits for the run to finish. By
         default, it is `0`, the maximum value is `60`. <!-- MAX_ACTOR_JOB_ASYNC_WAIT_SECS -->
-        If the build finishes in time then the returned run object will have a
+        If the run finishes in time then the returned run object will have a
         terminal status (e.g. `SUCCEEDED`),
         otherwise it will have a transitional status (e.g. `RUNNING`).
       style: form

apify-api/openapi/paths/actors/acts@{actorId}@runs@{runId}.yaml

@@ -38,7 +38,7 @@ get:
       description: |
         The maximum number of seconds the server waits for the run to finish. By
         default it is `0`, the maximum value is `60`. <!-- MAX_ACTOR_JOB_ASYNC_WAIT_SECS -->
-        If the build finishes in time then the returned run object will have a terminal status (e.g. `SUCCEEDED`),
+        If the run finishes in time then the returned run object will have a terminal status (e.g. `SUCCEEDED`),
         otherwise it will have a transitional status (e.g. `RUNNING`).
       style: form
       explode: true