Fix typos

[Hack666r]

Description

Fixes typos in the following files:

• README.md: Corrected a small typo in the description of the blocks exchange process.
• messagequeue.go: Fixed a typo in a comment describing timeout behavior in the message queue.

Motivation and Context

These changes are intended to improve the clarity and accuracy of comments and documentation. Correcting minor typos helps make the code more readable and maintainable for future contributors.

How Has This Been Tested?

There were no code changes; only comments and documentation were updated. I have verified the changes locally by reviewing the modified files.

Types of Changes

• Documentation (fix typo in comments and README)

Checklist:

• My code follows the style guidelines of this project
• I have updated the documentation accordingly
• I have read the contributing guidelines
• I have created a new branch for my changes

Additional Notes

I would love to contribute more to this project and would be excited to become an active member of your team. Let me know if there are other areas where I can assist.

[welcome]

Thank you for submitting this PR!
A maintainer will be here shortly to review it.
We are super grateful, but we are also overloaded! Help us by making sure that:

• The context for this PR is clear, with relevant discussion, decisions
  and stakeholders linked/mentioned.

• Your contribution itself is clear (code comments, self-review for the
  rest) and in its best form. Follow the code contribution
  guidelines
  if they apply.

Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment.
Next steps:

• A maintainer will triage and assign priority to this PR, commenting on
  any missing things and potentially assigning a reviewer for high
  priority items.

• The PR gets reviews, discussed and approvals as needed.

• The PR is merged by maintainers when it has been approved and comments addressed.

We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution.
We are very grateful for your contribution!