Fix: Broken Links in Documentation Files

[youyyytrok]

This pull request fixes broken links in the documentation files. Specifically, it addresses issues with links in the following files:

• full-node block-times.md
• cw-orch.md
• ibc-connection.md

Summary by CodeRabbit

• Documentation
  • Updated link references in multiple guides:
    • Block times guide: Updated link to full node setup
    • CosmWasm orchestrator guide: Updated example file paths
    • IBC connection guide: Corrected link to GM world rollup tutorial

[coderabbitai]

Walkthrough

This pull request focuses on updating documentation across multiple guide files. The changes primarily involve updating link references and paths to reflect the current repository structure. In block-times.md, a link is modified and an example command for block time configuration is added. The cw-orch.md guide sees updates to example file paths, and the ibc-connection.md document has a link path adjustment.

Changes

File	Change Summary
guides/block-times.md	- Updated link from ./full-and-sequencer-node to ./full-node - Added example command for setting block time with --rollkit.block_time 1s
guides/cw-orch.md	- Updated example file paths to contracts-ws/contracts/counter/... - Added newline at end of file
guides/ibc-connection.md	- Modified link path from ./gm-world to ../tutorials/gm-world

Possibly related PRs

• Update to use rollkit cli instead of <binary>d #394: Discusses Rollkit CLI changes and commands for starting rollups, which may relate to the block time configuration documentation update

Poem

🐰 Docs hopping down the wiki trail,
Links fixed with a bunny's detail,
Paths corrected, paths aligned,
Documentation now refined,
A rabbit's guide, crisp and bright! 📝

---

📜 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 8165897 and f1c717c.

📒 Files selected for processing (3)

• guides/block-times.md (1 hunks)
• guides/cw-orch.md (1 hunks)
• guides/ibc-connection.md (1 hunks)

✅ Files skipped from review due to trivial changes (2)

• guides/ibc-connection.md
• guides/cw-orch.md

🔇 Additional comments (2)

guides/block-times.md (2)

Line range hint 1-40: Documentation is clear and well-structured

The block time configuration documentation is well-organized with:

• Clear explanations of the configuration flag
• Practical examples showing different time configurations
• Proper code block formatting

🧰 Tools

🪛 LanguageTool

[uncategorized] ~1-~1: You might be missing the article “the” here.
Context: # How to change speed of block production If you have gone t...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

---

4-4: Verify the updated documentation link

The link has been updated from ./full-and-sequencer-node to ./full-node. Let's verify this change.

✅ Verification successful

Link update verified and consistent with documentation

The verification confirms:

• The new target file guides/full-node.md exists
• No references to the old path full-and-sequencer-node remain
• The link update is consistent with other documentation files that reference sequencer node setup

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the existence of the target documentation file and check for any references to the old path

# Check if the new target file exists
echo "Checking if new target file exists..."
fd --type f "full-node.md" guides/

# Check if there are any remaining references to the old path
echo "Checking for any remaining references to the old path..."
rg -l "full-and-sequencer-node" --type md

# Check if this is a consistent change across all docs
echo "Checking for any other files that might need similar updates..."
rg -l "sequencer.*node.*setup" --type md

Length of output: 526

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.