docs: fix typos in documentation and error messages

[vtjl10]

Description:
This pull request corrects several typographical errors in documentation and error messages:

• Fixed "occured" to "occurred" in x/staking/README.md
• Fixed "invaled" to "invalid" in crypto/keyring/errors.go

Summary by CodeRabbit

• Documentation
  • Corrected typographical errors in comments and documentation to improve clarity and accuracy. No functional changes were made.

[coderabbitai]

📝 Walkthrough

Walkthrough

This update corrects typographical errors in comments and documentation. Specifically, it fixes spelling mistakes in a comment within the keyring errors file and in the staking module's README documentation. No functional code, logic, or public interfaces are altered.

Changes

File(s)	Change Summary
crypto/keyring/errors.go	Fixed a comment typo: "invaled" → "invalid".
x/staking/README.md	Corrected "occured" → "occurred" in documentation.

Sequence Diagram(s)

No sequence diagram is generated as the changes are limited to comments and documentation.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Knowledge Base: Disabled due to Reviews > Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between 6442916 and 015cd66.

📒 Files selected for processing (2)

• crypto/keyring/errors.go (1 hunks)
• x/staking/README.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Summary

🔇 Additional comments (3)

crypto/keyring/errors.go (1)

18-18: Corrected typo in error comment.

The typo in the comment for ErrInvalidSignMode has been fixed from “invaled” to “invalid.” No functional changes introduced.

x/staking/README.md (2)

467-468: Typo fix: corrected “occured” → “occurred” in slashing description.

The spelling of “occurred” has been updated in the bullet describing slashing of unbonding delegations and redelegations.

---

475-475: Typo fix: corrected “occured” → “occurred” in evidence-based slashing section.

The spelling of “occurred” has been updated in the sentence describing when slashing occurs upon evidence submission.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Post Copyable Unit Tests in Comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this 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.