chore: fix inconsistent struct name in comment

[zhedazijingang]

👮🏻👮🏻👮🏻 !!!! REFERENCE THE PROBLEM YOUR ARE SOLVING IN THE PR TITLE AND DESCRIBE YOUR SOLUTION HERE !!!! DO NOT FORGET !!!! 👮🏻👮🏻👮🏻

PR Checklist:

• Have you read the CONTRIBUTING.md?
• Does your PR follow the C4 patch requirements?
• Have you rebased your work on top of the latest master?
• Have you checked your code compiles? (make)
• Have you included tests for any non-trivial functionality?
• Have you checked your code passes the unit tests? (make test)
• Have you checked your code formatting is correct? (go fmt)
• Have you checked your basic code style is fine? (golangci-lint run)
• If you added any dependencies, have you checked they do not contain any known vulnerabilities? (go list -json -m all | nancy sleuth)
• If your changes affect the client infrastructure, have you run the integration test?
• If your changes affect public APIs, does your PR follow the C4 evolution of public contracts?
• If your code changes public APIs, have you incremented the crate version numbers and documented your changes in the CHANGELOG.md?
• If you are contributing for the first time, please read the agreement in CONTRIBUTING.md now and add a comment to this pull request stating that your PR is in accordance with the Developer's Certificate of Origin.

fix inconsistent struct name in comment

Summary by CodeRabbit

• Documentation
  • Corrected an API comment to reference the proper response type, clarifying the request/response pairing.
  • No changes to message structures, fields, or runtime behavior.
  • Removes ambiguity in API docs to help integrators implement and troubleshoot more easily.

[coderabbitai]

Walkthrough

Updated a comment in proto/cronos/query.proto to correctly reference ContractByDenomResponse as the response type above its definition; no message structures, APIs, or behaviors were changed.

Changes

Cohort / File(s)	Change summary
Proto docs fix proto/cronos/query.proto	Fixed comment to state ContractByDenomResponse (previously mislabeled as ContractByDenomRequest). No schema or functional changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

cronos

Suggested reviewers

• thomas-nguy

Poem

I nibble at comments with whiskers so keen,
A typo hops out and is tidy and clean.
No contracts were harmed, no messages swapped,
Just a note in the proto, politely cropped.
Hop—docs aligned, and my garden's well-topped! 🥕🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 18ed9a0 and e61b1e7.

⛔ Files ignored due to path filters (1)

• x/cronos/types/query.pb.go is excluded by !**/*.pb.go

📒 Files selected for processing (1)

• proto/cronos/query.proto (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• proto/cronos/query.proto

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: semgrep-cloud-platform/scan

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a 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:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit 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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

proto/cronos/query.proto (1)

34-35: Nit: stray double period in comment.

"Params queries permissions for a specific address.." → remove one period.

-  // Params queries permissions for a specific address..
+  // Params queries permissions for a specific address.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 1f80cb2 and 18ed9a0.

📒 Files selected for processing (1)

• proto/cronos/query.proto (1 hunks)

🔇 Additional comments (1)

proto/cronos/query.proto (1)

55-55: LGTM: fixed the response type name in the comment.

The comment now correctly references ContractByDenomResponse and matches the RPC signature and message below. No behavioral impact.

[thomas-nguy]

please verify your commits

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 17.47%. Comparing base (a3c2f70) to head (18ed9a0).
⚠️ Report is 100 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1860      +/-   ##
==========================================
+ Coverage   16.87%   17.47%   +0.60%     
==========================================
  Files          72       75       +3     
  Lines        6163     6059     -104     
==========================================
+ Hits         1040     1059      +19     
+ Misses       5000     4877     -123     
  Partials      123      123              

see 3 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[zhedazijingang]

Executed and signed. Please review again.