[hotfix][docs] Make timeout param of async i/o more clearer

docs/content.zh/docs/dev/datastream/operators/asyncio.md

@@ -137,7 +137,8 @@ DataStream<Tuple2<String, String>> resultStream =
 
 下面两个参数控制异步操作：
 
-  - **Timeout**： 超时参数定义了异步操作执行多久未完成、最终认定为失败的时长，如果启用重试，则可能包括多个重试请求。 它可以防止一直等待得不到响应的请求。
+  - **Timeout**： 超时定义了从首次调用到异步操作最终完成的最大持续时间。
+    此持续时间可能包括多次重试尝试（如果启用了重试）并确定操作最终被视为失败的时间点。 它可以防止一直等待得不到响应的请求。
 
   - **Capacity**： 容量参数定义了可以同时进行的异步请求数。
     即使异步 I/O 通常带来更高的吞吐量，执行异步 I/O 操作的算子仍然可能成为流处理的瓶颈。 限制并发请求的数量可以确保算子不会持续累积待处理的请求进而造成积压，而是在容量耗尽时触发反压。

docs/content/docs/dev/datastream/operators/asyncio.md

@@ -152,8 +152,9 @@ All subsequent `complete` calls will be ignored.
 
 The following three parameters control the asynchronous operations:
 
-  - **Timeout**: The timeout defines how long an asynchronous operation take before it is finally considered failed,
-    may include multiple retry requests if retry enabled. This parameter guards against dead/failed requests.
+  - **Timeout**: The timeout defines the maximum duration from the first invocation to the final completion of an asynchronous operation,
+    This duration may include multiple retry attempts (if retries are enabled) and determines when the operation is ultimately considered complete.
+    This parameter guards against dead/failed requests.
 
   - **Capacity**: This parameter defines how many asynchronous requests may be in progress at the same time.
     Even though the async I/O approach leads typically to much better throughput, the operator can still be the bottleneck in