Typo Tyranny Toppled: Coding Clarity Restored!

Developers Rejoice as Path Updates and Spelling Corrections Propel Project Toward Perfection!

Commit Details:

fix: typo corrections and path updates (#2415) ## Why is this change needed? Typographical errors in variable names, comments, and documentation, such as "recieved" instead of "received" and incorrect paths in examples, have been corrected to ensure clarity, consistency, and improved developer experience. ### Key Changes: 1. Replaced all instances of "recievedMessages" with "receivedMessages" for correct spelling. 2. Updated code comments and logs to reflect the corrected spelling: - `recievedMessages.size` → `receivedMessages.size` - Comments updated for clarity: "recieved" → "received." 3. Corrected a typo in error logging: `errMessaeg` → `errMessage`. 4. Fixed a typo in a code comment within `shuttle/index.ts`: - "gurantees" → "guarantees." - "recieved" → "received." ## Merge Checklist _Choose all relevant options below by adding an `x` now or at any time before submitting for review:_ - [x] PR title adheres to the [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/) standard. - [x] PR has a [changeset](https://github.com/farcasterxyz/hub-monorepo/blob/main/CONTRIBUTING.md#35-adding-changesets). - [x] PR has been tagged with a change label(s) (i.e., documentation, feature, bugfix, or chore). - [ ] PR includes [documentation](https://github.com/farcasterxyz/hub-monorepo/blob/main/CONTRIBUTING.md#32-writing-docs) if necessary. <!-- start pr-codex --> --- ## PR-Codex overview This PR focuses on correcting spelling errors related to the word "received" across multiple files, enhancing code clarity and consistency. ### Detailed summary - Fixed spelling of `errMessaeg` to `errMessage` in `dbSnapshotBackupJob.ts`. - Corrected comments and variable names from `recievedMessages` to `receivedMessages` in `gossipProfileWorker.ts` and `gossipProfileWorker.js`. - Updated console log messages for consistency in spelling. > ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}` <!-- end pr-codex -->