fix typos in address

[sysrex]

Summary by CodeRabbit

• Documentation
  • Updated instructions for delegating stake to use the correct validator address format, ensuring that the output examples and user commands reflect the accurate format for successful wallet operations.

[coderabbitai]

Walkthrough

The guide for validator nodes was updated to correct the validator address format on the Celestia network. Two instances of the term celesvaloper were replaced with celestiavaloper. The command for retrieving the validator’s address and its displayed output have been updated accordingly. No changes were made to exported or public entity declarations.

Changes

File	Summary
how-to-guides/validator-node.md	Replaced celesvaloper with celestiavaloper in two instances in the command examples and outputs.

Suggested reviewers

• jcstein

Poem

I'm Bunny the coder, leaping with cheer,
Hopping through docs, the fix is here,
With a twitch of my nose and a joyful bound,
Correct addresses now perfectly sound,
In every line of code, my heart does sing—
A happy hop in every little thing!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 97425b7 and b20154e.

📒 Files selected for processing (1)

• how-to-guides/validator-node.md (2 hunks)

🔇 Additional comments (2)

how-to-guides/validator-node.md (2)

42-43: Corrected Address Format in Delegation Instructions.

The text now accurately refers to the validator’s address as celestiavaloper instead of the incorrect celesvaloper, ensuring that users follow the updated and correct address format when delegating stake.

---

54-55: Consistent Example Output Address.

The sample output now displays the correct validator address (celestiavaloper1q3v5cugc8cdpud87u4zwy0a74uxkk6u43cv6hd), which aligns with the updated instructions and prevents potential user confusion.

---

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

• 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 generate docstrings to generate docstrings 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.

[github-actions]

PR Preview Action v1.6.0
🚀 View preview at https://celestiaorg.github.io/docs-preview/pr-1945/
Built to branch main at 2025-03-21 13:09 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[jcstein]

thank you