chore(docs): Patch validators docs

[dohernandez]

Summary by CodeRabbit

• Documentation
  • Updated shell command in the setup guide to improve version string matching for node software downloads.
  • Corrected file paths in the upgrade guide to accurately reflect the current directory structure for database and keystore backups during validator upgrades.

[coderabbitai]

Walkthrough

The updates modify documentation for validator setup and upgrade procedures. The setup guide's shell command for listing software versions is adjusted to use a broader regex pattern. The upgrade guide corrects file paths for database and keystore directories to reflect the current directory structure in upgrade instructions.

Changes

File(s)	Change Summary
pages/validators/setup-guide.mdx	Updated the regex in a shell command to broaden version string matching for node software.
pages/validators/upgrade.mdx	Corrected file paths for database and keystore directories in upgrade instructions.

Suggested reviewers

• MuncleUscles

Poem

A regex hops and leaps anew,
Through version strings it now will chew.
Paths corrected, guides refined,
Validators stay in line.
With every doc and every line,
The warren’s code will brightly shine!
🐇✨

---

🪧 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.
  • Explain this complex logic.
  • 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 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 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.

[netlify]

✅ Deploy Preview for genlayer-docs ready!

Name	Link
🔨 Latest commit	ef2b074
🔍 Latest deploy log	https://app.netlify.com/projects/genlayer-docs/deploys/6842d6ecec82a90008d4191f
😎 Deploy Preview	https://deploy-preview-223--genlayer-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

pages/validators/upgrade.mdx (1)

37-37: Clarify terminology for config and keystore items.
The line refers to config.yaml and wallet.yaml (files) as “folders.” Consider revising to “files and folders” or listing them separately for accuracy.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7e8b127 and ef2b074.

📒 Files selected for processing (2)

• pages/validators/setup-guide.mdx (1 hunks)
• pages/validators/upgrade.mdx (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

• GitHub Check: Redirect rules - genlayer-docs
• GitHub Check: Header rules - genlayer-docs
• GitHub Check: Pages changed - genlayer-docs

🔇 Additional comments (3)

pages/validators/setup-guide.mdx (1)

82-82: Approve regex update for listing versions.
The simplified sed pattern (v[^/]*) broadens matching to capture all version identifiers after v, which aligns with current version naming conventions.

pages/validators/upgrade.mdx (2)

16-16: Corrected database path aligns with directory structure.
Updating the reference to data/node/genlayer.db matches the datadir configuration and ensures the upgrade steps target the actual storage location.

---

23-23: Updated removal instruction for database storage.
Changing the removal step to data/node/genlayer.db clarifies the correct path for clearing the old database during the v0.2→v0.3 upgrade.