Skip to content

Conversation

@CreeptoGengar
Copy link
Contributor

@CreeptoGengar CreeptoGengar commented Jul 31, 2025

Summary by CodeRabbit

  • Documentation
    • Corrected various typographical and grammatical errors across multiple architecture documents to improve clarity and accuracy of terminology.
    • Fixed misspellings in technical terms, pronouns, and section headings.
    • Improved consistency in language and corrected minor errors in example text.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 31, 2025

📝 Walkthrough

Walkthrough

A series of documentation files were updated to correct typographical and grammatical errors, including function names, terminology, pronoun agreement, and spelling. One change also corrected a receiver type name in a method signature within documentation. No functional code or logic was affected by these changes.

Changes

Cohort / File(s) Change Summary
ADR Typo Corrections
docs/architecture/adr-038-state-listening.md, docs/architecture/adr-039-epoched-staking.md, docs/architecture/adr-040-storage-and-smt-state-commitments.md, docs/architecture/adr-045-check-delivertx-middlewares.md, docs/architecture/adr-046-module-params.md, docs/architecture/adr-049-state-sync-hooks.md, docs/architecture/adr-050-sign-mode-textual-annex1.md, docs/architecture/adr-050-sign-mode-textual-annex2.md, docs/architecture/adr-050-sign-mode-textual.md
Corrected various typographical and grammatical errors in documentation text, including function names, terminology, and pronoun agreement. No logic or code changes.
Receiver Name Correction
docs/architecture/adr-054-semver-compatible-modules.md
Fixed a typo in the receiver type name in a method signature within documentation. No code or logic affected.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this 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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (5)
docs/architecture/adr-045-check-delivertx-middlewares.md (1)

67-67: Prefer “different from” over “different than” for formal consistency

Minor style nit: in technical documentation, “different from” is generally preferred to “different than”.

-Please note that because CheckTx handles separate logic related to mempool prioritization, its signature is different than DeliverTx and SimulateTx.
+Please note that because CheckTx handles separate logic related to mempool prioritization, its signature is different from DeliverTx and SimulateTx.
docs/architecture/adr-049-state-sync-hooks.md (1)

142-142: Tighten wording for clarity and concision

The sentence is correct but a bit verbose and contains a couple of style redundancies (“are able to”, “outside of”). Consider the edit below to streamline the phrasing and improve readability.

-As a result of this implementation, we are able to create snapshots of binary chunk stream for the state that we maintain outside of the IAVL Tree, CosmWasm blobs for example. And new clients are able to fetch snapshots of state for all modules that have implemented the corresponding interface from peer nodes. 
+As a result of this implementation, we can create binary snapshot streams for state maintained outside the IAVL tree—such as CosmWasm blobs. New clients can fetch these snapshots for all modules that implement the corresponding interface from peer nodes.
docs/architecture/adr-046-module-params.md (1)

145-147: Typo fixed, but tweak wording for smoother grammar

Nice catch on methods 👏. While you’re here, the phrase “persistence logics” reads awkwardly—“logic” is normally uncountable.

- developers are required to implement persistence logics of module parameters.
+ developers are required to implement persistence logic for module parameters.
docs/architecture/adr-038-state-listening.md (1)

530-533: Typo fix approved; minor grammar polish suggested

The rename to RegisterStreamingPlugin aligns the prose with the code snippets—nice catch.
While you’re touching this sentence, a small article is missing (“a helper function”).

-Note that `RegisterStreamingPlugin` function
-is helper function and not a requirement.
+Note that the `RegisterStreamingPlugin` function
+is a helper function and not a requirement.
docs/architecture/adr-050-sign-mode-textual-annex1.md (1)

281-282: Typo fixed, but consider singular verb
While the spelling correction of “invertibility” is correct, the phrase now reads “Data … are not rendered”. If you prefer the more modern singular usage of data, you could change are to is:

-Note: Data longer than 35 bytes are not rendered …
+Note: Data longer than 35 bytes is not rendered …

Purely stylistic—feel free to ignore.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Knowledge Base: Disabled due to Reviews > Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between 403377f and 9461072.

📒 Files selected for processing (10)
  • docs/architecture/adr-038-state-listening.md (1 hunks)
  • docs/architecture/adr-039-epoched-staking.md (1 hunks)
  • docs/architecture/adr-040-storage-and-smt-state-commitments.md (2 hunks)
  • docs/architecture/adr-045-check-delivertx-middlewares.md (1 hunks)
  • docs/architecture/adr-046-module-params.md (1 hunks)
  • docs/architecture/adr-049-state-sync-hooks.md (1 hunks)
  • docs/architecture/adr-050-sign-mode-textual-annex1.md (2 hunks)
  • docs/architecture/adr-050-sign-mode-textual-annex2.md (1 hunks)
  • docs/architecture/adr-050-sign-mode-textual.md (4 hunks)
  • docs/architecture/adr-054-semver-compatible-modules.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/architecture/adr-045-check-delivertx-middlewares.md

[style] ~67-~67: Did you mean ‘different from’? ‘Different than’ is often considered colloquial style.
Context: ...oritization, its signature is different than DeliverTx and SimulateTx. BaseApp hold...

(DIFFERENT_THAN)

docs/architecture/adr-049-state-sync-hooks.md

[style] ~142-~142: As a shorter alternative for ‘able to’, consider using “can”.
Context: ... As a result of this implementation, we are able to create snapshots of binary chunk stream...

(BE_ABLE_TO)


[style] ~142-~142: This phrase is redundant. Consider using “outside”.
Context: ...k stream for the state that we maintain outside of the IAVL Tree, CosmWasm blobs for examp...

(OUTSIDE_OF)


[style] ~142-~142: As a shorter alternative for ‘able to’, consider using “can”.
Context: ...Wasm blobs for example. And new clients are able to fetch snapshots of state for all module...

(BE_ABLE_TO)

docs/architecture/adr-039-epoched-staking.md

[style] ~48-~48: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...thub.com/tendermint/spec/issues/199). * For fairness of deterministic leader electi...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

docs/architecture/adr-050-sign-mode-textual.md

[style] ~14-~14: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...022: Re-ordering of envelope screens. * Dec 14, 2022: Mention exceptions for invert...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Summary
🔇 Additional comments (9)
docs/architecture/adr-039-epoched-staking.md (1)

48-48: Correct plural pronoun — good catch.

The update from “themself” to “themselves” fixes pronoun-number agreement and improves readability. No further changes required.

docs/architecture/adr-040-storage-and-smt-state-commitments.md (2)

20-21: Correct spelling improves technical accuracy – looks good.

The change from “Merkelized” to “Merkleized” aligns with the standard terminology for Merkle trees. No further action required.


33-34: Typo fix acknowledged.

“compute-optimized” is the preferred American spelling; change is appropriate and consistent with the rest of the document.

docs/architecture/adr-054-semver-compatible-modules.md (1)

647-649: Typo correction in receiver name – looks good

The receiver now correctly reads IntegrationTestConfig, matching the struct definition and allowing the sample to compile without errors. No further issues found in this snippet.

docs/architecture/adr-050-sign-mode-textual-annex2.md (1)

80-84: Correct typo – good catch
Replacing “chacters” with “characters” improves clarity; no further action required.

docs/architecture/adr-050-sign-mode-textual-annex1.md (1)

352-354: Heading correction looks good
“Best Practices” is now spelled correctly.

docs/architecture/adr-050-sign-mode-textual.md (3)

14-15: Changelog entry fixed
“Invertibility” spelling is now consistent with the rest of the document.


208-210: Minor wording tweak approved
The corrected “Tip” field comment reads cleanly; nothing else to address here.


288-300: Bulk typo cleanup acknowledged
All occurrences of “invertability” have been replaced by “invertibility” and prose tightened—thanks for the precision.

@aljo242
Copy link
Contributor

aljo242 commented Jul 31, 2025

@CreeptoGengar conflicts

@CreeptoGengar
Copy link
Contributor Author

@aljo242 resolved, all good now

@aljo242 aljo242 changed the title fix: typos docs: typos Aug 4, 2025
@aljo242 aljo242 added this pull request to the merge queue Aug 4, 2025
Merged via the queue into cosmos:main with commit 0290439 Aug 4, 2025
40 of 41 checks passed
warpbuild-benchmark-bot bot added a commit to WarpBuilds/cosmos-sdk that referenced this pull request Aug 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants