fix: fix 'occured' -> 'occurred' in message_dispatch.go doc comment

[SAY-5]

Doc comment in courier/message_dispatch.go line 23 reads the error if any occured. Fixed to occurred. Comment-only change.

Summary by CodeRabbit

• Documentation
  • Corrected a spelling mistake in a code comment to improve clarity and accuracy of internal documentation. No behavioral or API changes were made.

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: cd17ed3d-9047-4735-bc5b-7f682ea30c67

📥 Commits

Reviewing files that changed from the base of the PR and between 5e3c223 and 4391872.

📒 Files selected for processing (1)

• courier/message_dispatch.go

✅ Files skipped from review due to trivial changes (1)

• courier/message_dispatch.go

---

📝 Walkthrough

Walkthrough

A spelling correction was made in a comment within MessageDispatch in courier/message_dispatch.go, changing "occured" to "occurred". No functional changes, logic modifications, or method signatures were affected.

Changes

Cohort / File(s)	Summary
Comment Correction courier/message_dispatch.go	Fixed spelling error in MessageDispatch comment: "occured" → "occurred".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and accurately summarizes the main change: fixing a spelling error in a documentation comment from 'occured' to 'occurred' in the message_dispatch.go file.
Description check	✅ Passed	The description is minimal but adequate for a simple documentation fix. It clearly states what was changed and why, though it does not follow the full template structure with related issues or checklist items.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}