Fix typos and spelling errors in documentation

[Danyylka]

This pull request addresses the following errors in the documentation:

"messages" -> "message"
"defacto" -> "de facto"
"nodes" -> "node's"
"bash hash" -> "bad hash"

I hope my corrections will help you. Thank you for your work.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request introduces documentation updates for the Quantum Gravity Bridge (QGB) validator set management. The changes primarily focus on documenting new message types including BridgeValidator, Valset, MsgSetOrchestratorAddress, and MsgValsetConfirm. The document elaborates on the operational mechanics of the QGB, explaining how validator sets are created, updated, and confirmed, with an emphasis on the bridge's one-way nature and the requirement of over two-thirds voting power for validating events.

Changes

File	Change Summary
docs/architecture/adr-002-qgb-valset.md	Added detailed documentation for QGB validator set message types and processing logic
pkg/appconsts/global_consts.go	Corrected typo in comment from "defacto" to "de facto"
pkg/appconsts/initial_consts.go	Minor grammatical corrections in comments
pkg/da/data_availability_header_test.go	Corrected test case name typo from "bash hash" to "bad hash"

Possibly related PRs

• feat: limit the number of messages in prepare proposal #3942: Introduces limits on messages in PrepareProposal phase
• chore: ABCI methods benchmarks #3904: Modifies constants related to transaction processing limits
• chore: fix some function names in comment #4137: Updates comments in test application setup
• fix: typos #4141: Corrects typographical errors in documentation

Suggested labels

external

Suggested reviewers

• cmwaters
• evan-forbes
• rootulp
• ninabarbakadze
• rach-id

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. We would love to hear your feedback on Discord.

---

📜 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 415e870 and a1621db.

📒 Files selected for processing (4)

• docs/architecture/adr-002-qgb-valset.md (1 hunks)
• pkg/appconsts/global_consts.go (1 hunks)
• pkg/appconsts/initial_consts.go (2 hunks)
• pkg/da/data_availability_header_test.go (1 hunks)

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

• pkg/appconsts/global_consts.go
• pkg/appconsts/initial_consts.go

🔇 Additional comments (2)

pkg/da/data_availability_header_test.go (1)

190-190: LGTM! Test case name correction

The test case name has been corrected from "bash hash" to "bad hash", which better reflects its purpose of testing invalid hash validation.

docs/architecture/adr-002-qgb-valset.md (1)

40-40: LGTM! Documentation structure improvement

The added section header provides better organization and context for the message type definitions that follow.

---

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:

‼️ 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 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.