Clarify resume functionality after transient issues

Updated the description to clarify that the resume functionality now survives transient issues, not just database outages.

Author: matt-aitken

.changeset/resume-retry-transient-db.md

@@ -2,4 +2,4 @@
 "@trigger.dev/core": patch
 ---
 
-Runs resuming after a wait now survive a transient platform database outage instead of failing with `TASK_EXECUTION_ABORTED`. The worker retries the resume call generously with jittered backoff, so a brief blip while the run is being continued no longer aborts it.
+Runs resuming after a wait now survive a transient issue instead of failing with `TASK_EXECUTION_ABORTED`. The worker retries the resume call generously with jittered backoff, so a brief blip while the run is being continued no longer aborts it.