chore: fix spelling errors

[github-prbot]

This PR fixes typos in the codebase.
Please review it, and merge if everything is fine.
If there are proto changes, run make proto-gen and commit the changes.

Summary by CodeRabbit

• Bug Fixes
  • Corrected the spelling of "processing" in comments related to the BlockStage type.
  • Fixed the misspelling of "exceed" in comments within test functions.
  • Renamed the Commiter field to Committer in the MockStore struct for clarity.

These changes enhance the readability of the code without affecting functionality.

[coderabbitai]

Walkthrough

Walkthrough

This pull request includes minor corrections across several files, primarily focusing on typographical errors in comments and field names. Changes include correcting the spelling of "processsing" to "processing" in schema/appdata/data.go, fixing the spelling of "exeed" to "exceed" in server/v2/cometbft/abci_test.go, and renaming the Commiter field to Committer in the MockStore struct within server/v2/cometbft/internal/mock/mock_store.go. These modifications enhance the clarity and correctness of the code without altering any functionality.

Changes

File Path	Change Summary
schema/appdata/data.go	Corrected spelling of "processsing" to "processing" in comments.
server/v2/cometbft/abci_test.go	Corrected spelling of "exeed" to "exceed" in comments.
server/v2/cometbft/internal/mock/mock_store.go	Renamed Commiter to Committer in MockStore struct and updated all references.

Possibly related PRs

• test(server/v2/cometbft): Add abci unit tests #21020: Involves minor textual corrections in comments, similar to the changes in schema/appdata/data.go.
• chore: prepare core 1.0.0-alpha.1 #21564: Related to improvements in code clarity and structure, connecting with the documentation enhancements in this PR.
• feat(schema): update event index definitions #21565: Introduces modifications to the Event struct in schema/appdata/data.go, aligning with the focus on clarity in this PR.
• refactor(core): re-add handlers #21575: Refactor in the message handling system, indirectly relating to the overall aim of improving code quality in this PR.

Suggested labels

C:schema, C:server/v2, C:server/v2 cometbft

Tip

New features

Walkthrough comment now includes:

• Possibly related PRs: A list of potentially related PRs to help you recall past context.
• Suggested labels: CodeRabbit can now suggest labels by learning from your past PRs. You can also provide custom labeling instructions in the UI or configuration file.

Notes:

• Please share any feedback in the discussion post on our Discord.
• Possibly related PRs, automatic label suggestions based on past PRs, learnings, and possibly related issues require data opt-in (enabled by default).

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between ac53e33 and df02f23.

Files selected for processing (3)

• schema/appdata/data.go (1 hunks)
• server/v2/cometbft/abci_test.go (2 hunks)
• server/v2/cometbft/internal/mock/mock_store.go (6 hunks)

Files skipped from review due to trivial changes (3)

• schema/appdata/data.go
• server/v2/cometbft/abci_test.go
• server/v2/cometbft/internal/mock/mock_store.go