Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(x/gov): fix typos #21588

Merged
merged 1 commit into from
Sep 9, 2024
Merged

docs(x/gov): fix typos #21588

merged 1 commit into from
Sep 9, 2024

Conversation

hattizai
Copy link
Contributor

@hattizai hattizai commented Sep 9, 2024

fix some typos & grammar errors to improve the doc's readability. :)

Summary by CodeRabbit

  • Documentation
    • Improved clarity and readability of the governance documentation through grammatical corrections and minor rephrasing.

@hattizai hattizai requested review from julienrbrt, sontrinh16 and a team as code owners September 9, 2024 03:17
Copy link
Contributor

coderabbitai bot commented Sep 9, 2024

Walkthrough

Walkthrough

The pull request includes grammatical corrections and minor rephrasing in the governance documentation. These changes aim to improve clarity and readability while maintaining the original content and functionality. Specific adjustments involve correcting phrases and ensuring proper grammatical structure throughout the document.

Changes

Files Change Summary
x/gov/README.md Grammatical corrections and rephrasing for clarity, including adjustments to phrases and sentence structure.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Governance
    participant System

    User->>Governance: Submit proposal
    Governance->>System: Validate proposal
    System-->>Governance: Proposal valid
    Governance->>User: Notify proposal status
Loading

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

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: 1

Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 95383f5 and 08174ff.

Files selected for processing (1)
  • x/gov/README.md (8 hunks)
Additional context used
Path-based instructions (1)
x/gov/README.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

LanguageTool
x/gov/README.md

[grammar] ~95-~95: This is normally spelled as one word.
Context: ...cute any message, effectively acting as super user. ::: ### Deposit To prevent spam, pro...

(SUPER_COMPOUNDS)


[uncategorized] ~276-~276: Possible missing comma found.
Context: ...roposal gets vetoed. * BurnVoteQuorum burns the proposal deposit if the vote does n...

(AI_HYDRA_LEO_MISSING_COMMA)


[style] ~310-~310: Consider shortening this phrase to strengthen your wording.
Context: ...d by governance. Communities wishing to make amendments to their original constitution should use ...

(MAKE_CORRECTIONS)

Additional comments not posted (5)
x/gov/README.md (5)

66-66: Correction: Grammar improvement for clarity.

The phrase "divided in a few steps" has been correctly changed to "divided into a few steps" to improve grammatical accuracy and readability.


95-95: Correction: Clarification of governance capabilities.

The phrase "let governance can execute" has been changed to "let governance be able to execute," which corrects the grammatical structure and clarifies the meaning.

Tools
LanguageTool

[grammar] ~95-~95: This is normally spelled as one word.
Context: ...cute any message, effectively acting as super user. ::: ### Deposit To prevent spam, pro...

(SUPER_COMPOUNDS)


219-219: Correction: Improved grammatical structure.

The phrase "a threshold a NO votes" has been corrected to "a threshold of NO votes," which fixes a typographical error and enhances the sentence structure.


285-285: Correction: Clarification of execution limits.

The phrase "the vote does not reach quorum" has been changed to "if the vote does not reach quorum," which clarifies the conditional nature of the statement and improves the flow of the text.


276-276: Suggestion: Add a comma for clarity.

Consider adding a comma after "vetoed" to improve readability:

- * When the proposal is vetoed with greater than 1/3, deposits will be burned from the governance `ModuleAccount` and the proposal information along with its deposit information will be removed from state.
+ * When the proposal is vetoed, with greater than 1/3, deposits will be burned from the governance `ModuleAccount` and the proposal information along with its deposit information will be removed from state.

Likely invalid or redundant comment.

Tools
LanguageTool

[uncategorized] ~276-~276: Possible missing comma found.
Context: ...roposal gets vetoed. * BurnVoteQuorum burns the proposal deposit if the vote does n...

(AI_HYDRA_LEO_MISSING_COMMA)


This constitution is designed to be immutable, and placed only in genesis, though that could change over time by a pull request to the cosmos-sdk that allows for the constitution to be changed by governance. Communities wishing to make amendments to their original constitution should use the governance mechanism and a "signaling proposal" to do exactly that.
This constitution is designed to be immutable, and placed only in genesis, though that could change over time by a pull request to the cosmos-sdk that allows for the constitution to be changed by governance. Communities wishing to make amendments to their original constitution should use the governance mechanism and a "signaling proposal" to do exactly that.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggestion: Simplify the phrase for stronger impact.

Consider simplifying the phrase to make it more direct and impactful:

- Communities wishing to make amendments to their original constitution should use the governance mechanism and a "signaling proposal" to do exactly that.
+ Communities wanting to amend their original constitution should use the governance mechanism and a "signaling proposal."
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
This constitution is designed to be immutable, and placed only in genesis, though that could change over time by a pull request to the cosmos-sdk that allows for the constitution to be changed by governance. Communities wishing to make amendments to their original constitution should use the governance mechanism and a "signaling proposal" to do exactly that.
This constitution is designed to be immutable, and placed only in genesis, though that could change over time by a pull request to the cosmos-sdk that allows for the constitution to be changed by governance. Communities wanting to amend their original constitution should use the governance mechanism and a "signaling proposal."
Tools
LanguageTool

[style] ~310-~310: Consider shortening this phrase to strengthen your wording.
Context: ...d by governance. Communities wishing to make amendments to their original constitution should use ...

(MAKE_CORRECTIONS)

@julienrbrt julienrbrt added the backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release label Sep 9, 2024
@julienrbrt julienrbrt added this pull request to the merge queue Sep 9, 2024
Merged via the queue into cosmos:main with commit 644b263 Sep 9, 2024
69 checks passed
mergify bot pushed a commit that referenced this pull request Sep 9, 2024
(cherry picked from commit 644b263)
tac0turtle pushed a commit that referenced this pull request Sep 9, 2024
Co-authored-by: hatti <hattizai@gmail.com>
@hattizai hattizai deleted the typos branch September 11, 2024 02:29
@coderabbitai coderabbitai bot mentioned this pull request Sep 20, 2024
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release C:x/gov
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants