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

Fix: Documentation Typos and Improve Clarity #2232

Merged
merged 4 commits into from
Dec 18, 2024

Conversation

cypherpepe
Copy link
Contributor

@cypherpepe cypherpepe commented Dec 11, 2024

Description

This PR fixes several typos and minor documentation errors across multiple files for better clarity and professionalism. The updates include:

  • Preauthorization.md: Corrected transferedtransferred and refined explanations.
  • grpcurl.md: Fixed DescrieDescribe and improved phrasing.
  • state-sync.md: Addressed tesntettestnet and other minor adjustments.
  • transaction_proposal.md: Fixed PrequisitesPrerequisites and ranrun.

These changes ensure a smoother reading experience and reduce ambiguity for developers.

closes: #XXXX


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against correct branch (see CONTRIBUTING.md).
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Wrote unit and integration tests (n/a: documentation-only changes).
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/).
  • Added relevant godoc comments (n/a: no code changes).
  • Added relevant changelog entries under .changelog/unreleased (see Adding Changes).
  • Re-reviewed Files changed in the Github PR explorer.
  • Review Codecov Report in the comment section below once CI passes (n/a: documentation-only changes).

Summary by CodeRabbit

  • Documentation
    • Clarified and corrected spelling and grammatical errors in the Preauthorization.md, grpcurl.md, state-sync.md, and transaction_proposal.md documents.
    • Enhanced clarity of instructions for granting pre-authorization and state synchronization setup.

@cypherpepe cypherpepe requested a review from a team as a code owner December 11, 2024 13:26
Copy link
Contributor

coderabbitai bot commented Dec 11, 2024

Walkthrough

The pull request includes several modifications to documentation files aimed at improving clarity and correcting typographical errors. Changes were made to Preauthorization.md, grpcurl.md, state-sync.md, and transaction_proposal.md, focusing on spelling corrections and grammatical adjustments. The overall structure and content of the documents remain unchanged, ensuring that users can still follow the instructions without confusion. No new functionality or alterations to commands were introduced.

Changes

File Change Summary
docs/Preauthorization.md Corrected spelling of "transfered" to "transferred"; refined text for grammatical accuracy.
docs/grpcurl.md Corrected spelling of "Descrie" to "Describe" in section header; no other changes to content or structure.
docs/state-sync.md Corrected "tesntet" to "testnet"; explicitly set PIO_RPC variable to an IP address; no structural changes.
docs/transaction_proposal.md Corrected "Prequisites" to "Prerequisites"; changed "can be ran" to "can be run"; minor grammatical adjustments.

Possibly related PRs

Suggested labels

documentation

Suggested reviewers

  • Taztingo

Poem

In the land of code where rabbits hop,
We fix our docs, we never stop!
With spelling right and grammar neat,
Our guides are clear, a tasty treat!
So read along, and you will see,
How smooth the path to clarity can be! 🐇✨


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>, please review it.
    • 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 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.

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.

@cypherpepe cypherpepe changed the title Fix/corr Fix: Documentation Typos and Improve Clarity Dec 11, 2024
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

🧹 Outside diff range and nitpick comments (3)
docs/transaction_proposal.md (2)

33-33: Add missing commas for better readability

Consider adding commas to improve readability:

-In order to propose we need a json file containing our messages to run if the proposal passes.
+In order to propose, we need a json file containing our messages to run if the proposal passes.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~33-~33: A comma might be missing here.
Context: .... ## Creating the Proposal In order to propose we need a json file containing our mess...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[style] ~33-~33: Consider a shorter alternative to avoid wordiness.
Context: ... only be stored if the proposal passes. In order to obtain the JSON for this transaction th...

(IN_ORDER_TO_PREMIUM)


[uncategorized] ~33-~33: A comma might be missing here.
Context: ...s. In order to obtain the JSON for this transaction the following command can be run. `pro...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


75-75: Add missing comma in the instruction

Add a comma after "To propose it":

-To propose it the following command can be run:
+To propose it, the following command can be run:
🧰 Tools
🪛 LanguageTool

[typographical] ~75-~75: It seems that a comma is missing.
Context: ...been sent out to Provenance. To propose it the following command can be run: `pro...

(IN_ORDER_TO_VB_COMMA)

docs/Preauthorization.md (1)

17-17: Enhance readability of the spend-limit explanation

Consider restructuring the paragraph for better readability:

-The flag `spend-limit` is used to set the total amount of coin that can be transferred.  Each transfer will deduct from this total until it is exhausted at which point no more transfers can be made. However, the spend limit can be reset by the user doing another pre-authorize transaction.  Note that this new spend limit does not take into account what has already been spent.  So, for example if you grant permissions to transfer 100 coins and 50 are transferred and then you set a new spend limit of 75, that allows the user to now transfer 75 coins.  The previously spent coins are not taken into account with the new spend limit.
+The flag `spend-limit` sets the total amount of coin that can be transferred. Each transfer deducts from this total until exhausted, after which no more transfers can be made. The spend limit can be reset through another pre-authorize transaction. Important notes:
+
+- The new spend limit is independent of previously spent amounts
+- For example, if you:
+  1. Grant permission to transfer 100 coins
+  2. Transfer 50 coins
+  3. Set a new spend limit of 75
+Then the user can transfer 75 more coins, regardless of the previous 50-coin transfer.
🧰 Tools
🪛 LanguageTool

[style] ~17-~17: ‘take into account’ might be wordy. Consider a shorter alternative.
Context: ...Note that this new spend limit does not take into account what has already been spent. So, for e...

(EN_WORDINESS_PREMIUM_TAKE_INTO_ACCOUNT)


[uncategorized] ~17-~17: Possible missing comma found.
Context: ...t what has already been spent. So, for example if you grant permissions to transfer 10...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~17-~17: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ransfer 100 coins and 50 are transferred and then you set a new spend limit of 75, t...

(COMMA_COMPOUND_SENTENCE)


[style] ~17-~17: ‘taken into account’ might be wordy. Consider a shorter alternative.
Context: ...ns. The previously spent coins are not taken into account with the new spend limit. If a user w...

(EN_WORDINESS_PREMIUM_TAKEN_INTO_ACCOUNT)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between ae2196a and 5652e3e.

📒 Files selected for processing (4)
  • docs/Preauthorization.md (1 hunks)
  • docs/grpcurl.md (1 hunks)
  • docs/state-sync.md (1 hunks)
  • docs/transaction_proposal.md (4 hunks)
✅ Files skipped from review due to trivial changes (1)
  • docs/grpcurl.md
🧰 Additional context used
🪛 LanguageTool
docs/Preauthorization.md

[style] ~17-~17: ‘take into account’ might be wordy. Consider a shorter alternative.
Context: ...Note that this new spend limit does not take into account what has already been spent. So, for e...

(EN_WORDINESS_PREMIUM_TAKE_INTO_ACCOUNT)


[uncategorized] ~17-~17: Possible missing comma found.
Context: ...t what has already been spent. So, for example if you grant permissions to transfer 10...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~17-~17: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...ransfer 100 coins and 50 are transferred and then you set a new spend limit of 75, t...

(COMMA_COMPOUND_SENTENCE)


[style] ~17-~17: ‘taken into account’ might be wordy. Consider a shorter alternative.
Context: ...ns. The previously spent coins are not taken into account with the new spend limit. If a user w...

(EN_WORDINESS_PREMIUM_TAKEN_INTO_ACCOUNT)

docs/transaction_proposal.md

[uncategorized] ~33-~33: A comma might be missing here.
Context: .... ## Creating the Proposal In order to propose we need a json file containing our mess...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[style] ~33-~33: Consider a shorter alternative to avoid wordiness.
Context: ... only be stored if the proposal passes. In order to obtain the JSON for this transaction th...

(IN_ORDER_TO_PREMIUM)


[uncategorized] ~33-~33: A comma might be missing here.
Context: ...s. In order to obtain the JSON for this transaction the following command can be run. `pro...

(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)


[typographical] ~75-~75: It seems that a comma is missing.
Context: ...been sent out to Provenance. To propose it the following command can be run: `pro...

(IN_ORDER_TO_VB_COMMA)

🔇 Additional comments (1)
docs/state-sync.md (1)

78-78: Consider using DNS hostnames instead of hardcoded IPs

While the current implementation uses a hardcoded IP as a temporary workaround, this approach may cause maintenance issues if the IP changes. Consider:

  1. Using DNS hostnames for better maintainability
  2. Adding a comment with an expiration date for the temporary workaround
  3. Creating a tracking issue to implement a permanent solution

Let's verify if the IP is still active and if there are any DNS records we could use instead:

@SpicyLemon SpicyLemon merged commit af33265 into provenance-io:main Dec 18, 2024
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants