Update content/terraform-docs-common/docs/cloud-docs/api-docs/run-tasks/run-tasks-integration.mdx

Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>

Author: glennsarti

content/terraform-docs-common/docs/cloud-docs/api-docs/run-tasks/run-tasks-integration.mdx

@@ -138,7 +138,7 @@ The POST request submits the following properties as the request headers.
 While a run task runs, it should send progressive updates to HCP Terraform with a `running` status.
 Once an integrator determines that Terraform supports detailed run task outcomes, they can send these outcomes by appending to the run task's callback payload.
 
--> **Note:** HCP Terraform will consider the request as errored if it has not received a progress update in the last 10 minutes, or the request has been running for over 60 minutes.
+The request errors if  HCP Terraform does not receive a progress update within 10 minutes or if the request runs for more than 60 minutes.
 
 Once the external integration fulfills the request, that integration must call back into HCP Terraform with the overall result of either `passed` or `failed`.
 You can send outcomes with a status of `running`, `passed`, or `failed`, but it is a good practice only to send outcomes when a run task is `running`.