chore: update params.proto

[eltociear]

paramater -> parameter

Summary by CodeRabbit

• Documentation
  • Made minor textual corrections in internal documentation to ensure accurate and consistent terminology.
  • These improvements refine descriptive language and clarity without impacting functionality or user experience.

[coderabbitai]

Walkthrough

This change corrects two spelling mistakes in comment sections within the params.proto file. The typo "paramater" is replaced with "parameter" in descriptions related to unbond slashing valsets window and valset rewards parameters. No functional code or control flow has been affected.

Changes

File	Change Summary
proto/injective/peggy/v1/params.proto	Corrected spelling errors in comments ("paramater" → "parameter") in two locations.

Poem

In the code fields where comments bloom,
I hopped and found a typo in the room,
"Paramater" changed to "parameter" in a blink,
A small fix that brings clarity in a wink,
I, a cheerful rabbit, cheer each clear line! 🐰
May our code forever shine!

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 836fa87 and 3f51761.

📒 Files selected for processing (1)

• proto/injective/peggy/v1/params.proto (2 hunks)

🔇 Additional comments (2)

proto/injective/peggy/v1/params.proto (2)

76-76: Typo Correction in Unbond Slashing Comment

The misspelled word has been corrected from “paramater” to “parameter” in the description of the unbond slashing valsets window. This change improves the clarity of the documentation.

---

89-89: Typo Correction in Valset Rewards Comment

The correction replaces the erroneous “paramater” with “parameter” in the context of valset rewards. This update helps ensure the comment accurately reflects the intended terminology.

---

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:

• 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 generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

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.