docs: update grove ref to new url

[nv-anants]

Overview:

fix broken links in docs

Summary by CodeRabbit

• Documentation
  • Updated the Grove integration link in the multinode deployment guide to point to the correct installation guide, improving navigation and reducing confusion.
  • Ensures users are directed to the appropriate setup instructions without dead or outdated references.
  • No other content changes; functionality and workflows remain unaffected.

[coderabbitai]

Walkthrough

Updated a link in the "Using Grove (default)" subsection of the multinode deployment guide, changing the Grove integration reference from docs/getting-started.md to docs/installation.md. No other content was modified.

Changes

Cohort / File(s)	Summary of Changes
Docs link update docs/guides/dynamo_deploy/multinode-deployment.md	Updated Grove integration link target from docs/getting-started.md to docs/installation.md; no other edits.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I hop through docs with gentle cheer,
A link now points where paths are clear.
From “getting started” I veer with grace,
To “installation” — the proper place.
Thump-thump! The routes align anew,
Guide me true, oh pages blue. 🐇🧭

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

docs/guides/dynamo_deploy/multinode-deployment.md (2)

28-28: Nit: Tweak bullet formatting for consistency.

Avoid starting a list item with a parenthetical; place “optional” after the bolded name.

Apply:

- - (optional) **[KAI-Scheduler](https://github.com/NVIDIA/KAI-Scheduler)**: Kubernetes native scheduler optimized for AI workloads at scale
+ - **[KAI-Scheduler](https://github.com/NVIDIA/KAI-Scheduler)** (optional): Kubernetes native scheduler optimized for AI workloads at scale

---

27-27: Verified Grove installation link; consider using a permalink

I’ve confirmed that the link to docs/installation.md is the correct, canonical installation guide and that no references to the old getting-started.md remain in the repo. To guard against future breaks (e.g., if the file moves), you may want to pin this URL to a release tag or commit SHA:

• File: docs/guides/dynamo_deploy/multinode-deployment.md (line 27)
• Example permalink:
https://github.com/NVIDIA/grove/blob/vX.Y.Z/docs/installation.md
(or use a specific commit SHA in place of vX.Y.Z)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 199b9a3 and cd2254f.

📒 Files selected for processing (1)

• docs/guides/dynamo_deploy/multinode-deployment.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

docs/guides/dynamo_deploy/multinode-deployment.md

[grammar] ~27-~27: There might be a mistake here.
Context: ...duling and auto-scaling for AI workloads - (optional) **[KAI-Scheduler](https://git...

(QB_NEW_EN)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Build and Test - dynamo