docs: fix broken link

[cr7258]

Overview:

fix broken link.

Details:

Where should the reviewer start?

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

• closes GitHub issue: #xxx

Summary by CodeRabbit

• Documentation
  • Updated the SLA planner guide to reflect the current location of the defaults configuration, ensuring instructions align with the latest project structure.
  • Clarified references to configuration paths to reduce confusion for readers following setup and maintenance steps.
  • Improved accuracy of internal links and references within the document for a smoother navigation and onboarding experience.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[github-actions]

👋 Hi cr7258! Thank you for contributing to ai-dynamo/dynamo.

Just a reminder: The NVIDIA Test Github Validation CI runs an essential subset of the testing framework to quickly catch errors.Your PR reviewers may elect to test the changes comprehensively before approving your changes.

🚀

[coderabbitai]

Walkthrough

Updated SLA planner documentation to change the referenced defaults.py path from /components/planner/src/dynamo/planner/defaults.py to /components/src/dynamo/planner/defaults.py.

Changes

Cohort / File(s)	Summary
Docs path update docs/architecture/sla_planner.md	Updated the documented path to the defaults file to the new location.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I twitch my ears at tidy trails,
A path now straight where old one fails.
Hop-hop through docs, I set the way—
From nested burrows to brighter day.
A nibble of links, a gentle fix,
Carrots aligned with cleaner ticks.

Pre-merge checks

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description follows the template structure but leaves the “Details” and “Where should the reviewer start?” sections blank, so it does not provide the required information about what was changed or which files to review.	Please complete the “Details” section with a summary of the specific change (e.g., updating the path in docs/architecture/sla_planner.md) and list the file(s) or sections the reviewer should examine under “Where should the reviewer start?” to meet the template requirements.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title succinctly indicates that a documentation link was broken and has been fixed, directly reflecting the primary change without unnecessary detail.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 90dc758 and c16d7aa.

📒 Files selected for processing (1)

• docs/architecture/sla_planner.md (1 hunks)

⏰ 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

🔇 Additional comments (1)

docs/architecture/sla_planner.md (1)

24-24: Approve link update Confirmed that components/src/dynamo/planner/defaults.py exists; link is valid.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}