docs: remove duplicate words from documents

[jasmyhigh]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request includes minor modifications to comments in the defaultMigrationsOrder function in app/module/utils.go, correcting a duplicated word. In app/test/process_proposal_test.go, new test cases for the ProcessProposal method have been added to enhance testing coverage for various transaction scenarios. Significant revisions were made to the adr-006-non-interactive-defaults.md document, clarifying the implementation of non-interactive defaults and introducing new functions for subtree root calculations. Lastly, the consensus rules documentation in specs/src/consensus.md has been improved for clarity and detail.

Changes

File	Change Summary
app/module/utils.go	Minor comment modification in the defaultMigrationsOrder function to remove duplicated word "will".
app/test/process_proposal_test.go	Added new test cases for ProcessProposal, including various transaction scenarios, error handling, and a new calculateNewDataHash function for hash computation. Minor comment updates for clarity.
docs/architecture/adr-006-non-interactive-defaults.md	Significant revisions to clarify non-interactive defaults and transaction handling. Expanded design section with constraints and new functions for subtree root calculations. Decision section marked as "TBD".
specs/src/consensus.md	Enhanced clarity of consensus rules documentation, including detailed descriptions of constants, rewards, penalties, and block structure checks. Pseudocode examples reformatted for better understanding.

Possibly related PRs

• feat: limit the number of messages in prepare proposal #3942: The main PR modifies the PrepareProposal function to limit the number of transactions, which relates to the changes in this PR that also enhance transaction preparation by capping the number of messages in proposals.
• fix: reject BlobTxs larger than 2 MiB #4084: This PR introduces a check for blob transactions exceeding 2 MiB, which is relevant to the main PR's focus on transaction handling and limits in the PrepareProposal function.

Suggested labels

WS: Maintenance 🔧, enhancement, external

Suggested reviewers

• liamsi
• rootulp
• evan-forbes
• cmwaters
• ninabarbakadze

---

📜 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 eedbbd5 and 073f9d3.

📒 Files selected for processing (4)

• app/module/utils.go (1 hunks)
• app/test/process_proposal_test.go (1 hunks)
• docs/architecture/adr-006-non-interactive-defaults.md (1 hunks)
• specs/src/consensus.md (1 hunks)

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

• app/module/utils.go

🔇 Additional comments (4)

app/test/process_proposal_test.go (2)

174-174: LGTM: Well-structured utility function for test data hash calculation.

The function correctly updates the data hash after test mutations, maintaining data consistency across test cases.

---

Line range hint 1-11: LGTM: Comprehensive test coverage for ProcessProposal.

The test suite thoroughly covers various scenarios including:

• Valid and invalid transaction cases
• Version-specific behaviors
• Edge cases for transaction ordering and validation

Also applies to: 32-38

docs/architecture/adr-006-non-interactive-defaults.md (1)

298-298: LGTM: Clear documentation improvement.

The clarification about MsgWirePayForBlob parsing helps developers understand the optimization where other transaction types are not parsed unnecessarily.

specs/src/consensus.md (1)

230-230: LGTM: Helpful clarification about state root computation.

The added note clearly specifies when the new state root should be computed after applying a transaction.

---

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. (Experiment)
• @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.

[gitpoap-bot]

Congrats, your important contribution to this open-source project has earned you a GitPOAP!

GitPOAP: 2024 Celestia Contributor:

Head to gitpoap.io & connect your GitHub account to mint!

Learn more about GitPOAPs here.