Contributed a documentation update to the amperity/amperity-docs repository, focusing on clarifying the behavior of Journey Workflow Alerts. The work detailed the specific conditions under which alerts are triggered, including failures, cancellations, successful completions, and runtime threshold breaches, while explicitly noting that alerts for individual journeys are limited to failure notifications. This approach reduced ambiguity for both users and operators, supporting more effective incident response and operational transparency. The update was implemented using reStructuredText (RST) and leveraged strong documentation skills to ensure technical accuracy and clarity. No bugs were addressed during this period, with efforts concentrated solely on feature documentation.