docs: fix typos README.md

[osrm]

Corrected typos and polished the documentation to make it clearer. Hope this fix helps :)

"usecases" -> "use cases"

"contract calls, that involve token movement." -> "contract calls that involve token movement."

"cryptogaphically" -> "cryptographically"

"Weather" -> "Whether"

Description

Closes: #XXXX

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title, you can find examples of the prefixes below:

• confirmed ! in the type prefix if API or client breaking change
• targeted the correct branch
• provided a link to the relevant issue or specification
• reviewed "Files changed" and left comments if necessary
• included the necessary unit and integration tests
• updated the relevant documentation or specification, including comments for documenting Go code
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed all author checklist items have been addressed
• reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

• Documentation
  • Improved spelling and formatting in the README file for better readability and professionalism.
  • Corrected terminology for consistency (e.g., "wasm" to "Wasm") and clarified phrases (e.g., "usecases" to "use cases").

[coderabbitai]

Walkthrough

The changes involve updates to the app/ibc-hooks/README.md file, focusing on spelling and formatting corrections. Key terms have been standardized, and various typographical errors have been rectified to improve clarity and consistency in the documentation.

Changes

Files	Change Summary
app/ibc-hooks/README.md	Corrected spelling errors ("cryptogaphically" to "cryptographically", "Weather" to "Whether"), capitalized "wasm" to "Wasm", and separated "usecases" into "use cases".

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Documentation
    User->>Documentation: Request for clarity
    Documentation-->>User: Provide updated README
    User->>Documentation: Review changes
    Documentation-->>User: Confirm corrections made

Loading

Poem

In the garden of code, where the rabbits play,
Words once tangled now dance in a way.
"Wasm" stands tall, and "use cases" are clear,
With each little fix, we spread joy and cheer!
So hop along, friends, let the changes unfold,
In the world of our docs, new stories are told! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between a0c1dbd and 1810120.

📒 Files selected for processing (1)

• app/ibc-hooks/README.md (3 hunks)

🧰 Additional context used

LanguageTool

app/ibc-hooks/README.md

[style] ~7-~7: The phrase “a variety of” may be wordy. To make your writing clearer, consider replacing it.
Context: ...olve token movement. This is useful for a variety of use cases. One of primary importance is...

(A_VARIETY_OF)

---

[grammar] ~111-~111: It seems that “to” is missing before the verb.
Context: ...IBC packet is cryptographically valid * Ensure the incoming IBC packet is not timed ou...

(MISSING_TO_BETWEEN_BE_AND_VB)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.