docs(agentic-ai): Apply review suggestions

Co-authored-by: Angel Fernandez <[email protected]>

Author: maff

docs/components/connectors/out-of-the-box-connectors/agentic-ai/aiagent/configuration/_error-codes-task.md

@@ -1,7 +1,7 @@
-The AI Agent Task emits the following error codes when generating the tools schema from the process definition XML:
+The AI Agent Task generates the following error codes when creating the tool schema from the process definition XML:
 
 | Error code                           | Description                                                                                              |
 | :----------------------------------- | :------------------------------------------------------------------------------------------------------- |
 | `AD_HOC_SUB_PROCESS_XML_FETCH_ERROR` | The process definition XML could not be fetched.                                                         |
 | `AD_HOC_SUB_PROCESS_NOT_FOUND`       | The ad-hoc sub-process with the configured ID could not be found in the process definition XML.          |
-| `AD_HOC_TOOL_DEFINITION_INVALID`     | The ad-hoc sub-process contains invalid tool definitions which can't be transformed into a tools schema. |
+| `AD_HOC_TOOL_DEFINITION_INVALID`     | The ad-hoc sub-process contains invalid tool definitions which can't be transformed into a tool schema. |

docs/components/connectors/out-of-the-box-connectors/agentic-ai/aiagent/configuration/_error-handling.md

@@ -8,15 +8,15 @@ If an error occurs, the AI Agent connector throws an error and includes the erro
 | :--------------- | :------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Error expression | No       | You can handle an AI Agent connector error using an Error Boundary Event and [error expressions](/components/connectors/use-connectors/index.md#error-expression). |
 
-In the error expression, you can handle the following error codes emitted by the AI Agent connector to react on specific situations. For example, you can map a specific error code to a BPMN error and model
+In the error expression, you can handle the following error codes emitted by the AI Agent connector to respond to specific situations. For example, you can map a specific error code to a BPMN error and model
 your process accordingly.
 
 | Error code                              | Description                                                                                                                                    |
 | :-------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------- |
 | `FAILED_MODEL_CALL`                     | The call to the LLM API failed, for example due to misconfiguration or wrong credentials. The error message contains additional details.       |
 | `FAILED_TO_PARSE_RESPONSE_CONTENT`      | The AI Agent was configured to parse the LLM response as JSON, but the parsing failed.                                                         |
 | `MAXIMUM_NUMBER_OF_MODEL_CALLS_REACHED` | The AI Agent reached the maximum number of configured model calls.                                                                             |
-| `NO_USER_MESSAGE_CONTENT`               | Indicates that no user messages content - either coming from a user prompt or a document - was provided to the agent.                          |
-| `TOOL_CALL_RESULTS_ON_EMPTY_CONTEXT`    | Tool call results were passed to the AI Agent despite the context being empty. This typically indicates misconfiguration of the agent context. |
+| `NO_USER_MESSAGE_CONTENT`               | Indicates that no user message content, either from a user prompt or a document, was provided to the agent.                  |
+| `TOOL_CALL_RESULTS_ON_EMPTY_CONTEXT`    | Tool call results were passed to the AI Agent despite the context being empty, which typically indicates a misconfiguration of the agent context. |
 
 {props.type === "task" && <ConfigurationErrorCodesTask />}

versioned_docs/version-8.8/components/connectors/out-of-the-box-connectors/agentic-ai/aiagent/configuration/_error-codes-task.md

@@ -1,7 +1,7 @@
-The AI Agent Task emits the following error codes when generating the tools schema from the process definition XML:
+The AI Agent Task generates the following error codes when creating the tool schema from the process definition XML:
 
 | Error code                           | Description                                                                                              |
 | :----------------------------------- | :------------------------------------------------------------------------------------------------------- |
 | `AD_HOC_SUB_PROCESS_XML_FETCH_ERROR` | The process definition XML could not be fetched.                                                         |
 | `AD_HOC_SUB_PROCESS_NOT_FOUND`       | The ad-hoc sub-process with the configured ID could not be found in the process definition XML.          |
-| `AD_HOC_TOOL_DEFINITION_INVALID`     | The ad-hoc sub-process contains invalid tool definitions which can't be transformed into a tools schema. |
+| `AD_HOC_TOOL_DEFINITION_INVALID`     | The ad-hoc sub-process contains invalid tool definitions which can't be transformed into a tool schema. |

versioned_docs/version-8.8/components/connectors/out-of-the-box-connectors/agentic-ai/aiagent/configuration/_error-handling.md

@@ -8,14 +8,14 @@ If an error occurs, the AI Agent connector throws an error and includes the erro
 | :--------------- | :------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Error expression | No       | You can handle an AI Agent connector error using an Error Boundary Event and [error expressions](/components/connectors/use-connectors/index.md#error-expression). |
 
-In the error expression, you can handle the following error codes emitted by the AI Agent connector to react on specific situations. For example, you can map a specific error code to a BPMN error and model
+In the error expression, you can handle the following error codes emitted by the AI Agent connector to respond to specific situations. For example, you can map a specific error code to a BPMN error and model
 your process accordingly.
 
 | Error code                              | Description                                                                                                                                    |
 | :-------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------- |
 | `FAILED_TO_PARSE_RESPONSE_CONTENT`      | The AI Agent was configured to parse the LLM response as JSON, but the parsing failed.                                                         |
 | `MAXIMUM_NUMBER_OF_MODEL_CALLS_REACHED` | The AI Agent reached the maximum number of configured model calls.                                                                             |
-| `NO_USER_MESSAGE_CONTENT`               | Indicates that no user messages content - either coming from a user prompt or a document - was provided to the agent.                          |
-| `TOOL_CALL_RESULTS_ON_EMPTY_CONTEXT`    | Tool call results were passed to the AI Agent despite the context being empty. This typically indicates misconfiguration of the agent context. |
+| `NO_USER_MESSAGE_CONTENT`               | Indicates that no user message content, either from a user prompt or a document, was provided to the agent.                         |
+| `TOOL_CALL_RESULTS_ON_EMPTY_CONTEXT`    | Tool call results were passed to the AI Agent despite the context being empty, which typically indicates a misconfiguration of the agent context. |
 
 {props.type === "task" && <ConfigurationErrorCodesTask />}