Fix typos in documentation and Code comments

[Pricstas]

This pull request addresses several typographical errors in the Celestia app repository:

1. README.md: Corrected the phrase "one second timeout commit" to "one-second timeout commit" for grammatical accuracy.
2. genesis.go: Fixed the usage of "a identifier" to "an identifier" for proper article usage.
3. adr-001-abci++-adoption.md: Replaced "where is was" with "where it was" to fix incorrect grammar.

These changes improve the readability and professionalism of the documentation and code comments while maintaining technical clarity.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request encompasses minor documentation and comment improvements across multiple files. The changes include a hyphen correction in the README.md usage instructions, a grammatical fix in the app/genesis.go comments, and a comprehensive architectural documentation update in docs/architecture/adr-001-abci++-adoption.md detailing the adoption of ABCI++ and its implications for block processing, transaction management, and data validation.

Changes

File	Change Summary
README.md	Corrected phrasing from "one second" to "one-second" in timeout commit instruction
app/genesis.go	Minor grammatical correction in comment from "key'd by a identifier" to "key'd by an identifier"
docs/architecture/adr-001-abci++-adoption.md	Comprehensive documentation update explaining ABCI++ adoption, new methods, message structures, and block processing mechanisms

Sequence Diagram

sequenceDiagram
    participant Validator
    participant Application
    participant BlockProducer

    Validator->>Application: PrepareProposal
    Application-->>BlockProducer: Validate Block Data
    BlockProducer->>Application: ProcessProposal
    Application->>Validator: Validate Proposal

Loading

Possibly related PRs

• docs: correct command of binary file #3467: Documentation update in README.md related to celestia-appd binary command correction

---

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs/architecture/adr-001-abci++-adoption.md (1)

331-331: Consider a more concise phrasing

The sentence could be made more concise by removing "of" while maintaining its technical clarity.

-Ideally, we would move all of the code that computes erasure encoding to the app.
+Ideally, we would move all the code that computes erasure encoding to the app.

🧰 Tools

🪛 LanguageTool

[style] ~331-~331: Consider removing “of” to be more concise
Context: ...a remains there. Ideally, we would move all of the code that computes erasure encoding to ...

(ALL_OF_THE)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 05d1acd and 18f20ef.

📒 Files selected for processing (3)

• README.md (1 hunks)
• app/genesis.go (1 hunks)
• docs/architecture/adr-001-abci++-adoption.md (1 hunks)

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

• README.md
• app/genesis.go

🧰 Additional context used

🪛 LanguageTool

docs/architecture/adr-001-abci++-adoption.md

[style] ~331-~331: Consider removing “of” to be more concise
Context: ...a remains there. Ideally, we would move all of the code that computes erasure encoding to ...

(ALL_OF_THE)