fix: update Cosmos Keyring setup links in peggo documentation

[PavelInjective]

Summary by CodeRabbit

• Documentation
  • Updated links to the Cosmos Keyring setup documentation for both Mainnet and Testnet configurations, directing users to version 0.46.
  • Clarified instructions for configuring the Peggo relayer, including the correct path for configuration files and recommended key management practices.
  • Enhanced security warnings regarding the use of plaintext private keys.

[coderabbitai]

Walkthrough

The changes in this pull request involve updates to the documentation for the peggo application, specifically for both the mainnet and testnet configurations. Key modifications include updating links to the Cosmos Keyring setup documentation to point to version 0.46, along with clarifications and enhancements in the instructions for setting up and managing the Peggo relayer. Adjustments were made to the formatting and structure of the documents, improving clarity regarding environment variable configurations and key management.

Changes

File Path	Change Summary
.gitbook/nodes/validators/mainnet/peggo.md	Updated links to Cosmos Keyring setup documentation (v0.46), minor formatting adjustments.
.gitbook/nodes/validators/testnet/testnet-peggo.md	Clarified Peggo relayer setup instructions, updated configuration file path, refined key management instructions, and reiterated security warnings. Updated links to Cosmos Keyring setup documentation (v0.46).

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Peggo
    participant CosmosKeyring
    participant Ethereum

    User->>Peggo: Configure Peggo relayer
    Peggo->>CosmosKeyring: Refer to updated documentation
    User->>CosmosKeyring: Set up Cosmos keys
    User->>Ethereum: Set up Ethereum keys
    Peggo->>User: Confirm configuration

Loading

🐇 "In the land of code where rabbits hop,
We update our docs, and we never stop!
Links to the Keyring, now clear as day,
Helping all users to find their way.
With clearer paths and steps so bright,
Configuration's now a pure delight!" 🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between d1105f6 and d542cfe.

📒 Files selected for processing (2)

• .gitbook/nodes/validators/mainnet/peggo.md (2 hunks)
• .gitbook/nodes/validators/testnet/testnet-peggo.md (2 hunks)

🧰 Additional context used

🪛 LanguageTool

.gitbook/nodes/validators/mainnet/peggo.md

[typographical] ~282-~282: Consider adding a comma after ‘Usually’ for more clarity.
Context: ...y stored on disk in the encrypted form. Usually the keyring is located within node's ho...

(RB_LY_COMMA)

---

[uncategorized] ~282-282: You might be missing the article “the” here.
Context: .... Usually the keyring is located within node's homedir, i.e. `/.injectived/keyring-...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

🔇 Additional comments (2)

.gitbook/nodes/validators/testnet/testnet-peggo.md (2)

229-229: LGTM! Good improvement in documentation versioning.

The update from 'master' to 'v0.46' in the Cosmos documentation link provides a more stable and version-specific reference.

---

375-375: LGTM! Consistent documentation versioning.

The update maintains consistency with the previous link change, ensuring all references to Cosmos documentation point to the same stable version.

---

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:

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