fix docs_en description (#2161)

docs/pipeline_usage/tutorials/cv_pipelines/image_anomaly_detection_en.md

@@ -149,16 +149,16 @@ Below are the API references and multi-language service invocation examples:
 For all operations provided by the service:
 
 - Both the response body and the request body for POST requests are JSON data (JSON objects).
-- When the request is processed successfully, the response status code is `200`, and the response body attributes are as follows:
+- When the request is processed successfully, the response status code is `200`, and the response body properties are as follows:
 
     |Name|Type|Description|
     |-|-|-|
     |`errorCode`|`integer`|Error code. Fixed as `0`.|
     |`errorMsg`|`string`|Error message. Fixed as `"Success"`.|
 
-    The response body may also have a `result` attribute of type `object`, which stores the operation result information.
+    The response body may also have a `result` property of type `object`, which stores the operation result information.
 
-- When the request is not processed successfully, the response body attributes are as follows:
+- When the request is not processed successfully, the response body properties are as follows:
 
     |Name|Type|Description|
     |-|-|-|
@@ -173,13 +173,13 @@ Operations provided by the service:
 
     `POST /anomaly-detection`
 
-    - Request body attributes:
+    - Request body properties:
 
         |Name|Type|Description|Required|
         |-|-|-|-|
         |`image`|`string`|The URL of the image file accessible by the service or the Base64 encoded result of the image file content.|Yes|
 
-    - When the request is processed successfully, the `result` of the response body has the following attributes:
+    - When the request is processed successfully, the `result` of the response body has the following properties:
 
         |Name|Type|Description|
         |-|-|-|

docs/pipeline_usage/tutorials/cv_pipelines/image_classification_en.md

@@ -750,16 +750,16 @@ Below are the API references and multi-language service invocation examples:
 For all operations provided by the service:
 
 - Both the response body and the request body for POST requests are JSON data (JSON objects).
-- When the request is processed successfully, the response status code is `200`, and the response body attributes are as follows:
+- When the request is processed successfully, the response status code is `200`, and the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
     |`errorCode`|`integer`|Error code. Fixed as `0`.|
     |`errorMsg`|`string`|Error message. Fixed as `"Success"`.|
 
-    The response body may also have a `result` attribute of type `object`, which stores the operation result information.
+    The response body may also have a `result` property of type `object`, which stores the operation result information.
 
-- When the request is not processed successfully, the response body attributes are as follows:
+- When the request is not processed successfully, the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
@@ -774,27 +774,27 @@ Operations provided by the service are as follows:
 
     `POST /image-classification`
 
-    - The request body attributes are as follows:
+    - The request body properties are as follows:
 
         | Name | Type | Description | Required |
         |------|------|-------------|----------|
         |`image`|`string`|The URL of an image file accessible by the service or the Base64 encoded result of the image file content.|Yes|
         |`inferenceParams`|`object`|Inference parameters.|No|
 
-        The attributes of `inferenceParams` are as follows:
+        The properties of `inferenceParams` are as follows:
 
         | Name | Type | Description | Required |
         |------|------|-------------|----------|
         |`topK`|`integer`|Only the top `topK` categories with the highest scores will be retained in the results.|No|
 
-    - When the request is processed successfully, the `result` of the response body has the following attributes:
+    - When the request is processed successfully, the `result` of the response body has the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|
         |`categories`|`array`|Image category information.|
         |`image`|`string`|The image classification result image. The image is in JPEG format and encoded using Base64.|
 
-        Each element in `categories` is an `object` with the following attributes:
+        Each element in `categories` is an `object` with the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|

docs/pipeline_usage/tutorials/cv_pipelines/image_multi_label_classification_en.md

@@ -156,16 +156,16 @@ Below are the API references and multi-language service invocation examples:
 For all operations provided by the service:
 
 - Both the response body and the request body for POST requests are JSON data (JSON objects).
-- When the request is processed successfully, the response status code is `200`, and the response body attributes are as follows:
+- When the request is processed successfully, the response status code is `200`, and the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
     |`errorCode`|`integer`|Error code. Fixed to `0`.|
     |`errorMsg`|`string`|Error message. Fixed to `"Success"`.|
 
-    The response body may also have a `result` attribute of type `object`, which stores the operation result information.
+    The response body may also have a `result` property of type `object`, which stores the operation result information.
 
-- When the request is not processed successfully, the response body attributes are as follows:
+- When the request is not processed successfully, the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
@@ -180,27 +180,27 @@ Operations provided by the service are as follows:
 
     `POST /multilabel-image-classification`
 
-    - The request body attributes are as follows:
+    - The request body properties are as follows:
 
         | Name | Type | Description | Required |
         |------|------|-------------|----------|
         |`image`|`string`|The URL of the image file accessible by the service or the Base64 encoded result of the image file content.|Yes|
         |`inferenceParams`|`object`|Inference parameters.|No|
 
-        The attributes of `inferenceParams` are as follows:
+        The properties of `inferenceParams` are as follows:
 
         | Name | Type | Description | Required |
         |------|------|-------------|----------|
         |`topK`|`integer`|Only the top `topK` categories with the highest scores will be retained in the result.|No|
 
-    - When the request is processed successfully, the `result` of the response body has the following attributes:
+    - When the request is processed successfully, the `result` of the response body has the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|
         |`categories`|`array`|Image category information.|
         |`image`|`string`|Image classification result image. The image is in JPEG format and encoded in Base64.|
 
-        Each element in `categories` is an `object` with the following attributes:
+        Each element in `categories` is an `object` with the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|

docs/pipeline_usage/tutorials/cv_pipelines/instance_segmentation_en.md

@@ -178,16 +178,16 @@ Below are the API references and multi-language service invocation examples:
 For all operations provided by the service:
 
 - Both the response body and the request body for POST requests are JSON data (JSON objects).
-- When the request is processed successfully, the response status code is `200`, and the response body attributes are as follows:
+- When the request is processed successfully, the response status code is `200`, and the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
     |`errorCode`|`integer`|Error code. Fixed as `0`.|
     |`errorMsg`|`string`|Error message. Fixed as `"Success"`.|
 
-    The response body may also have a `result` attribute of type `object`, which stores the operation result information.
+    The response body may also have a `result` property of type `object`, which stores the operation result information.
 
-- When the request is not processed successfully, the response body attributes are as follows:
+- When the request is not processed successfully, the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
@@ -202,20 +202,20 @@ Operations provided by the service:
 
     `POST /instance-segmentation`
 
-    - The request body attributes are as follows:
+    - The request body properties are as follows:
 
         | Name | Type | Description | Required |
         |------|------|-------------|----------|
         |`image`|`string`|The URL of an image file accessible by the service or the Base64 encoded result of the image file content.|Yes|
 
-    - When the request is processed successfully, the `result` of the response body has the following attributes:
+    - When the request is processed successfully, the `result` of the response body has the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|
         |`instances`|`array`|Information about the locations and categories of instances.|
         |`image`|`string`|The result image of instance segmentation. The image is in JPEG format and encoded in Base64.|
 
-        Each element in `instances` is an `object` with the following attributes:
+        Each element in `instances` is an `object` with the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|
@@ -224,7 +224,7 @@ Operations provided by the service:
         |`score`|`number`|The score of the instance.|
         |`mask`|`object`|The segmentation mask of the instance.|
 
-        The attributes of `mask` are as follows:
+        The properties of `mask` are as follows:
 
         | Name | Type | Description |
         |------|------|-------------|

docs/pipeline_usage/tutorials/cv_pipelines/object_detection_en.md

@@ -465,16 +465,16 @@ Below are the API references and multi-language service invocation examples:
 For all operations provided by the service:
 
 - Both the response body and the request body for POST requests are JSON data (JSON objects).
-- When the request is processed successfully, the response status code is `200`, and the response body attributes are as follows:
+- When the request is processed successfully, the response status code is `200`, and the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
     | `errorCode` | `integer` | Error code. Fixed as `0`. |
     | `errorMsg` | `string` | Error description. Fixed as `"Success"`. |
 
-    The response body may also have a `result` attribute of type `object`, which stores the operation result information.
+    The response body may also have a `result` property of type `object`, which stores the operation result information.
 
-- When the request is not processed successfully, the response body attributes are as follows:
+- When the request is not processed successfully, the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
@@ -489,20 +489,20 @@ Operations provided by the service are as follows:
 
     `POST /object-detection`
 
-    - The request body attributes are as follows:
+    - The request body properties are as follows:
 
         | Name | Type | Description | Required |
         |------|------|-------------|----------|
         | `image` | `string` | The URL of an image file accessible by the service or the Base64 encoded result of the image file content. | Yes |
 
-    - When the request is processed successfully, the `result` of the response body has the following attributes:
+    - When the request is processed successfully, the `result` of the response body has the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|
         | `detectedObjects` | `array` | Information about the location and category of the detected objects. |
         | `image` | `string` | The image of the object detection result. The image is in JPEG format and encoded in Base64. |
 
-        Each element in `detectedObjects` is an `object` with the following attributes:
+        Each element in `detectedObjects` is an `object` with the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|

docs/pipeline_usage/tutorials/cv_pipelines/semantic_segmentation_en.md

@@ -184,16 +184,16 @@ Below are the API references and multi-language service invocation examples:
 For all operations provided by the service:
 
 - Both the response body and the request body for POST requests are JSON data (JSON objects).
-- When the request is processed successfully, the response status code is `200`, and the response body attributes are as follows:
+- When the request is processed successfully, the response status code is `200`, and the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
     |`errorCode`|`integer`|Error code. Fixed as `0`.|
     |`errorMsg`|`string`|Error description. Fixed as `"Success"`.|
 
-    The response body may also have a `result` attribute of type `object`, which stores the operation result information.
+    The response body may also have a `result` property of type `object`, which stores the operation result information.
 
-- When the request is not processed successfully, the response body attributes are as follows:
+- When the request is not processed successfully, the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
@@ -208,13 +208,13 @@ Operations provided by the service are as follows:
 
     `POST /semantic-segmentation`
 
-    - The request body attributes are as follows:
+    - The request body properties are as follows:
 
         | Name | Type | Description | Required |
         |------|------|-------------|----------|
         |`image`|`string`|The URL of an image file accessible by the service or the Base64 encoded result of the image file content.|Yes|
 
-    - When the request is processed successfully, the `result` of the response body has the following attributes:
+    - When the request is processed successfully, the `result` of the response body has the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|

docs/pipeline_usage/tutorials/cv_pipelines/small_object_detection_en.md

@@ -157,16 +157,16 @@ Below are the API references and multi-language service invocation examples:
 For all operations provided by the service:
 
 - Both the response body and the request body for POST requests are JSON data (JSON objects).
-- When the request is processed successfully, the response status code is `200`, and the response body attributes are as follows:
+- When the request is processed successfully, the response status code is `200`, and the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
     | `errorCode` | `integer` | Error code. Fixed as `0`. |
     | `errorMsg` | `string` | Error description. Fixed as `"Success"`. |
 
-    The response body may also have a `result` attribute of type `object`, which stores the operation result information.
+    The response body may also have a `result` property of type `object`, which stores the operation result information.
 
-- When the request is not processed successfully, the response body attributes are as follows:
+- When the request is not processed successfully, the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
@@ -181,20 +181,20 @@ Operations provided by the service are as follows:
 
     `POST /object-detection`
 
-    - The request body attributes are as follows:
+    - The request body properties are as follows:
 
         | Name | Type | Description | Required |
         |------|------|-------------|----------|
         | `image` | `string` | The URL of an image file accessible by the service or the Base64 encoded result of the image file content. | Yes |
 
-    - When the request is processed successfully, the `result` of the response body has the following attributes:
+    - When the request is processed successfully, the `result` of the response body has the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|
         | `detectedObjects` | `array` | Information about the location and category of the detected objects. |
         | `image` | `string` | The image of the object detection result. The image is in JPEG format and encoded in Base64. |
 
-        Each element in `detectedObjects` is an `object` with the following attributes:
+        Each element in `detectedObjects` is an `object` with the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|

docs/pipeline_usage/tutorials/information_extration_pipelines/document_scene_information_extraction_en.md

@@ -232,16 +232,16 @@ Below are the API references and multi-language service invocation examples:
 For all operations provided by the service:
 
 - Both the response body and the request body for POST requests are JSON data (JSON objects).
-- When the request is processed successfully, the response status code is `200`, and the response body attributes are as follows:
+- When the request is processed successfully, the response status code is `200`, and the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
     | `errorCode` | `integer` | Error code. Fixed as `0`. |
     | `errorMsg` | `string` | Error description. Fixed as `"Success"`. |
 
-    The response body may also have a `result` attribute of type `object`, which stores the operation result information.
+    The response body may also have a `result` property of type `object`, which stores the operation result information.
 
-- When the request is not processed successfully, the response body attributes are as follows:
+- When the request is not processed successfully, the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
@@ -256,12 +256,12 @@ Operations provided by the service are as follows:
 
     `POST /chatocr-vision`
 
-    - Request body attributes:
+    - Request body properties:
 
         | Name | Type | Description | Required |
         |------|------|-------------|----------|
         | `image` | `string` | The URL of an image file or PDF file accessible by the service, or the Base64 encoded result of the content of the above-mentioned file types. For PDF files with more than 10 pages, only the content of the first 10 pages will be used. | Yes |
-        | `fileType` | `integer` | File type. `0` indicates a PDF file, `1` indicates an image file. If this attribute is not present in the request body, the service will attempt to automatically infer the file type based on the URL. | No |
+        | `fileType` | `integer` | File type. `0` indicates a PDF file, `1` indicates an image file. If this property is not present in the request body, the service will attempt to automatically infer the file type based on the URL. | No |
         | `useOricls` | `boolean` | Whether to enable document image orientation classification. This feature is enabled by default. | No |
         | `useCurve` | `boolean` | Whether to enable seal text detection. This feature is enabled by default. | No |
         | `useUvdoc` | `boolean` | Whether to enable text image correction. This feature is enabled by default. | No |
@@ -273,14 +273,14 @@ Operations provided by the service are as follows:
         |------|------|-------------|----------|
         | `maxLongSide` | `integer` | During inference, if the length of the longer side of the input image for the text detection model is greater than `maxLongSide`, the image will be scaled so that the length of the longer side equals `maxLongSide`. | No |
 
-    - When the request is processed successfully, the `result` of the response body has the following attributes:
+    - When the request is processed successfully, the `result` of the response body has the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|
         | `visionResults` | `array` | Analysis results obtained using computer vision models. The array length is 1 (for image input) or the smaller of the number of document pages and 10 (for PDF input). For PDF input, each element in the array represents the processing result of each page in the PDF file. |
         | `visionInfo` | `object` | Key information in the image, which can be used as input for other operations. |
 
-        Each element in `visionResults` is an `object` with the following attributes:
+        Each element in `visionResults` is an `object` with the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|
@@ -290,7 +290,7 @@ Operations provided by the service are as follows:
         | `ocrImage` | `string` | OCR result image. The image is in JPEG format and encoded using Base64. |
         | `layoutImage` | `string` | Layout area detection result image. The image is in JPEG format and encoded using Base64. |
 
-        Each element in `texts` is an `object` with the following attributes:
+        Each element in `texts` is an `object` with the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|
@@ -301,7 +301,7 @@ Interact with large language models to extract key information.
 
 `POST /chatocr-vision`
 
-- Request body attributes:
+- Request body properties:
 
     | Name | Type | Description | Required |
     |------|------|-------------|----------|
@@ -327,7 +327,7 @@ Interact with large language models to extract key information.
     }
     ```
 
-- On successful request processing, the `result` in the response body has the following attributes:
+- On successful request processing, the `result` in the response body has the following properties:
 
     | Name | Type | Description |
     |------|------|-------------|

docs/pipeline_usage/tutorials/ocr_pipelines/OCR_en.md

@@ -209,16 +209,16 @@ Below are the API references and multi-language service invocation examples:
 For all operations provided by the service:
 
 - Both the response body and the request body for POST requests are JSON data (JSON objects).
-- When the request is processed successfully, the response status code is `200`, and the response body attributes are as follows:
+- When the request is processed successfully, the response status code is `200`, and the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
     |`errorCode`|`integer`|Error code. Fixed as `0`.|
     |`errorMsg`|`string`|Error description. Fixed as `"Success"`.|
 
-    The response body may also have a `result` attribute of type `object`, which stores the operation result information.
+    The response body may also have a `result` property of type `object`, which stores the operation result information.
 
-- When the request is not processed successfully, the response body attributes are as follows:
+- When the request is not processed successfully, the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
@@ -233,7 +233,7 @@ Operations provided by the service:
 
     `POST /ocr`
 
-    - Request body attributes:
+    - Request body properties:
 
         | Name | Type | Description | Required |
         |------|------|-------------|----------|
@@ -246,14 +246,14 @@ Operations provided by the service:
         |------|------|-------------|----------|
         |`maxLongSide`|`integer`|During inference, if the length of the longer side of the input image for the text detection model is greater than `maxLongSide`, the image will be scaled so that the length of the longer side equals `maxLongSide`.|No|
 
-    - When the request is processed successfully, the `result` in the response body has the following attributes:
+    - When the request is processed successfully, the `result` in the response body has the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|
         |`texts`|`array`|Positions, contents, and scores of texts.|
         |`image`|`string`|OCR result image with detected text positions annotated. The image is in JPEG format and encoded in Base64.|
 
-        Each element in `texts` is an `object` with the following attributes:
+        Each element in `texts` is an `object` with the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|

docs/pipeline_usage/tutorials/ocr_pipelines/table_recognition_en.md

@@ -208,16 +208,16 @@ Below are the API references and multi-language service invocation examples:
 For all operations provided by the service:
 
 - Both the response body and the request body for POST requests are JSON data (JSON objects).
-- When the request is processed successfully, the response status code is `200`, and the response body attributes are as follows:
+- When the request is processed successfully, the response status code is `200`, and the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
     |`errorCode`|`integer`|Error code. Fixed as `0`.|
     |`errorMsg`|`string`|Error message. Fixed as `"Success"`.|
 
-    The response body may also have a `result` attribute of type `object`, which stores the operation result information.
+    The response body may also have a `result` property of type `object`, which stores the operation result information.
 
-- When the request is not processed successfully, the response body attributes are as follows:
+- When the request is not processed successfully, the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
@@ -232,7 +232,7 @@ Operations provided by the service:
 
     `POST /table-recognition`
 
-    - Request body attributes:
+    - Request body properties:
 
         | Name | Type | Description | Required |
         |------|------|-------------|----------|
@@ -245,7 +245,7 @@ Operations provided by the service:
         |------|------|-------------|----------|
         |`maxLongSide`|`integer`|During inference, if the length of the longer side of the input image for the text detection model is greater than `maxLongSide`, the image will be scaled so that the length of the longer side equals `maxLongSide`.|No|
 
-    - When the request is processed successfully, the `result` of the response body has the following attributes:
+    - When the request is processed successfully, the `result` of the response body has the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|
@@ -253,7 +253,7 @@ Operations provided by the service:
         |`layoutImage`|`string`|Layout area detection result image. The image is in JPEG format and encoded using Base64.|
         |`ocrImage`|`string`|OCR result image. The image is in JPEG format and encoded using Base64.|
 
-        Each element in `tables` is an `object` with the following attributes:
+        Each element in `tables` is an `object` with the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|

docs/pipeline_usage/tutorials/time_series_pipelines/time_series_anomaly_detection_en.md

@@ -173,16 +173,16 @@ Below are the API references and multi-language service invocation examples:
 For all operations provided by the service:
 
 - Both the response body and the request body for POST requests are JSON data (JSON objects).
-- When the request is processed successfully, the response status code is `200`, and the attributes of the response body are as follows:
+- When the request is processed successfully, the response status code is `200`, and the properties of the response body are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
     |`errorCode`|`integer`|Error code. Fixed as `0`.|
     |`errorMsg`|`string`|Error description. Fixed as `"Success"`.|
 
-    The response body may also have a `result` attribute of type `object`, which stores the operation result information.
+    The response body may also have a `result` property of type `object`, which stores the operation result information.
 
-- When the request is not processed successfully, the attributes of the response body are as follows:
+- When the request is not processed successfully, the properties of the response body are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
@@ -203,7 +203,7 @@ Operations provided by the service:
         |------|------|-------------|----------|
         |`csv`|`string`|The URL of a CSV file accessible by the service or the Base64 encoded result of the CSV file content. The CSV file must be encoded in UTF-8.|Yes|
 
-    - When the request is processed successfully, the `result` of the response body has the following attributes:
+    - When the request is processed successfully, the `result` of the response body has the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|

docs/pipeline_usage/tutorials/time_series_pipelines/time_series_classification_en.md

@@ -163,16 +163,16 @@ Below are the API references and multi-language service invocation examples:
 For all operations provided by the service:
 
 - Both the response body and the request body for POST requests are JSON data (JSON objects).
-- When the request is processed successfully, the response status code is `200`, and the response body attributes are as follows:
+- When the request is processed successfully, the response status code is `200`, and the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
     |`errorCode`|`integer`|Error code. Fixed as `0`.|
     |`errorMsg`|`string`|Error message. Fixed as `"Success"`.|
 
-    The response body may also have a `result` attribute of type `object`, which stores the operation result information.
+    The response body may also have a `result` property of type `object`, which stores the operation result information.
 
-- When the request is not processed successfully, the response body attributes are as follows:
+- When the request is not processed successfully, the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
@@ -187,13 +187,13 @@ Operations provided by the service:
 
     `POST /time-series-classification`
 
-    - The request body attributes are as follows:
+    - The request body properties are as follows:
 
         | Name | Type | Description | Required |
         |------|------|-------------|----------|
         |`csv`|`string`|The URL of a CSV file accessible by the service or the Base64 encoded result of the CSV file content. The CSV file must be encoded in UTF-8.|Yes|
 
-    - When the request is processed successfully, the `result` in the response body has the following attributes:
+    - When the request is processed successfully, the `result` in the response body has the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|

docs/pipeline_usage/tutorials/time_series_pipelines/time_series_forecasting_en.md

@@ -174,16 +174,16 @@ Below are the API references and multi-language service invocation examples:
 For all operations provided by the service:
 
 - Both the response body and the request body for POST requests are JSON data (JSON objects).
-- When the request is processed successfully, the response status code is `200`, and the response body attributes are as follows:
+- When the request is processed successfully, the response status code is `200`, and the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
     |`errorCode`|`integer`|Error code. Fixed as `0`.|
     |`errorMsg`|`string`|Error message. Fixed as `"Success"`.|
 
-    The response body may also have a `result` attribute of type `object`, which stores the operation result information.
+    The response body may also have a `result` property of type `object`, which stores the operation result information.
 
-- When the request is not processed successfully, the response body attributes are as follows:
+- When the request is not processed successfully, the response body properties are as follows:
 
     | Name | Type | Description |
     |------|------|-------------|
@@ -198,13 +198,13 @@ Operations provided by the service are as follows:
 
     `POST /time-series-forecasting`
 
-    - The request body attributes are as follows:
+    - The request body properties are as follows:
 
         | Name | Type | Description | Required |
         |------|------|-------------|----------|
         |`csv`|`string`|The URL of a CSV file accessible by the service or the Base64 encoded result of the CSV file content. The CSV file must be encoded in UTF-8.|Yes|
 
-    - When the request is processed successfully, the `result` of the response body has the following attributes:
+    - When the request is processed successfully, the `result` of the response body has the following properties:
 
         | Name | Type | Description |
         |------|------|-------------|