docs: fix spelling issues

[Guayaba221]

Hey !
I fixed several spelling issues.Glad I could help .
Br, Guayaba221.

Summary by CodeRabbit

• Bug Fixes

  • Corrected a typographical error in the documentation of the UnmarshalInterfaceJSON method.

• Refactor

  • Renamed the isReferenceType method to isReferenceableType in the ReferenceableType interface for clarity.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request involves two minor documentation and naming improvements across two files. In codec/codec.go, a typographical error in a comment for the UnmarshalInterfaceJSON method is corrected from "JSON enoded data" to "JSON encoded data". In schema/type.go, the method isReferenceType() is renamed to isReferenceableType() to provide more clarity about its purpose as a marker for reference types. These changes do not impact the functional behavior of the code.

Changes

File	Change Summary
codec/codec.go	Corrected comment typo in UnmarshalInterfaceJSON method documentation
schema/type.go	Renamed method isReferenceType() to isReferenceableType() in ReferenceableType interface

Possibly related PRs

• chore(schema): rename ReferenceType to ReferenceableType #22698: PR involving renaming the ReferenceType interface to ReferenceableType

Suggested labels

C:schema, C:server/v2

Suggested reviewers

• sontrinh16
• julienrbrt
• aaronc

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. This feature will be included in our Pro Plan when released.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 256ec4f and 4e77372.

📒 Files selected for processing (2)

• codec/codec.go (1 hunks)
• schema/type.go (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• codec/codec.go

🧰 Additional context used

📓 Path-based instructions (1)

schema/type.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

🔇 Additional comments (1)

schema/type.go (1)

21-21: Comment follows Go conventions

The comment update follows the standard Go commenting conventions as per the Uber style guide, starting with the function name and providing a clear description of its purpose.

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

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.

[julienrbrt]

Thanks!

whops

[julienrbrt]

Note 2: At this time, we will not be accepting contributions that only fix spelling or grammar errors in documentation, code or elsewhere. The repository has a nightly job that spell checks all files and will automatically open PRs for any spelling errors.

https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md