refactor: imrpoved documentation text

Author: danpoletaev

apify-api/openapi/paths/actors/acts@{actorId}@[email protected]

@@ -3,13 +3,13 @@ get:
     - Actors/Default build object
   summary: Get default build
   description: |
-    By passing the optional `waitForFinish` parameter the API endpoint will
-    synchronously wait for the build to finish.
-    This is useful to avoid periodic polling when waiting for an Actor build to
-    finish.
+    Get the default build for an Actor. 
+    
+    Use the optional `waitForFinish` parameter to synchronously wait for the build to finish. 
+    This avoids the need for periodic polling when waiting for the build to complete.
 
-    This endpoint does not require the authentication token. Instead, calls are authenticated using a hard-to-guess ID of the build. However,
-    if you access the endpoint without the token, certain attributes, such as `usageUsd` and `usageTotalUsd`, will be hidden.
+    This endpoint does not require an authentication token. Instead, calls are authenticated using the build's unique ID.
+    However, if you access the endpoint without a token, certain attributes (e.g., `usageUsd` and `usageTotalUsd`) will be hidden.
   operationId: act_build_default_get
   security:
     - apiKeyActorBuilds: []
@@ -27,9 +27,10 @@ get:
       in: query
       description: |
         The maximum number of seconds the server waits for the build 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 build object will have a terminal status (e.g. `SUCCEEDED`),
+        If the build finishes within this time, the returned build object will have a terminal status (e.g. `SUCCEEDED`),
         otherwise it will have a transitional status (e.g. `RUNNING`).
+        
+        By default it is `0`, the maximum value is `60`. <!-- MAX_ACTOR_JOB_ASYNC_WAIT_SECS -->
       style: form
       explode: true
       schema: